Alexander Shlemin

Kernel crashes under concurrent connections tests

5

Kernel panic occurs when: - backend returns several KB of data - data is requested by multiple connections. Example command to create a load: `wrk -d 120 -t10 -c 100...

Access to any vhost is possible with the valid SNI

3

Access to vhosts does not controlled properly. Its is possible to access any vhost, even not-TLS enabled, after the connection SNI was validated. # Testing Test to reproduce: [tls.test_tls_cert.TlsSNIwithHttpTable](https://github.com/tempesta-tech/tempesta-test/blob/78ddd8e0a4fd770c42a1f79fecc9d7daac69a02a/tls/test_tls_cert.py#L542) Related...

Chunked transfer encoding: cached response is truncated

1

# Scope Cached response is truncated (missing the final CRLF) when chunked transfer encoding is used by backend. This causes client to hang waiting for an incomplete response. Related issue:...

# Scope Kernel panic occurs when: - backend returns minimum headers + several KB of data - H2 request is made DMESG [ 461.140300] [tempesta fw] Warning: Unable to transform...

# Scope Currently, requests containing single character header names are rejected with a 400 code. Request example: ```http GET / HTTP/1.1 X: test ``` Corresponding parser warning: `Warning: Parser error:...

# Scope Currently, PURGE method s logged as a Warning: ```Warning: purge: success, status 200: 192.168.1.1```, because [tfw_http_send_err_resp](https://github.com/tempesta-tech/tempesta/blob/2529df2277f5b91de49c4ff94ed3a0957807cd71/fw/cache.c#L2043) is used to send response. Test to reproduce: [cache.test_purge.TestPurgeGet.test_purge_without_get_completed_with_no_warnings](https://github.com/tempesta-tech/tempesta-test/blob/2c3310afaa835f102529818c5ce4a8778e5e88b9/cache/test_purge.py#L376)

Chunked transfer encoding: PURGE+GET request connection is not closed

4

# Scope For PURGE requests with the `X-Tempesta-Cache: get` header set: * Connection is not closed when chunked transfer encoding is used by backend * When keepalive is used with...

Multiple Set-Cookie headers break the HTTP parser

2

# Scope Backend responses with multiple `Set-Cookie` headers are dropped. Multiple `Set-Cookie` headers support required to run WordPress backend https://github.com/tempesta-tech/tempesta-test/issues/290 Example error output: ``` [267822.051861] [tempesta fw] Warning: Parser error:...

This issue is to address possible steps to document re-connection routine: see PR #33 by @robgar2001 Possible steps: - [ ] `BLE.connectGatt()` Java method should close current GATT client before...

Large responses support

2

# Motivation Currently, it is not possible to serve big responses (files) from backend, because of memory allocation error. DMESG WARNING mm/page_alloc.c:4935 [53957.157446] [tdb] Start Tempesta DB [53957.245089] [tempesta fw]...