Back/Forward should honor <meta> tags that specify the equivalent of 'Cache-control: no-cache' If not, then it's a bug.
However, it is not a bug for content served up with 'Cache-control: no-cache' to be stored in the browsers cache. It is only a bug if it is used again without first validating the copy with the server. Netscape 6.2 and Mozilla cache nearly everything for the purposes of supporting View->Source, File->SaveAs, etc. without requiring another download. Try sending 'Cache-control: no-store' if you don't want the browser to ever hold onto a local copy. Darin Gavin Brelstaff wrote: > Jonas > Thanks for the suggestion but the > > <meta http-equiv="Cache-Control" content="no-cache"/> > > doesn't make any difference - perhaps it's a bug. > - FWIW here's the file I'm serving from Apache > (there's a server side include that provides the server-side > time shown on the page). > -- > <HTML> > <HEAD> > <meta HTTP-EQUIV="Pragma" CONTENT="no-cache"> > <meta HTTP-EQUIV="Cache-Control" CONTENT="no-cache"/> > <meta HTTP-EQUIV="Expires" CONTENT="0"> > <TITLE>Welcome to the demo</TITLE> > </HEAD> > <BODY> > Time: > <!--#config timefmt=" %H:%M:%S %a %b %d, %Y" --> > <!--#echo var="DATE_LOCAL" --> > <A HREF="junk.html">click</A> on this then > try the back button. > <HR> > </BODY> > </HTML> > -- > > > Jonas J�rgensen wrote: > >>Gavin Brelstaff wrote: >> >>>What should I do to emulate the behavior I get in IE5.5+ nd NS4.x >>>using >>><meta HTTP-EQUIV="Pragma" CONTENT="no-cache"> >>>in the <HEAD> section of my html page? >>>I'd like the page not to be cached at all. >>>Netscape 6.2 - still lists such pages in the session history >>>and then redisplays a cached version of them - i.e doesn't even >>>check with the server if the option is "Automatic". >>> >>>Is this by design? If so - other than going to SSL where I read that >>>nothing gets cached by default - what can I do? >>> >>Try <meta http-equiv="Cache-Control" content="no-cache"/>. >> >>/Jonas >> >
