Richard Dobson wrote:
No it is perfectly valid to have body content when doing a 302 redirect, usually the default apache 302 redirects contain a body which displays a message such as "This page is now located at ..." to support very old browsers that dont know about 302 redirects and gives the user the information they need to get to where they are wanting to go.It would stand to reason that those same "very old browsers" would not know what to do with gziped data - so if the idea is to be portable, then the data following a 302 should not be gzipped. Of course, IE6 should be able to figure this out...
I dont understand what you are trying to get at here? Default apache behaviors have nothing to do with PHP.True, but the design of one influences the design of the other. Missing the trailing slashes with Apache is a know problem, which only becomes evident if your apache hostname differs from your actual DNS hostname.
Otherwise the redirects happen "silently" and most people never know the difference. My point was that something similar could be happening in PHP as well.
I'd be tempted to look for 302's in the server logs, might give a clue.
-R
_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
