We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There seems to be a problem with how reqwest encodes values of Content-Disposition parameters.
Content-Disposition
RFC 6266 and RFC 8187 defines the characters that can be included without percent encoding in an encoded value of a Content-Disposition parameter as
attr-char = ALPHA / DIGIT / "!" / "#" / "$" / "&" / "+" / "-" / "." / "^" / "_" / "`" / "|" / "~"
which is to say
a-zA-Z0-9!#$&+-.^_`|~
Reqwest uses PATH_SEGMENT_ENCODE_SET from the url crate to encode parameter values, which in addition allows the following characters
PATH_SEGMENT_ENCODE_SET
url
'(),=@[\]
This causes problems when files having any of these characters in their names are uploaded to servers that rely on the RFC
The text was updated successfully, but these errors were encountered:
Sorry for polluting the history with bad commits :( I had some issues with my network and keyboard...
Sorry, something went wrong.
44c8ca3
No branches or pull requests
There seems to be a problem with how reqwest encodes values of
Content-Disposition
parameters.RFC 6266 and RFC 8187 defines the characters that can be included without percent encoding in an encoded value of a
Content-Disposition
parameter aswhich is to say
Reqwest uses
PATH_SEGMENT_ENCODE_SET
from theurl
crate to encode parameter values, which in addition allows the following charactersThis causes problems when files having any of these characters in their names are uploaded to servers that rely on the RFC
The text was updated successfully, but these errors were encountered: