http_proto
http_proto copied to clipboard
HTTP/1 parsing and serialization algorithms using C++11
The ZLib service probe should round the measurement of each allocation up to the nearest 64-bit integer. Also, it should return both the total allocated bytes, and the number of...
I would be better to leave out the "Contents" panel on the right side of the Antora documentation. I believe this is done in the playbook or perhaps in the...
Currently, the `parser` object has many members that can be moved into an inner `impl` type and removed from the header files. It would be beneficial to construct the `impl`...
`parser` must destroys Sink and ElasticBuffer objects **immediately** after: - The message body is completely received, or - An unrecoverable parsing error occurs, or - The parser is destroyed.
Temporary strings are sometimes required to call `fields_base::set`. For example: ```C++ request.set(field::host, url.authority().encoded_host_and_port().decode()); ``` ```C++ std::string field = cookie_jar->make_field(url); // temporary field.append(explicit_cookies); // ideally append in place request.set(field::cookie, field); ```...
Since it's common for users to forget to install the parser service, we might want to use a more descriptive error message here. Given that `asio::resolver` can produce the same...
Should http-proto require Boost.JSON?
Should `request_parser` parse the target URL? Where would we store it?
Should we validate the request-target? Should it be opt-in? How do we validate it and where do we pass it?
parser and serializer should both have the same member function name for `is_complete` and `is_done`