RFC 5987 Encoding on content-disposition headers #1765
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Important
Update
Content-Disposition
headers to use RFC 5987 encoding for filenames inexport_files
andget_document_file
.Content-Disposition
header to use RFC 5987 encoding for filenames inexport_files
andget_document_file
.urllib.parse.quote
to handle special characters.export_files
to setContent-Disposition
withfilename*=UTF-8''{encoded_filename}
.get_document_file
to setContent-Disposition
withfilename*=UTF-8''{encoded_filename}
.This description was created by for d28b645. It will automatically update as commits are pushed.