Re: Work Around For COmmunicator

On Thu, 10 Jul 1997, Marc van Selm wrote:
> I've also wondered why microsofts home gives us a shitty hit-rate. It's very
> popular (I wonder why) and a low hit-rate: this is not normal.

Yesterday:
# Request-Peak by 2ndlevel-domain Request % kByte % Hit-%
----------------------------------------- ------- ------ -------- ------ ------
206.64.127.* 3606 10.07 21048 6.55 19.94
*.microsoft.com 3156 8.81 7861 2.45 73.48

Day before:
# Request-Peak by 2ndlevel-domain Request % kByte % Hit-%
----------------------------------------- ------- ------ -------- ------ ------
206.64.127.* 2256 7.92 17063 8.35 16.05
*.microsoft.com 1343 4.71 6358 3.11 67.46

> Guess what I've found: an expires header on many of their pages with the
> expires time almost the same as "now"....

I think what's helping to get my *.microsoft.com hit rate up to
high-sixty/low-seventy percent is the refresh_pattern suggestion made on
this list about a week ago, where images and movies and the like have much
more stringent refresh rules attached to them. In examining a number of
Microsoft's pages, it looks to me like the ones that they're marking to
expire immediately are the *.asp files that do the custom page-building,
and the various articles, and the custom-home-page things, but not the
images, and the images are the bulk of the bytes.

> A good discussion though: What would be nice is some settings in the config
> to force a minimal caching-time and/or IMS based on url/site (also when the
> server tries to prevent caching via expires headers and users try to force a
> reload). This way we could improve the hit rate on low importance /
> frequently used sites.

You can do this with refresh_pattern, here's a small sample of what I
have:

refresh_pattern/i ^http://.*\.jpeg$ 10080 90% 40320
refresh_pattern/i ^http://.*\.jpg$ 10080 90% 40320
refresh_pattern/i ^http://.*\.zip$ 10080 90% 40320
refresh_pattern/i ^http://.*\.exe$ 10080 90% 40320

You could also stick in:

refresh_pattern/i ^http://.*\.microsoft\.com ... whatever ...

To apply more stringent refresh rules to only microsoft's sites. You'd
probably also want to add "*.msn.com" too.

        -Mike Pelletier.
Received on Thu Jul 10 1997 - 07:37:26 MDT