Re: [us...@httpd] mod_expires > Why are both the Expires and Cache-Control HTTP headers set?
On 10 May 2010, at 23:37, Geoff Millikan wrote: >> The HTTP spec linked below says, "Servers specify explicit >> expiration times using *either* the Expires header, or >> the max-age directive of the Cache-Control header." >> >> So why then does mod_expires set *both* the Expires HTTP >> header *and* the max-age directive of the >> Cache-Control HTTP header? It's overkill to set >> both, right? It's a cousin of (half of) Postel's law: be careful in what you send. If the server sets both headers, it maximises the chance of an unknown client understanding at least one of them. -- Nick Kew - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org " from the digest: users-digest-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [us...@httpd] mod_expires > Why are both the Expires and Cache-Control HTTP headers set?
On Mon, May 10, 2010 at 6:37 PM, Geoff Millikan wrote: >> The HTTP spec linked below says, "Servers specify explicit >> expiration times using *either* the Expires header, or >> the max-age directive of the Cache-Control header." It later talks about times when you might want to set them to different values, so I wouldn't interpret "either" as not allowing both. >> So why then does mod_expires set *both* the Expires HTTP >> header *and* the max-age directive of the >> Cache-Control HTTP header? It's overkill to set >> both, right? It's been like that in mod_expires for more than 10 years, perhaps there were clients that knew Cache-Control but not Expires (and 1.0 clients that have the other side) -- Eric Covener cove...@gmail.com - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org " from the digest: users-digest-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
RE: [us...@httpd] mod_expires > Why are both the Expires and Cache-Control HTTP headers set?
Is this the wrong forum for this question? > The HTTP spec linked below says, "Servers specify explicit > expiration times using *either* the Expires header, or > the max-age directive of the Cache-Control header." > > So why then does mod_expires set *both* the Expires HTTP > header *and* the max-age directive of the > Cache-Control HTTP header? It's overkill to set > both, right? > > http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.2.1 > > http://httpd.apache.org/docs/2.2/mod/mod_expires.html > > Thanks, > > http://www.t1shopper.com/ > > PS. It would be great if mod_expires had a Directive something like > "ExpiresHeader" where the syntax could be something like > Expires|Cache-Control|All > smime.p7s Description: S/MIME cryptographic signature
[us...@httpd] mod_expires > Why are both the Expires and Cache-Control HTTP headers set?
The HTTP spec linked below says, "Servers specify explicit expiration times using *either* the Expires header, or the max-age directive of the Cache-Control header." So why then does mod_expires set *both* the Expires HTTP header *and* the max-age directive of the Cache-Control HTTP header? It's overkill to set both, right? http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.2.1 http://httpd.apache.org/docs/2.2/mod/mod_expires.html Thanks, http://www.t1shopper.com/ PS. It would be great if mod_expires had a Directive something like "ExpiresHeader" where the syntax could be something like Expires|Cache-Control|All smime.p7s Description: S/MIME cryptographic signature
