-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Incorrect quoting in Content-Disposition headers? #520
Comments
According the spec:
Where token is:
So |
We can enforce quoting, however. It shouldn't cause any harm. But suddenly, you cannot enforce it without a patch. With what service do you have such problem btw? |
This is with Strava's upload API. I posted to their developer support forum as well: |
BTW SimpleCookie starting from Python 3.5 enforces quoting for cookie names |
(#520) Always quote params for Content-Disposition
Fixed by #641 |
I've having a hard time grokking the various RFCs, but I just came across a service that refused to parse Content-Disposition lines like this:
But accepted this:
The only difference being the quoting of the
name
parameter. Is aiohttp doing the right thing here? Is there a way to force quoting to happen?The text was updated successfully, but these errors were encountered: