https://issues.apache.org/bugzilla/show_bug.cgi?id=45419
--- Comment #1 from Will Rowe <[EMAIL PROTECTED]> 2008-07-17 08:02:53 PST --- We might have lost sight of the issue here; this issue is not whether or not it's possible to encode utf-16-le, it's that the URI was not encoded in that character set. As I pointed out above, in the similar -be encoding, we need 16 bits to transmit each character, This particular browser sent 8 bit octets. That is not utf-16. Two escaped characters does not constitute a utf-16 request, it's a utf-16 fragment within an ASCII/ISO-8859/UTF-8/whatever bytestream. I would recommend no change whatsoever in Tomcat's code on this issue. As far as working around it, it might be nice if one could deploy a Valve that was triggered based on User-Agent, that would probably be the most elegant hack for this browser flaw. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
