Skip to content
This repository has been archived by the owner on Jan 23, 2023. It is now read-only.
/ corefx Public archive

Give SocketsHttpHandler more descriptive error messages #37251

Merged
merged 1 commit into from
Apr 27, 2019

Conversation

stephentoub
Copy link
Member

Currently lots of parsing failures just result in an exception stating "The server returned an invalid or unrecognized response." We can instead be more descriptive about what the problem is in most cases.

cc: @davidsh, @geoffkizer, @wfurt

Currently lots of parsing failures just result in an exception stating "The server returned an invalid or unrecognized response."  We can instead be more descriptive about what the problem is in most cases.
@stephentoub stephentoub merged commit 8e551d4 into dotnet:master Apr 27, 2019
@stephentoub stephentoub deleted the bettersocketshttperrors branch April 27, 2019 23:22
picenka21 pushed a commit to picenka21/runtime that referenced this pull request Feb 18, 2022
…x#37251)

Currently lots of parsing failures just result in an exception stating "The server returned an invalid or unrecognized response."  We can instead be more descriptive about what the problem is in most cases.

Commit migrated from dotnet/corefx@8e551d4
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