http_proto
http_proto copied to clipboard
cppalliance
HTTP/1 parsing and serialization algorithms using C++11
`request` and `response` still use `copied_strings`. Switch to `move_chars` and remove `copied_strings` from the project.
The parser should allow for user-defined filters to ignore fields that are not of interest, by removing them from the input stream.
`fields_base` and `fields_view_base` need tests to make sure their special members are inaccessible.
we don't need the partial success condition just the fatal one, which we can recycle from boost.url the error code enum values need to be looked at again after parsing...
If two or more HTTP responses are read into the `parser` buffer, and the `parser::prepare()` buffer returns a non-empty mutable buffer, then the subsequent `async_read_some` operation on the stream will...
The `parser` needs internal exposition, added to the .cpp file in the form of C-style and C++-style comments, explaining in sufficient detail that someone new to the project can get...
The service registry has a dependency on `type_index` which requires RTTI, so the code currently polyfills this via: https://github.com/cppalliance/http_proto/blob/develop/include/boost/http_proto/detail/type_index.hpp This incurs extra maintenance burden not to mention the introduction of...
To implement automatic decoding in the parser, we first need to detect the encoding of the body. This task is complicated by the existence of two headers that determine the...
Metadata
Owner
Metadata
HTTP/1 parsing and serialization algorithms using C++11