go to bug id or search bugs for
This bug report forms part of an attempt to test and fix the implementation of HTTP/1.1 in the HTTP stream wrapper. See http://marc.info/?l=php-internals&m=147544280019519&w=2
A "100 Continue" response is *usually* only sent in response to an "Expect: 100-continue" header, and *usually* only useful with requests which have a body (e.g. POST, PUT). As such, it is unlikely to be encountered by someone sending a GET request using e.g. file_get_contents, but this is not guaranteed.
According to RFC 7231 section 6.2:
> A client MUST be able to parse one or more 1xx responses received
> prior to a final response, even if the client does not expect one. A
> user agent MAY ignore unexpected 1xx responses.
However, the code currently treats these statuses as errors:
> HTTP request failed! HTTP/1.1 100 Continue
Add a Patch
Add a Pull Request
I've created a failing phpt test for this https://gist.github.com/IMSoP/b893785c9c8f04c2b5ce3b0a638b33a7 and intend to attempt a fix.
Pull request filed against 5.6: https://github.com/php/php-src/pull/2175
Thank you for your bug report. This issue has already been fixed
in the latest released version of PHP, which you can download at
https://github.com/php/php-src/pull/2175 was merged