GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||
GeezerVison is showing github.com — Fix expect 100-continue Issue with Web Cmdlets by markekraus · Pull Request #8679 · PowerShell/PowerShell Conversation
|
|
Ilya (@iSazonov) It's not a breaking change. In previous versions of .NET Core it would have been as some linux distros were sending the header by default due to curl. That is no longer the case with the new HttpClient stack. By default this header is not sent, but we were (before this PR) forcibly removing it if it was present which means users were not even able to send it if they chose. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Mark Kraus (@markekraus) Thanks! If we don't break any scripts the breaking-change label is not needed. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Mark Kraus (@markekraus) Thanks for your contribution! |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Web Cmdlets will no longer forcibly remove Expect: 100-continue from web requests. This was a legacy setting that needed to be there because of platform differences that have since been resolved in CoreFX.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
[Invoke-WebRequest][PSVersion 6.0.2] Unable to set "expect" (100-continue) request-header field in multipart/form-data
There was an error while loading. Please reload this page.