Originally Posted by Kewangeder
Naive question: what stops a reasonably savvy browser from caching most of that XSL, JS, and CSS data after the first retrieval?
|
Looking at the HTTP headers returned when fetching mini-search-templates.xsl, it appears that they're setting a few headers relating to web caching:
Date: Thu, 24 Jan 2008 01:32:50 GMT
Server: Apache
Last-Modified: Fri, 11 Jan 2008 19:27:36 GMT
Cache-Control: max-age=259200
Expires: Sun, 27 Jan 2008 01:32:50 GMT
It appears that they're doing the right thing and setting stuff like
Cache-Control and
Expires on that more "static" content.
I asked a friend who is a web caching guru; his response:
|
Generally, they shouldn't (with a lot of caveats) consider it stale until after the freshness lifetime (which uses the Date, Cache-Control and Expires headers as input). It may still try to re-*fetch* it if it gets pushed out of cache.
|
Given that, the browsers should be doing the right thing and caching the those particular files.
Another thought; those HTTP headers indicate that the server claims to be Apache.
Unless the armory is fronted by a transparent redirector, I'm not surprised that there are performance problems; in the past Apache has been shown to top out at about 4000 connections per second, and given each Armory request may result in up to 100-200 requests based on what Kalroth wrote, that may explain some of the performance issues we see.