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

MultipartFormData ContentHeaderEncoding UTF-8 #3755

Open
apps4everyone opened this issue Aug 1, 2023 · 1 comment · May be fixed by #3754
Open

MultipartFormData ContentHeaderEncoding UTF-8 #3755

apps4everyone opened this issue Aug 1, 2023 · 1 comment · May be fixed by #3754

Comments

@apps4everyone
Copy link
Contributor

apps4everyone commented Aug 1, 2023

Currently it is not possible to set in MultipartFormData the ContentHeader Encoding information for the server side.
Some server fall back to ISO-8859-1 and not use UFT-8 .

Therefore explicit UTF-8 info should be optional possible to set.

The parameters "filename" and "filename*" differ only in that "filename*" uses the encoding defined in RFC5987, allowing the use of characters not present in the ISO-8859-1 character set (ISO-8859-1).

https://www.rfc-editor.org/rfc/rfc6266#ref-ISO-8859-1
https://greenbytes.de/tech/webdav/rfc5987.html#examples

@apps4everyone apps4everyone linked a pull request Aug 1, 2023 that will close this issue
@apps4everyone apps4everyone changed the title MultipartFormData ContentHeaderEncoding UTF-8 & iso-8859-1 MultipartFormData ContentHeaderEncoding UTF-8 Sep 4, 2023
@apps4everyone
Copy link
Contributor Author

Sorry for disturbing @jshier, maybe it is possible to re review. It is more about server side to tell them that UTF-8 is used. This change in my PR is optional and will not break current usage. Thank you

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 a pull request may close this issue.

1 participant