hit-for-pass vs. hit-for-miss

[Poul-Henning Kamp]

--------
In message <4E80A314-241C-4566-B6BA-61B72DC2CAA6 at uplex.de>, Geoffrey Simmons wr
ites:

>That may indeed be unusual, but I see that a sad commentary on the
>state of web developers' knowledge about caching and HTTP. Not as
>somebody's peculiar requirement.

Oh, man, if you think that is a sad commentary, wait till I get started...

>It would strike me as rather odd if a caching proxy has to treat
>it as a special case when backends actually do something the right
>way (like always set Cache-Control to determine TTLs).

IMO the unusual detail, is that it takes several minutes to fetch
the object from the backend, and that people are trying to find
a way to mitigate/work around that special case.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.