Darin Fisher wrote: > > Back/Forward should honor <meta> tags that specify the equivalent of > 'Cache-control: no-cache' If not, then it's a bug.
It should not! The HTTP/1.1 spec says: 13.13 History Lists User agents often have history mechanisms, such as "Back" buttons and history lists, which can be used to redisplay an entity retrieved earlier in a session. History mechanisms and caches are different. In particular history mechanisms SHOULD NOT try to show a semantically transparent view of the current state of a resource. Rather, a history mechanism is meant to show exactly what the user saw at the time when the resource was retrieved. By default, an expiration time does not apply to history mechanisms. If the entity is still in storage, a history mechanism SHOULD display it even if the entity has expired, unless the user has specifically configured the agent to refresh expired history documents. If the Back/Forward buttons honor Cache-control: no-cache, whether it's sent as a header or as a <meta> tag, that is a *major* bug. /Jonas
