tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Konstantin Kolinko <>
Subject Re: isHexDigit error problems and upgrading Tomcat and jdk
Date Thu, 07 Jun 2012 11:19:11 GMT
2012/6/7 Miguel González Castaños <>:
> On 07/06/2012 00:54, Konstantin Kolinko wrote:
>> 2012/6/7 Miguel González Castaños<>:
>>> Hi,
>>>  We are getting isHexDigit errors again, although there is no malformed
>>> URL
>>> requests
>> It is parameter parsing code. It cannot claim the request as malformed
>> (API does not allow it). It can only skip malformed parameters.
> Does that mean that it won't show up in the access log?

Yes, it would not show in access log.

> It is a problem with
> a parameter used by the parsing code?

It is problem with parameters submitted by client. Broken parameters
are ignored (and this warning is printed).

Parameters parsing is performed lazily on your first call to
getParameter() or similar methods. It is not allowed to fail.

In recent versions of Tomcat this and similar failures set a flag in
the request object to signal that an error happened.  This flag can be
tested by your code (using FailedRequestFilter as an example),  or you
can just configure and use FailedRequestFilter  as is, if it is
available in that version of Tomcat.

What ever you do upon detecting the failure - is your choice. The
FailedRequestFilter  rejects the request.

> How can I log any info that could show
> where is the problem in the code or when is this happening? It's making
> Tomcat to pause and then to stop.

This failure cannot make Tomcat pause and stop.

Best regards,
Konstantin Kolinko

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message