http_proto

http_proto copied to clipboard

Once the HTTP-version for a connection has been established, both sides MUST use that version for all subsequent messages on that connection. In practical terms the parser should return an...

vinniefalco

Looks like this is already handled inside `prefix_op_t`, but we still need to add test cases for it in the [response](https://github.com/cppalliance/http_proto/blob/develop/test/unit/response.cpp) and [request](https://github.com/cppalliance/http_proto/blob/develop/test/unit/request.cpp) tests.

ashtum

We use the term "message" to describe the start-line plus fields, and this is confusing because we also use "message" to describe the full request or response including the body....

vinniefalco

We need routines to convert `std::chrono` time points to HTTP-date: https://www.rfc-editor.org/rfc/rfc9110.html#http.date The server example in http_io has a crude printing function for the current time

vinniefalco

Parser should preserve trailing headers in chunked HTTP messages

3

Currently, we are discarding trailing headers. We need to provide an interface that gives access to these fields once the message is completely received. Additionally, we must be cautious of...

ashtum

Currently, dynamic containers have to allocate and memcpy for every newly added field. We need a growth factor to reduce the number of allocations.

ashtum

serializer should set Content-Length if body fits into internal buffer after serialization

1

There are at least two scenarios where this is useful: - When we want to use a source object and there is no way to determine the length of the...

ashtum

serializer should provide an interface to capture and cache HTTP responses

1

This is useful when a server wants to cache static responses specially when they need compression.

ashtum

For efficiency reasons, servers tend not to compress small response bodies. To address this, we define a threshold and skip compressing bodies smaller than that. However, for some source objects...

ashtum

parser_service and serializer_service should probe zlib's memory footprint

1

Currently we are using the suggested formula from zlib's documentation: https://github.com/cppalliance/http_proto/blob/cf22661f3e2811a328aec5e8574fe637017ac007/src/parser.cpp#L472-L480 However, it has the same issue mentioned in the documentation: > zlib's memory footprint can also be specified fairly...

ashtum