-
Notifications
You must be signed in to change notification settings - Fork 113
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
fix: quotes in content-disposition header #4748
fix: quotes in content-disposition header #4748
Conversation
f958054
to
6f42cd2
Compare
Replaces the quotes by actually encoding the filename in the dav `Content-Disposition` header. The value of the `filename*` parameter must not be surrounded by any quotes, but rather be encoded in the first place. See RFC-6266 for more details. The quotes caused an issue where certain browsers would decode the quotes and falsely prepend them to the filename.
6f42cd2
to
d9a5e03
Compare
@saw-jan Do you know if the CI is currently flaky? I can't get it green, there always some test(s) failing. They are located in |
tests with posix-fs were flaky previously. owncloud/ocis#9340 |
c2a533e
to
d9a5e03
Compare
Fixes the encoding of blanks in the dav `Content-Disposition` header. This is a regression caused by cs3org#4748.
Fixes the encoding of blanks in the dav `Content-Disposition` header. This is a regression caused by cs3org#4748.
Fixes the encoding of blanks in the dav `Content-Disposition` header. This is a regression caused by cs3org#4748.
Fixes the encoding of blanks in the dav `Content-Disposition` header. This is a regression caused by cs3org#4748.
Fixes the encoding of blanks in the dav `Content-Disposition` header. This is a regression caused by cs3org#4748.
Fixes the encoding of blanks in the dav `Content-Disposition` header. This is a regression caused by cs3org#4748.
Fixes the encoding of blanks in the dav `Content-Disposition` header. This is a regression caused by cs3org#4748.
…er-stable [backport #4748] fix: quotes in content-disposition header
Replaces the quotes by actually encoding the filename in the dav
Content-Disposition
header. The value of thefilename*
parameter must not be surrounded by any quotes, but rather be encoded in the first place. See RFC-6266 for more details.The quotes caused an issue where certain browsers would decode the quotes and falsely prepend them to the filename.
refs owncloud/web#11031