tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Treves" <>
Subject Re: problems serving HTTP requests
Date Tue, 17 Jul 2001 16:25:56 GMT
Thanks for your reply.

The problem is that the ISAPI doesn't seem to pass the request to Tomcat. I
know that is the request is for a non existing page there is an error that
the Tomcat logs, right? Well, even if I request for a page within the
application that does not exist there is no log about it in the Tomcat logs.

IIS logs the action to be successful but Tomcat is not activated at all...

What could cause that kind of behavior?


----- Original Message -----
From: "William Kaufman" <>
To: <>
Sent: Tuesday, July 17, 2001 4:41 PM
Subject: RE: problems serving HTTP requests

> >From the HTTP spec at
> :
> ] 10.2.7 206 Partial Content
> ] The server has fulfilled the partial GET request for the resource.
> That means you called HttpServletResponse.setContentLength() with a number
> bigger than the actual amount of data you're returning.  If you stop
> that, everything should be fine.  (Calling setContentLength() is a good
> idea, but only if you actually know the length, which you rarely do
> bufferring all the data yourself.)
> ] 10.3.5 304 Not Modified
> ] If the client has performed a conditional GET request and
> ] access is allowed, but the document has not been modified,
> ] the server SHOULD respond with this status code.
> That means that Tomcat's copy of your servlet's output is newer than the
> date returned by getLastModified().  If your implementation of
> getLastModified() is returning the right timestamp, then everything's OK.
>                                         -- Bill K.
> -----Original Message-----
> From: David Treves []
> Sent: Tuesday, July 17, 2001 1:40 AM
> To: tomcat-user
> Subject: problems serving HTTP requests
> Hi, I searched the archives yet didn't find anything can help me... I
> installed the Tomcat 3.2.2 in an out-of-process mode with IIS 5, for some

> time it worked just fine. Today Tomcat decided it is on a strike... I
> get any servlet/jsp file served by it. Instead I get the option to
> the file I request and the files are filled with gibberish.
> The Tomcat's DOS window doesn't print any error and I see in the IIS log
> that the request went fine (08:15:19 GET
> /jakarta/isapi_redirect.dll 200) a few times (even though I saw no
> and some times I got 206 HTTP message or 304.
> What could make the sudden change?
> Thanks in advance!
> David.

View raw message