-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
FormData problem with Cyrillic characters #695
Comments
Guys, I still have this issue. Can anyone help me with this? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this is still an issue, please make sure it is up to date and if so, add a comment that this is still an issue to keep it open. Thank you for your contributions. |
same here,did you solved? |
i have the same problem... |
HELP! |
did you solve it |
Please file new issues with a minimal reproducible example if anyone still sees the issue. |
When I send
FormData
which hasString
with Latin characters, I get this:And this is ok, I think.
But when I send
FormData
with Cyrillic(Russian) characters, I get this:So, I get extra
content-type
andcontent-transfer-encoding
fields.I also have the same issue if my
FormData
has only aString
.I think this is the wrong behavior because:
FormData
has acontent-type: text/plain
even if it contains not onlyString
FormData
has a different behavior for Latin and Cyrillic alphabets.Is it a bug? And how can I get rid of a
content-type
andcontent-transfer-encoding
fields?The text was updated successfully, but these errors were encountered: