tract the domain name and reject the rest (if the
encoding was incorrect)
But due to tomcat rejecting the whole URL, we can't even get the domain from
the URL.
--
View this message in context:
http://tomcat.10.n6.nabble.com/tomcat-bad-encoding-tp4983806p4984193.html
Sent from the Tomcat - D
On 10/07/2012 18:03, Thushara Wijeratna wrote:
> Is it possible to have tomcat treat bad URI encodings leniently?
No. Sorry.
> 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. B
On 2012-07-10 19:03, Thushara Wijeratna wrote:
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
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 w
