durusmail: quixote-users: Redirect "caching", mozilla...
Redirect "caching", mozilla...
Redirect "caching", mozilla...
Hugo van der Merwe
2003-06-30
I have one page (url A), which contains a form, submitted to url B via
POST, url B presents another form, which, when submitted (also to url
B), performs the required action, then redirects back to url A. (url A
is not under my control, not part of my quixote app.)

I'm now getting the odd effect that when I click on the link
submitting the form at url A a second time, I just get A again,
reloaded. _q_lookup is called for url B, my page rendering code is
called, the apache logs seem to indicate (by page size) that the page
page is being returned properly, with status code 200, why would
mozilla take be directly back to url A then?

Is there some elegant way I can fix this in my code? I use
request.redirect, I see from the http_response.py code that it
apparently does turn off caching, and it does return temporary
redirect, not permanent. Any ideas?

Thanks,
Hugo van der Merwe

reply