Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[BrowserKit] Raw body with custom Content-Type header#36839
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
Uh oh!
There was an error while loading.Please reload this page.
Conversation
ro0NL commentedMay 16, 2020
nicolas-grekas left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Thanks. Here is some nitpicking.
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.
Uh oh!
There was an error while loading.Please reload this page.
azhurb commentedMay 16, 2020
Hi@ro0NL. Actually I believe we need to preserve content-type only if the raw body data is not empty. It looks like other cases are already covered. Anyway, your patch should work as well :) |
azhurb commentedMay 16, 2020
There is also discussion from 2016 about this issue#20042 |
fabpot commentedMay 22, 2020
Thank you@azhurb. |
Uh oh!
There was an error while loading.Please reload this page.
Currently, if you try to send POST/PUT request with custom
Content-Typeheader and specified body, the real request will containtext/plaincontent type.Following code
produces next request
With this fix, the request will be