sidki's config set: 2005-06-09

[sidki3003]

z12 Wrote:Also at w3.org, the "Content-Location: Show real Onsite URL " filter kicks in often. When this filter matches, the response won't cache. At w3.org, clicking on the css link loads several css files that won't cache.

Any thoughts on this?

The server isn't sending any conditional caching headers, nor does it accept any. Even when unticking the Content-Location filter, i get:

Code:

GET 1827 : Cache-Control killed: max-age=0
GET 1827 : If-None-Match: prxETag stripped: oth
GET 1827 : Time: 14:41:13::160

+++GET 1827+++
GET /StyleSheets/Core/Oldstyle HTTP/1.1
Host: www.w3.org
User-Agent: Mozilla/5.0 (Windows NT 5.0; U; rv:1.7.7) Gecko/20050414 Firefox
Accept: text/css,*/*;q=0.1
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip, x-gzip, deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Referer: http://www.w3.org/Style/CSS/
If-Modified-Since: Tue, 10 May 2005 12:40:46 GMT
Connection: keep-alive
Client-IP: 66.80.139.114
Via: 1.1 none:8016 (Topproxy-2.0/), 1.1 athe736a (NetCache NetApp/5.5R4D2)
X-Forwarded-For: 66.80.139.114

RESP 1827 : Cache-Control replaced: max-age=21600
RESP 1827 : Expires killed: Tue, 10 May 2005 18:41:13 GMT
RESP 1827 : Last-Modified added
RESP 1827 : Vary killed: negotiate
RESP 1827 : Time: 14:41:13::711

+++RESP 1827+++
HTTP/1.1 200 OK
Date: Tue, 10 May 2005 12:41:13 GMT
Server: Apache/1.3.33 (Unix) PHP/4.3.10
Content-Location: Oldstyle.css
TCN: choice
P3P: policyref="http://www.w3.org/2001/05/P3P/p3p.xml"
Cache-Control: public, max-age=86400
Transfer-Encoding: chunked
Content-Type: text/css
!URL-ID: http://www.w3.org/StyleSheets/Core/Oldstyle
!Z12-Debug: oth
ETag: prx-CT:oth;
Last-Modified: Tue, 10 May 2005 12:41:13 GMT
+++CLOSE 1827+++

"max-age=86400" seems to work, with and without the Content-Location filter being active: That CSS doesn't appear in the log on revisit. Hard to be really sure about that tho...


One more thing about XHTML caching. While at W3.org, i remembered that i'm changing the Content-Type with "Content-Type: 3 Sel. XML to text/html" like:

Code:

Content-Type: text/html; charset=utf-8; PrxMsg=Changed - Filterable XML: application/xhtml+xml

I was thinking about what way to choose back then: Changing the Content-Type or testing for XHTML in the web filters. I ended up with former because i'm lazy, but also because the $TYPE(htm) test is much faster than any (let alone wildcarded) $IHDR test. So there is no need to include *xml* in the Content-Type check of the caching filters, or did i miss something here?

edit: There is another way to include XHTML for web filters: Testing for e.g. text/html and application/xhtml+xml just once, setting a var hFilter:1, and let the web filters test for this var instead of $TYPE(htm). But i guess i'll leave that for the moment when it becomes necessary.

sidki