-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nick,
On 8/13/2010 3:16 PM, Nick Langlois wrote:
> thanks for the response. I've already done quite a bit of
> analysis and reported it in the following bug:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=49718
I apologize for not
On Thu, Aug 12, 2010 at 5:02 PM, Pid wrote:
> On 11/08/2010 14:38, Nick Langlois wrote:
> > Hi,
> >I need confirmation of an issue I've encountered while upgrading from
> > Apache Tomcat 5.5.25 to 5.5.29 running in Java 1.5.0_22 on Solaris 10u8.
> > Unfortunately, I'm going about this backwar
Hi Chris,
thanks for the response. I've already done quite a bit of
analysis and reported it in the following bug:
https://issues.apache.org/bugzilla/show_bug.cgi?id=49718
In summary, the issue was introduced in 5.5.28 as a fix for:
46984: Reject requests with invalid HTTP methods w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nick,
On 8/11/2010 9:38 AM, Nick Langlois wrote:
> Get "HTTP/1.1 400 Bad Request" response back when Tomcat receives an HTTP
> simple request (no HTTP version specified in request line).
[snip]
> Example of expected behaviour:
>
> wcars1u7-unit1# t
On 11/08/2010 14:38, Nick Langlois wrote:
> Hi,
>I need confirmation of an issue I've encountered while upgrading from
> Apache Tomcat 5.5.25 to 5.5.29 running in Java 1.5.0_22 on Solaris 10u8.
> Unfortunately, I'm going about this backwards as I've already created a bug
> report. The tomcat s
Hi,
I need confirmation of an issue I've encountered while upgrading from
Apache Tomcat 5.5.25 to 5.5.29 running in Java 1.5.0_22 on Solaris 10u8.
Unfortunately, I'm going about this backwards as I've already created a bug
report. The tomcat site, however, recommends that confirmation should be
