[jetty-dev] [jira] (JETTY-1532) HTTP headers decoded with platform's default encoding
"Dawid Weiss (JIRA)" <[email protected]> Mon, 20 Aug 2012 00:53:21 -0500 (CDT)
| Newsgroups | gmane.comp.java.jetty.general |
|---|---|
| Message-ID | <702990430.42642.1345442001217.JavaMail.j2ee-jira@codehaus01.managed.contegix.com> |
Dawid Weiss
commented on JETTY-1532
HTTP headers decoded with platform's default encoding
I did a simple scan for Buffer.toString() and it's called in various places. Since this method is fundamentally broken (uses platform encoding for converting a buffer to a string) then I'd assume any call that relies on it will break sooner or later given non-lower-ascii default codepage. What I would do is replace all calls to Buffer.toString or even make it return something that is not a direct representation of the buffer ("Buffer: ASCII contents=XXX").
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators .
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email