Is it possible to have tomcat treat bad URI encodings leniently? It
currently modifies a buffer in place and if a % sign is followed by
anything other than 2 hexadecimal characters, it gives up decoding and
throws an exception. But if this method was changed to a lenient decoding,
then the buffer would not be corrupt and can be returned to caller.

We get bad encodings due to various truncation issues so it is very helpful
if we can get a lenient decoding.

Please let me know if this is something that could be looked at. I'd
volunteer dev / test time to get this in the code.

thx,
thushara

Reply via email to