tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pid <...@pidster.com>
Subject Re: Tomcat Jakarta 1.2.31 ISAPI Reconnector incorrectly sending Content body with HTTP 304 Status
Date Fri, 03 Dec 2010 23:04:28 GMT
On 12/3/10 5:53 PM, Konstantin Prei├čer wrote:
> On 12/03/10 18:05 PM, Pid wrote:
>> So, if you can consistently repeat this, can you also confirm
>> that changing the date of the static error page prevents the
>> 304 from being sent on a subsequent request?
> 
> Hello,
> 
> when I change the date of the static error page so that it is newer than the
> one which is sent in the "If-Modified-Since" header, then on subsequent
> requests Tomcat returns correctly "404 Not Found", not "304 Not Modified"
> anymore (however it returns a "Last-Modified" header with the new date of
> that static error file). 
> 
> If I then do a GET request again, but with a date which again is newer than
> the one of the static error file, then Tomcat returns 304 again.

A lively debate will no doubt follow, if the HTTP and Servlet specs
differ, but I don't believe a modification type header is appropriate
for a 404.

So that, I suspect, is a bug.  You can add it to bugzilla unless this
email is followed by people pointing out that I'm completely wrong.


p



Mime
View raw message