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,
______________________________________________________________________
Your ad could be here. Monies from ads go to support these lists and provide more
resources for the community. http://www.fusionauthority.com/ads.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
