Darin Fisher wrote:
> 
> we had a long debate on this and the fact of the matter is that we must
> honor 'cache-control: no-cache' on back/forward.  this is unfortunate
> because the spec would allow us to not do this, but unfortunately many
> important web servers depend on this behavior, and would block mozilla
> from accessing their web servers if we didn't implement back/forward in
> this manner.

Why do they depend on this and why would they block Mozilla?

I find this behaviour *extremely* annoying, both as an end-user (why
doesn't the stupid back button work when I'm offline?!?) and as a
webmaster (I store some data in the session cookie when this page is
loaded, therefore we will get into trouble later if this page is
retrieved from cache, but I can't send a header telling the browser not
to cache it 'coz then the friggin' back button won't work!!!).

/Jonas

Reply via email to