-
-
Notifications
You must be signed in to change notification settings - Fork 684
Should urlencoded support encoding? #294
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
Comments
I'm not experienced with gbk encoding, but I'd be happy to merge a PR. |
not only gbk, and also win1251, ucs2 etc, I'll work on it asap. |
Cool, thanks! |
@hefangshi, @felixge, was it already done and merged? or maybe PR is pending? |
In #730 we switched to https://developer.mozilla.org/en-US/docs/Web/API/URLSearchParams internally which should handle all the encodings |
We use https://github.com/node-modules/urlencode to create a querystring with gbk encoding, and formidable can't handle the encoding.
Since the multipart encoding works fine, should formidable support the urlencoded encoding setting? I'm willing to create a pr for this.
The text was updated successfully, but these errors were encountered: