"Garfield, Ben" wrote: > > 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. > >
By 302 I meant the http return code, from the server to the browser, but also logged in the http log. It is used to redirect the browser to another URL. This is defined in the http spec and it's hard to believe iPlanet would do something that dumb, though I guess I could be convinced . . . does iplanet actually say something about this in their documentation? It seems like a mistake somehow, not something you would do on purpose. And we've had similar (header) problems with JRun before. Also, our problems with the 302 are mainly on dynamic content from JRun---stuff that isn't cached and most times isn't even coming off a disk (it's in a database). Regards, ______________________________________________________________________ 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
