> Brilliant resource! Thank you for that. > > The problem stems from the cookie mechanism: > > "This object will be considered stale, because it doesn't have any > freshness information assigned. It doesn't have a validator present. > This object requests that a Cookie be set; this makes it and other pages > affected automatically stale; clients must check them upon every > request. It doesn't have a Content-Length header present, so it can't be > used in a HTTP/1.0 persistent connection." > > I'm not sure how to get around this. Any suggestions? > >
- You can't , that's how the http standard is defined when handling caching parameters concerning objects with Cookie's attached. M.
