Follow up:
Well I screwed up, but at least now I know it!
The 303 status code did give me the result I wanted, but after I removed
the bug which caused the problem, I no longer need to use it. (I had a
global variable which was previously set and latter caused my REDIRECT to
cycle right back to the previous REDIRECT location. Kind of like a,
"REDIRECT pong bug". :-).
Sorry to have bothered you about this one, but I did learn something about
the http status codes and such.
>| Is there a way to tell the browser(s) not to make this same substitution
>in
>| the near future?
>| Or, is there a better way to do a one time only redirect from within a
>| dynamic page?
>
>I don't expect IE to do anything by the rules, but maybe you can experiment
>with sending an explicit Status: 303, as described on
>http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.4
>
Yes, the 303 status code is exactly what I needed. I also tried setting
the "Expire" time to a negative and a small positive time in conjunction
with the "normal" REDIRECT (302) status return code, but IE 5 still did not
hack the response favorably.
I hope that SEE_OTHER {302} can be added to mod_perl's:
FakeRequest.pm
for future reference.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
