73417 - New cache doesn't do an initial out-of-date check

Status: VERIFIED DUPLICATE of bug 73099

(Core :: Networking: Cache, defect)

Description

[tor]

The new cache, with "once per session", doesn't check if the disk cache
copy is out of date during the first visit of a session.  Steps to
reproduce:

  * start mozilla
  * visit http://news.bbc.co.uk/
  * quit mozilla
  * kill a couple hours
  * visit http://news.bbc.co.uk/ with another browser to make sure it changed
  * start mozilla
  * visit http://news.bbc.co.uk/
  * read out-of-date news

Comment 1

[Brandon Hume]

I'm seeing this on Solaris/SPARC (build id 2001032521) as well.

Comment 2

[neeti]

-->gordon

Comment 3

[gordon]

This is an http issue, not a cache issue.

Comment 4

[Darin Fisher]

this is only a problem with cache validation set to "once per session"

Comment 5

[Darin Fisher]

for some reason, the last modification time on the cache entry is always in
the future (ie. after the session start time), hence "once-per-session" ends
up meaning validate never.  i'm not sure why the last modified time stamp
is being updated... investigating.

Comment 6

[Darin Fisher]

*** This bug has been marked as a duplicate of 73099 ***

Comment 7

[Tom Everingham]

verified