-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Unify MaxResponseHeadersLength calculations #73907
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
Conversation
|
Tagging subscribers to this area: @dotnet/ncl Issue DetailsFixes #73848
|
src/libraries/System.Net.Http/src/System/Net/Http/SocketsHttpHandler/Http3RequestStream.cs
Show resolved
Hide resolved
stephentoub
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we missing a test?
|
We have an existing test that checks that we enforce the limit, but we don't check inputs that would overflow - added that. Actually, it looks like that existing test is limited to 1.1 :/ Let me fix that |
src/libraries/Common/tests/System/Net/Http/HttpClientHandlerTest.MaxResponseHeadersLength.cs
Outdated
Show resolved
Hide resolved
|
The tests are failing with the WinHTTP variants. |
Fixes #73848