Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[HttpClient] Fix strict parsing of response status codes#35324
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
[HttpClient] Fix strict parsing of response status codes#35324
Uh oh!
There was an error while loading.Please reload this page.
Conversation
nicolas-grekas commentedJan 13, 2020
I'm not sure about |
Uh oh!
There was an error while loading.Please reload this page.
nicolas-grekas commentedJan 13, 2020
Thank you @Armando-Walmeric. |
…Armando-Walmeric)This PR was submitted for the master branch but it was squashed and merged into the 4.3 branch instead.Discussion----------[HttpClient] Fix strict parsing of response status codes| Q | A| ------------- | ---| Branch? | 5.0| Bug fix? | yes| New feature? | no| Deprecations? | no| Tickets | No ticket opened| License | MIT| Doc PR | No new featureIf you wait a strict Http code response by the server were you request, but the server response isn't strict and only return HTTP/1.1 200 we have a problem without sense to be strict on regular expression.Commits-------4aa9536 [HttpClient] Fix strict parsing of response status codes
nicolas-grekas commentedJan 13, 2020
Merged into 4.3, will come to upper branches once we merge 4.3 up. |
If you wait a strict Http code response by the server were you request, but the server response isn't strict and only return HTTP/1.1 200 we have a problem without sense to be strict on regular expression.