Skip to content
This repository was archived by the owner on Jan 23, 2023. It is now read-only.

Fix MaxResponseHeadersLength assert for value string#39085

Merged
stephentoub merged 1 commit intodotnet:masterfrom
stephentoub:fixasserttest
Jul 1, 2019
Merged

Fix MaxResponseHeadersLength assert for value string#39085
stephentoub merged 1 commit intodotnet:masterfrom
stephentoub:fixasserttest

Conversation

@stephentoub
Copy link
Member

I'd fixed the assert message to contain the right value when MaxResponseHeadersLength was exceeded, but this error message isn't used for WinHttpHandler, and thus it doesn't contain the value. Special-case the check for just SocketsHttpHandler.

I'd fixed the assert message to contain the right value when MaxResponseHeadersLength was exceeded, but this error message isn't used for WinHttpHandler, and thus it doesn't contain the value.  Special-case the check for just SocketsHttpHandler.
@stephentoub stephentoub merged commit e78b22b into dotnet:master Jul 1, 2019
@stephentoub stephentoub deleted the fixasserttest branch July 1, 2019 19:12
@karelz karelz added this to the 3.0 milestone Jul 16, 2019
picenka21 pushed a commit to picenka21/runtime that referenced this pull request Feb 18, 2022
…9085)

I'd fixed the assert message to contain the right value when MaxResponseHeadersLength was exceeded, but this error message isn't used for WinHttpHandler, and thus it doesn't contain the value.  Special-case the check for just SocketsHttpHandler.

Commit migrated from dotnet/corefx@e78b22b
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants