You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RomanBelozerov
changed the title
hpack decoder does not work as expected with TCP segmentation 1 byte and @ in header value
huffman decoder does not work as expected with TCP segmentation 1 byte
Apr 21, 2023
Scope
1 case:
Send h2 request with TCP segmentation 1 byte and header
from: testuser@example.com
. Header value contain "@",AR: Tempesta forwarded request with header
from: testuserj.I7iB0nWaN
ER: Tempesta forwarded request with header
from: testuser@example.com
2 case:
For frang config:
Send h2 request with TCP segmentation 1 byte and header
host: [20:11:abb::1]:443
AR: Tempesta returns 400 response and dmesg warning
ER: Tempesta returns 403 response
3 case:
Send h2 request with TCP segmentation 1 byte and header
accept: */*
:AR: Tempesta returns 400 response and dmesg warning
ER: Tempesta forwards request to server.
Testing
t_http_rules.test_h2_http_rules.HttpRulesH2.test_scheduler
with -T 1 option or;from: testuser@example.com
) or;t_frang.test_host_required.FrangHostRequiredH2TestCase.test_h2_host_header_as_ipv6
andtest_h2_authority_header_as_ipv6
with -T 1 option or;sessions.test_js_challenge.JSChallengeH2.test_get_challenge
with -T 1 option.The text was updated successfully, but these errors were encountered: