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

FormData problem with Cyrillic characters #695

Closed
konstantin-doncov opened this issue Mar 6, 2020 · 7 comments
Closed

FormData problem with Cyrillic characters #695

konstantin-doncov opened this issue Mar 6, 2020 · 7 comments

Comments

@konstantin-doncov
Copy link

When I send FormData which has String with Latin characters, I get this:

----dio-boundary-0956346409
content-disposition: form-data; name="MyRequest"

{"someInt":5,"someBool":true,"someString":"English text"}
----dio-boundary-0956346409--

And this is ok, I think.
But when I send FormData with Cyrillic(Russian) characters, I get this:

----dio-boundary-2698561535
content-disposition: form-data; name="MyRequest"
content-type: text/plain; charset=utf-8
content-transfer-encoding: binary

{"someInt":5,"someBool":true,"someString":"Русский текст"}
----dio-boundary-2698561535--

So, I get extra content-type and content-transfer-encoding fields.
I also have the same issue if my FormData has only a String.
I think this is the wrong behavior because:

  • FormData has a content-type: text/plain even if it contains not only String
  • FormData has a different behavior for Latin and Cyrillic alphabets.

Is it a bug? And how can I get rid of a content-type and content-transfer-encoding fields?

@konstantin-doncov
Copy link
Author

Guys, I still have this issue. Can anyone help me with this?

@stale
Copy link

stale bot commented Apr 18, 2020

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.

@stale stale bot added the stale label Apr 18, 2020
@stale stale bot closed this as completed Apr 25, 2020
@1232209
Copy link

1232209 commented May 17, 2021

same here,did you solved?

@Darnelo-Inc
Copy link

i have the same problem...

@Arteandr
Copy link

HELP!

@Arteandr
Copy link

same here,did you solved?

did you solve it

@AlexV525
Copy link
Member

AlexV525 commented Oct 7, 2024

Please file new issues with a minimal reproducible example if anyone still sees the issue.

@AlexV525 AlexV525 reopened this Oct 7, 2024
@AlexV525 AlexV525 closed this as not planned Won't fix, can't repro, duplicate, stale Oct 7, 2024
@cfug cfug locked and limited conversation to collaborators Oct 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants