Re: isHexDigit error problems and upgrading Tomcat and jdk

2012-06-10 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Miguel, On 6/7/12 5:51 PM, Miguel González Castaños wrote: That depends upon how you have configured your access log: you can configure an access log to log only requests that failed and the details of that request like this: Valve

Re: isHexDigit error problems and upgrading Tomcat and jdk

2012-06-07 Thread Miguel González Castaños
On 07/06/2012 00:54, Konstantin Kolinko wrote: 2012/6/7 Miguel González Castañosmiguel_3_gonza...@yahoo.es: 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).

Re: isHexDigit error problems and upgrading Tomcat and jdk

2012-06-07 Thread Stefan Mayr
Am 07.06.2012 10:13, schrieb Miguel González Castaños: ... Do you suggest me to upgrade to Tomcat 6 or 7? What about jdk? 1.6 or 1.7? 1.6 is more widely tested (many years), but for a new system I would go with 1.7. It's not a new system, it's been running for 3 years already. I don't want

Re: isHexDigit error problems and upgrading Tomcat and jdk

2012-06-07 Thread Konstantin Kolinko
2012/6/7 Miguel González Castaños miguel_3_gonza...@yahoo.es: On 07/06/2012 00:54, Konstantin Kolinko wrote: 2012/6/7 Miguel González Castañosmiguel_3_gonza...@yahoo.es: Hi,  We are getting isHexDigit errors again, although there is no malformed URL requests It is parameter parsing

Re: isHexDigit error problems and upgrading Tomcat and jdk

2012-06-07 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Miguel, On 6/7/12 4:13 AM, Miguel González Castaños wrote: It's not a new system, it's been running for 3 years already. I don't want to risk that any library has changed its behavior with tomcat 7 or something similar. I don't believe it's less

Re: isHexDigit error problems and upgrading Tomcat and jdk

2012-06-07 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Miguel, On 6/7/12 4:13 AM, Miguel González Castaños wrote: On 07/06/2012 00:54, Konstantin Kolinko wrote: It is parameter parsing code. It cannot claim the request as malformed (API does not allow it). It can only skip malformed parameters.

Re: isHexDigit error problems and upgrading Tomcat and jdk

2012-06-07 Thread Miguel González Castaños
That depends upon how you have configured your access log: you can configure an access log to log only requests that failed and the details of that request like this: Valve className=org.apache.catalina.valves.AccessLogValve conditionIf=org.apache.catalina.parameter_parse_failed

isHexDigit error problems and upgrading Tomcat and jdk

2012-06-06 Thread Miguel González Castaños
Hi, We are getting isHexDigit errors again, although there is no malformed URL requests We are using Tomcat 5.5 and jdk 1.5 (from Sun). As some of you have suggested me in the past, I'm considering to upgrade to a more up-to-date Tomcat and/or jdk so I can get more support and help from

Re: isHexDigit error problems and upgrading Tomcat and jdk

2012-06-06 Thread Konstantin Kolinko
2012/6/7 Miguel González Castaños miguel_3_gonza...@yahoo.es: 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. It