Closed Bug 166787 Opened 23 years ago Closed 23 years ago

Caching does not (always) check original for changes

Categories

(Camino Graveyard :: General, defect)

Product:
Camino Graveyard
Component:
General
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: jnp, Assigned: saari)

Details

(Whiteboard: cannot confirm)

On a webserver, create a directory with an index.html like the following: wget http://w1.1757.telia.com/~u175700445/ Go to the directory and be redirected. Now delete the index.html Go to the directory and be redirected again! It seems that the erver is not being contacted any longer (until flushing the cache) Build: 2002090405
Please test this with Mozilla, rather than chimera. If it happens in Mozilla too, it should be a Mozilla bug.
Does not happen in Mozilla 1.1 (Cache setting: check every time)
Reporter, you need to compare to Mozilla 1.0.1 rather than 1.1, as Chimera is currently based off the Mozilla 1.0.1 branch. If you can reproduce this with Mozilla 1.0.1, then this is not a Chimera bug.
Does not happen with Mozilla 1.0.1
Whiteboard: cannot confirm
I see that the status changed to 'cannot confirm'. However, I still get the described behaviour with Build ID: 2002121604. Is there a way I can help find the cause of this problem?
Re: Comment #5 From Jørgen Nørgaard 2002-12-16 13:04 ------- > I see that the status changed to 'cannot confirm'. That's because I currently don't have the time to test this on both Mozilla 1.0.1 and Chimera, and there does not seem to be anyone else to care about this bug (apart from smfr, who is probably too busy). So I've put it on the "later" stack for now.
Isn't this the exepected behaviour, unless you quit and restart chimera? Our default cache settings are to check the net 'once per session', so unless the index.html has no-cache meta information, we'll just assume it's there the second time.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
I just checked it with a plain html file and it seems that Chimera checks modification time for a plain file at every access (reload or entering the URL certainly), even if supposedly cached already. The behaviour I prefer btw.
You need to log in before you can comment on or make changes to this bug.