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 <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx