Hi there, WRT to the Expires header: http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.21 HTTP/1.1 clients and caches MUST treat other invalid date formats, especially including the value "0", as in the past (i.e., "already expired"). Cheers Ken > -----Original Message----- > From: thelist-bounces at lists.evolt.org [mailto:thelist- > bounces at lists.evolt.org] On Behalf Of Bill Moseley > Sent: Tuesday, 6 May 2008 10:46 AM > To: thelist at lists.evolt.org > Subject: Re: [thelist] Prevent Caching in IE > > On Tue, May 06, 2008 at 10:38:44AM +1000, Ken Schaefer wrote: > > Cache-Control: no-cache should be enough to get browsers to stop > caching content. > > It should be, but IE was still returning a previous page even with > that header. Maybe it was the post- or pre-check breaking things, not > sure. > > > An invalid Expires header value (e.g. -1) is interpreted to be > > "expires immediately", which is why using an invalid value like -1 > > causes the page to expire (and IE to get a new copy) > > So, it's OK to use -1 in the Expires header? I didn't see in the http > spec that was allowed. > > > Thanks, > > -- > Bill Moseley > moseley at hank.org > > -- > > * * Please support the community that supports you. * * > http://evolt.org/help_support_evolt/ > > For unsubscribe and other options, including the Tip Harvester > and archives of thelist go to: http://lists.evolt.org > Workers of the Web, evolt !