Repository navigation
[Http] Implement full HTTP/1.1 spec #3
Description
Some todos:
- delimit requests by empty body, content-length or chunked encoding (as defined by the RFC)
- keepalive
- 100-continue handling (could be improved by adding a separate event for that header)
- pipelining
- multipart parsing (inspiration)
We also need to decide how to handle encoding of outgoing data. There are different use cases for modifying the response, some of which may require buffering: websockets, gzip compression, chunked encoding.
Activity
Merge pull request #3 from reactphp/libuv-filesystem
andig commentedon Mar 11, 2015
Is there any progress? I understand without this solved there is no simple reading POST requests?
onigoetz commentedon Mar 12, 2015
I started work on reactphp/http#13 and that adds the ability to read POST request parameters
But don't know how to finalize the part with file uploads. we should implement each upload a a stream, but I don't know how to do it.
If you want to give a hand, you're welcome to do so.
andig commentedon Mar 20, 2015
Imho simple post handling is a very necessary first step. Why not skip multipart for now?
onigoetz commentedon Apr 12, 2015
Actually, POST is also sent through multipart. An implementation of POST without multipart would be incomplete.
clue commentedon Feb 8, 2017
See reactphp/http#39 and reactphp/http#96