Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sending redirection should make sure it doesn't get cached by browsers #84

Open
GoogleCodeExporter opened this issue Jan 8, 2016 · 0 comments

Comments

@GoogleCodeExporter
Copy link

Otherwise, problems could arise. I suggest that the framework's header sending 
code does the following prior to sending the redirection headers:

header("Cache-Control: no-cache, must-revalidate"); // HTTP/1.1
header("Expires: Sat, 26 Jul 1997 05:00:00 GMT"); // Date in the past

Original issue reported on code.google.com by roman...@gmail.com on 25 Oct 2012 at 1:50

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant