Uh oh!
There was an error while loading. Please reload this page.
Remove Uri scheme validation from HttpRequestMessage - #55035
Conversation
ghost
commented
Jul 1, 2021
Tagging subscribers to this area: @dotnet/ncl Issue DetailsFixes #52836 Removed the Uri scheme check from Any scheme will be passed to handlers. No merge: Should other handlers have filters for specific schemes?
|
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
geoffkizer
commented
Jul 1, 2021
Yeah, we should add the same logic to WinHttpHandler. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
MihaZupan
commented
Jul 8, 2021
With this PR:
@lewing is this the desired behavior for Browser, or should we be filtering out relative Uris? |
MihaZupan
commented
Jul 9, 2021
/azp run runtime-libraries-coreclr outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Why do we disable telemetry if the Uri isn't absolute?
There was a problem hiding this comment.
The call to RequestStart that follows this check will access Uri fields that would throw for relative Uris.
Adding this check here so that you get the meaningful exception message from SocketsHttpHandler instead.
Uh oh!
There was an error while loading. Please reload this page.
9eb1416 to
da8844dCompare
Fixes#52836
Removed the Uri scheme check from
HttpRequestMessage/HttpClient.BaseAddressand moved it inSocketsHttpHandler.ValidateAndNormalizeRequest.Any scheme will be passed to handlers.
No merge: Should other handlers have filters for specific schemes?
WinHttpHandlertakes 85 seconds to figure out it can't processfoo://httpbin.orgwithout a fail-fast like this for example.Added
http/httpschecks toWinHttpHandler.