Updates:
Summary: Cache not invalidated correctly on cookie changes?
Cc: da...@chromium.org w...@chromium.org
Comment #1 on issue 7538 by pkast...@chromium.org: Cache not invalidated
correctly on cookie changes?
http://code.google.com/p/chromium/issues/detail?id=7538
Wait a minute. This may not be cookies, it may be something with our cache.
I just reloaded that internal page again and went to go set my location,
and found it
already set (!). So I clicked "save settings" and got the version of the
page with
the location set. Then I closed it again and typed the address again to
reopen, and
got the non-cookied version; hit reload and got the with-cookie version;
and then
closed and reopened and got the with-cookie version.
So my hypothesis is that when I got the newer version of the page after
setting the
cookie, that should have evicted the old version in our cache, but it
didn't, and
continued to not evict it until after I reloaded manually. The reason that
I've seen
this when closing and reopening quickly is because if you wait long enough
the
resources in the cache pass their expiry time.
CCing people who understand the cache more.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
