The 302 code in iPlanet means that the web server used a cached version of
the file instead of reading it off of the hard drive on the server.
- Ben
-----Original Message-----
From: Christopher B. Hamlin [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 06, 2002 5:11 PM
To: JRun-Talk
Subject: Unexpected 302 return code?
Hi,
I'm asking this in hopes that someone knows something,
even though I don't know exactly where the problem lies.
We are sometimes in the (iplanet) http logs getting
requests that look completely like normal, completed
requests except that they have a status code of 302.
We're using JRun 3.0(sp2?).
For example, the size of the form returned by a
jsp call is the same as in a 200 return, but it has
a 302 code. Shouldn't this only be when a "Location"
header is sent back to send the client somewhere else?
And shouldn't the content length logged be (if any)
minimal?
Would "redirecting" "internal" to Jrun affect this?
For example:
RequestDispatcher dispatcher;
dispatcher =
getServletContext().getContext("/").getRequestDispatcher(somePage);
dispatcher.forward(req, res);
This almost never happens on non-JRun content, though
there are a couple.
I've looked at all our NSAPI code, the JRun connector
source code, our Java code, etc. I'm wondering if the
JRun server is sending it back through the connector,
and why/when.
Thanks for any ideas,
______________________________________________________________________
This list and all House of Fusion resources hosted by CFHosting.com. The place for
dependable ColdFusion Hosting.
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
