I tested the URL that Andrzej mentions below. Sho 'nuf, the value of the
Expires: headers we send is exactly the same as the value of the Date: header.
RFC 2616 says the content can't be cached by proxies in this case.
[gregames@gandalf gregames]$ runsocks nc httpd.apache.org 80
HEAD /docs/mod/core.html HTTP/1.0
host: httpd.apache.org
HTTP/1.1 200 OK
Date: Tue, 22 Jan 2002 15:34:16 GMT
Server: Apache/2.0.29 (Unix)
Content-Location: core.html.en
Vary: negotiate,accept-language
TCN: choice
Accept-Ranges: bytes
Connection: close
Content-Type: text/html
Content-Language: en
Expires: Tue, 22 Jan 2002 15:34:16 GMT
but for many other URLs, we don't bother with the Expires: header
[gregames@gandalf gregames]$ runsocks nc httpd.apache.org 80
HEAD /index.html HTTP/1.0
host: httpd.apache.org
HTTP/1.1 200 OK
Date: Tue, 22 Jan 2002 15:44:37 GMT
Server: Apache/2.0.29 (Unix)
Accept-Ranges: bytes
Content-Length: 6139
Connection: close
Content-Type: text/html
Does anyone understand the care and feeding of Expires: headers in Apache?
Seems like it would be in our best interest to allow caching for most/all static
pages.
Thanks,
Greg
-------- Original Message --------
Subject: Two things (fwd)
Date: Mon, 21 Jan 2002 09:39:05 -0800 (PST)
From: Brian Behlendorf <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], <[EMAIL PROTECTED]>
Notice the 2nd issue.
Brian
---------- Forwarded message ----------
Date: Mon, 21 Jan 2002 12:55:17 +0100
From: Andrzej Kukula <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Two things
Hello.
I've got just two annoying things:
1. On www.apache.org, httpd.apache.org there's no mention on a general
contact concerning the Web Page, so I'm sending this message to well-known
address.
2. (Far more important) httpd.apache.org transmits the same Date: and
Expires: HTTP headers, thus making squid unable to cache your pages. I've
tested it with httpd.apache.org/docs/mod/core.html.
Regards,
Andrzej Kuku�a
