-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release/6.0] Fix HTTTP/2 header decoder buffer allocation #85976
[release/6.0] Fix HTTTP/2 header decoder buffer allocation #85976
Conversation
* Add test for literal field without name reference * Fix header name buffer allocation * Add more tests * Unified QPackDecoderTest test files * Fix variable name * Fixed HPackDecoder and ported QPack tests * Feedback --------- Co-authored-by: ManickaP <mapichov@microsoft.com>
Tagging subscribers to this area: @dotnet/ncl Issue DetailsFixes #78516 Backports #78862 Customer impactReliability problem in HTTP/2 (HPack), where some requests/responses with large headers (4KB+) that should be accepted might end up throwing exception. This is a shared code with Kestrel so this affects server side as well - expect follow up PR in ASP.NET. TestingAdded tests for the root cause and similar scenarios, increasing test coverage. All of those are ran in CI. RiskLow, as this affects only (rare) case of 4KB+ headers data buffers in HTTP/2 (HPack).
|
From: #85341 (comment) Approved by Tactics (@SteveMCarroll) on 4/27 via email. Marking as servicing-approved. |
@ManickaP @MihaZupan @karelz today is code complete for the June Release. Is this ready to merge?
|
@carlossanlop Yes, these should be ready to merge. |
Fixes #78516
Backports #78862
Customer impact
Reliability problem in HTTP/2 (HPack), where some requests/responses with large headers (4KB+) that should be accepted might end up throwing exception.
This is a shared code with Kestrel so this affects server side as well - expect follow up PR in ASP.NET.
Testing
Added tests for the root cause and similar scenarios, increasing test coverage. All of those are ran in CI.
Risk
Low, as this affects only (rare) case of 4KB+ headers data buffers in HTTP/2 (HPack).