Reporter, can you provide a test URL ? According to bug 94121 and bug 112564 it should work. It should be revalidated when it becomes stale (expires), regardless of your cache-options. But I think that the key point is the expiration. If your image contains an expiration-date in the future, it won't be revalidated every time you try to display the image. The 'must-revalidate' just prevents the browser and/or cache to enforce its own options (like 'validate never'). See RFC2616, section 14.9.4
Assignee: general → darin
Component: Browser-General → Networking: HTTP
QA Contact: general → httpqa
Note that having no expiration date header is equivalent to a expiration in the future (1/10 of the time since last-modified, in fact).
You are correct, I misunderstood the specs for must-revalidate. After adding max-age=0 I got the behavior I desired. Sorry for the false alarm.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.