Constantine

Current issue may contribute to https://github.com/tempesta-tech/tempesta/issues/1667

Http2 pseudo-headers must be matched by HTTP Tables rules e.g `hdr :authority == "test.com" -> test_host;`. After unifying the processing logic need to ensure, that Authority(Authority from URI for HTTP),...

Hi, I currently working on this issue for my myself. I have almost done with first and second part. When I write tests I will PR. Can you assign it...

Parsing of forwarded header has been implemented. Functional tests also has been added . Now, we need to introduce support of `X-Real-IP`. `X-Real-IP` requires functional tests too.

- [x] Caught warning during sending http2 multiplexed request with six or above streams. ``` [19097.737101] ------------[ cut here ]------------ [19097.737670] WARNING: CPU: 1 PID: 27635 at /home/constantine/projects/tempesta/fw/http_frame.c:232 tfw_h2_context_clear+0x15/0x20 [tempesta_fw]...

For stripping chunked parts at body parsing stage we flag chunks that should be cut, then cut chunked parts from body during HTTP1 to HTTP2 message transformation. For cached responses...

Tempesta prints `[tempesta fw] Warning: Unable to transform HTTP/1.1 data into HTTP/2 format: free space exhausted (accumulated length: 99` when receive certain response from server and forwards it to http2...

Now we use another cache strategy. Before placing response into cache, tempesta transform response to regular form, without chunks and adds Content-Length header. It means once "expected chunked" response will...

FIxed by PR #1418

[RFC 9110 6.6.1](https://www.rfc-editor.org/rfc/rfc9110#section-6.6.1) says: > A recipient with a clock that receives a response with an invalid Date header field value MAY replace that value with the time that response...