Basic "100 Continue" support

[nick4fake]

#94

[clue]

Thanks for filing this PR, but I'd like to see some (significant) changes to this proposal before we can get this in 👍

The intermediary 100 (Continue) response MUST NOT be sent for requests that did not include a proper Expect: 100-continue header (which we never actually send). This implies that we should only really ignore this in this case which in turn implies that we should probably also send this header automatically for certain outgoing requests. Also, the response is actually a "complete" response, which means that we actually have to buffer this to deal with response headers etc. See also #94 for more details.

[nick4fake]

@clue

Also, the response is actually a "complete" response, which means that we actually have to buffer this to deal with response headers etc. See also #94 for more details.

Actually, I have copied working code from the project :)
There is a return that skips further processing

[clue]

Perhaps an example may help, but the following is actually a valid intermediary 100 (Continue) response:

HTTP/1.1 100 Go On!\r\n
Server: ReactPHP\r\n
X-Powered-By:PHP 3\r\n
\r\n
HTTP/1.1 200 Yey!\r\n
Content-Length: 2\r\n
\r\n
OK

[nick4fake]

@clue yep, you are right. I should have read RFC more accurately

[clue]

@nick4fake Thank you for looking into this and confirming this!

I believe this has been answered, so I'm closing this for now. Please come back with more details if this persists and we can reopen this 👍