Thank you for the suggestion. I changed the http headers directly from
On Jan 30, 11:58 pm, Gavin Peters (蓋文彼德斯) <
gav...@chromium.org> wrote:
> Unfortunately, Chrome doesn't respect caching META tags. Can you maybe
> change the HTTP headers directly to control caching?
>
> track this feature, so you'll know if it gets implemented.
>
> - Gavin
>
> On 30 January 2012 07:59, Tanvir Shaikh <
tan...@google.com> wrote:
>
>
>
>
>
>
>
> > Hi,
>
> > We have a website where we have implemented login/logout mechanism.
> > When we go to any page, if our session has expired, we are logged out.
> > When we sign in and go to the same page where our session expired, we
> > are shown the logout page again.
>
> > This is because the browser caches the pages. We added the following
> > headers in the HTML pages to stop the caching:
>
> > <META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE, NO-STORE, MUST-
> > REVALIDATE">
> > <META HTTP-EQUIV="PRAGMA" CONTENT="NO-CACHE">
> > <META HTTP-EQUIV="EXPIRES" CONTENT="0">
> > <META NAME="ROBOTS" CONTENT="NONE">
> > <META NAME="GOOGLEBOT" CONTENT="NOARCHIVE">
>
> > While this works on other browsers, Chrome is still caching the pages.
> > Please let us know if there is any way to stop the caching in Chrome.
>
> > We would prefer if the solution would be in the form of HTML or
> > Javascript or any client-side code, as many people use our site and
> > any manual changes to browser settings would not be feasible.
>
> > Thanks.
>
> > --