On Wed, Feb 26, 2003 at 12:07:56PM +0259, Kir Kolyshkin wrote: > I'm just realized that the implementation is probably buggy, as m_period is > overwritten later, in UpdateUrl or UpdateLongUrl. Can you please check it, > and if that doesn't work, submit a report to bugzilla?
Yes, I'll do that. But why not allow expiry dates less than Period? For example, I want to set the Expires header only for pages which need to be expired right away or which need to stay in web caches for a certain amount of time. For other pages, I set Last-Modified. So the browser or search engine can refetch the page if it has expired or ask the server if there is a more recent version available. Most static content never expire, but the HTTP/1.1 standard says servers SHOULD NOT send expiry dates more than a year in the future. The document (http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html) also says that "never expires" mean one year from the date of request.
pgp00000.pgp
Description: PGP signature
