-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[wasm] HttpRequestMessage.Headers.ExpectContinue is ignored on browser #53876
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsIn unit test
|
- move tests to inner loop - include echo middleware in xharness server - improve doc - more granular ActiveIssue #53592 for lack of TRACE - more granular ActiveIssue #53591 for content on GET/HEAD - more granular ActiveIssue #53874 for HttpRequestMessage.Headers.Host - more granular ActiveIssue #53872 for NPE on System.Net.Http.BrowserHttpHandler - more granular ActiveIssue #53876 - include middleware in Helix correlation payload
This needs browser support, so that the HTTP client would pause after headers, before sending the HTTP payload. But no browser does it, see |
In unit test
System.Net.Http.Functional.Tests.HttpClientHandler_RemoteServerTest.PostAsync_ExpectContinue_Success(expectContinue: True, version: 1.1)
on WASM in BrowserThe text was updated successfully, but these errors were encountered: