-Original Message-
From: Rainer Jung [mailto:rainer.j...@kippdata.de]
Sent: Sunday, December 12, 2010 10:23 PM
To: users@tomcat.apache.org
Subject: Re: Tomcat Jakarta 1.2.31 ISAPI Reconnector incorrectly
sending Content body with HTTP 304 Status
10054 is a winsock error code, so
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.
On 12.12.2010 19:09, Konstantin Preißer wrote:
I have one additional question about the ISAPI Redirector (I have chunked
encoding enabled):
In my isapi redirector's log, a lot of lines look like this (I removed the
date prefix):
[1764:3472] [error] iis_write::jk_isapi_plugin.c (1297): Vector
Now if I do a GET-Request with an If-modified-since header to a file
which
doesn't exist, Tomcat returns a 302 Not Modified response instead of 404
Not
Found. I think this is because Tomcat compares the date after the
Is-modified-since header to the date of the static 404 error file, thus
On 11/29/10 8:38 PM, Konstantin Preißer wrote:
At the moment I can't reproduce this issue any more. It happened
some days ago, when I was viewing the webapp by Firefox and
pressed F5 several times, when I noticed that Firefox sometimes
displayed HTTP Headers as plain text. I used a network
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
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
This is the first time I ask a question here, so I hope I do it right.
I am using Tomcat 7.0.5 (with Tomcat Native 1.1.20 library) on Windows
Server 2003 (32-Bit) with Java 1.6.0_22, and I have configured IIS6.0 to use
the Jakarta 1.2.31 ISAPI Redirector (with enable_chunked_encoding set to
OK, after a bit more investigation I can replicate your responses: One
is a 304 response with a response.flushBuffer() or similar, and the
other is a 304 response with an implicit close.
I've tested a fix to the ISAPI Redirector to resolve this.
Hello,
OK, after a bit more investigation I can replicate your responses: One
is a 304 response with a response.flushBuffer() or similar, and the
other is a 304 response with an implicit close.
I've tested a fix to the ISAPI Redirector to resolve this.
At the moment I can't reproduce this issue any more. It happened
some days ago, when I was viewing the webapp by Firefox and
pressed F5 several times, when I noticed that Firefox sometimes
displayed HTTP Headers as plain text. I used a network sniffer to
see what the responses looked
Konstantin Preißer wrote:
Good afternoon,
This is the first time I ask a question here, so I hope I do it right.
You seem to be on the right path, considering the next paragraph.
I am using Tomcat 7.0.5 (with Tomcat Native 1.1.20 library) on Windows
Server 2003 (32-Bit) with Java 1.6.0_22,
Not saying that there may not be a problem in the isap_redirector, but
in the answers above, I see a header Server: Microsoft-IIS/6.0
Are you sure that it is not IIS which is sending back these responses ?
Since you are talking about static pages and images, it may be that
these are
13 matches
Mail list logo
