tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <wbar...@wilshire.com>
Subject Re: DO NOT REPLY [Bug 20850] - POST is not defined in RFC 2068 and is not supported by the Servlet API
Date Wed, 18 Jun 2003 07:08:47 GMT

----- Original Message -----
From: "Remy Maucherat" <remm@apache.org>
To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Sent: Tuesday, June 17, 2003 11:47 PM
Subject: Re: DO NOT REPLY [Bug 20850] - POST is not defined in RFC 2068 and
is not supported by the Servlet API


> Bill Barker wrote:
> > I don't think that you've really read the stack-trace.  This is
happening
> > well into the Servlet.service method, so Coyote has obviously read the
> > method fine.
>
> Hmmm, I don't think so: service does the request name dispatching.
> And the status returned is 501, not 500.
> The read timeout may not occur on the same request.
>
> All in all, I'll leave to the reporter that he's sending valid requests.
> I think the report is bogus :)

Without more details from the reporter, I certainly wasn't going to
investigate it further :).  At first glance, it just looked to me like one
of the (few) cases where disableUploadTimeout should be false.  However, I
can't explain why this should give a 501 instead of a 500.

>
> Remy
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message