-
Notifications
You must be signed in to change notification settings - Fork 684
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
Wrong request-body decoding for content-type "application/x-www-form-urlencoded" #1212
Comments
@AlinaDidenko Can you prepare a pull request? |
@asolntsev Yes, we will try to fix it |
AlexaWeisse
added a commit
to AlexaWeisse/play1
that referenced
this issue
Jan 11, 2018
Why no review? Why not in the 1.5.1 version? |
@GordeevArt is there a pull request that we could review? |
xael-fry
added a commit
that referenced
this issue
Aug 23, 2018
[#1212] Fix non-Latin characters decode in UrlEncodedParser
Merge #1213 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
there is request with content-type "application/x-www-form-urlencoded; charset=utf-8" and cyrillic symbols in body. After update to play-1.5.0 from play-1.2.7.2 controller params contain invalid character sequences instead cyrillic words. This is due to an error in org.apache.common.codec.net.URLCodec#decode(java.lang.String, java.lang.String) (used in play/data/parsing/UrlEncodedParser.java:132).
For example:
Output:
This error lies in the incorrect receipt of bytes: string.getBytes(Charsets.US_ASCII);
So this decision works only for standard ascii-symbols.
Please fix the error.
The text was updated successfully, but these errors were encountered: