Skip to content
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 Content-Disposition header for clients without rfc6266 support #1198

Conversation

perrinjerome
Copy link
Contributor

Since #893 the Content-Disposition header supports non-ascii filenames, by containing the filename in ascii and the filename in UTF-8, but the ascii version was produced by applying str on a bytes instance, so it looks like b'file.txt' instead of file.txt.

Since zopefoundation#893 the
Content-Disposition header supports non-ascii filenames, by containing
the filename in ascii and the filename in UTF-8, but the ascii version
was produced by applying `str` on a `bytes` instance, so it looks like
`b'file.txt'` instead of `file.txt`.
@perrinjerome perrinjerome force-pushed the fix/content-disposition-filename branch from 71e849c to 7f4c61c Compare February 17, 2024 13:13
@perrinjerome perrinjerome changed the title Fix Content-Disposition heeader for clients without rfc6266 support. Fix Content-Disposition heeader for clients without rfc6266 support Feb 17, 2024
@perrinjerome perrinjerome changed the title Fix Content-Disposition heeader for clients without rfc6266 support Fix Content-Disposition header for clients without rfc6266 support Feb 17, 2024
@perrinjerome
Copy link
Contributor Author

Thank you

@perrinjerome perrinjerome merged commit 168963a into zopefoundation:master Feb 19, 2024
21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants