Re: Choosing proxy on location

In a previous episode Adrian Chadd said...

:: You can't be guaranteed that the origin server you're talking to *IS*
:: an origin server.

you have to be sure of that.. not only for cache-control but
potentially some response codes (like proxy authentication
required).. things you'd never implement if you didn't support proxy
communication.. which you're not required to do.

:: Take, for example, a cluster of http accelerators in front of a web
:: server. I know a lot of people who do this, and wondered why people
:: were seeing 'stale' data from the accelerators even with shift-reload.
::

not the same thing at all. clusters made with accelerators are just
gateways and the whole cluster becomes the origin server.. because it
is responsible for 'owning' the data.. the admin of that origin server
(as with any OS) is responsible for what gets sent when.. in any sane
deployment when 'source content' gets changed the cache entry is
cleared (which is possible because the cache is not a third party
unknown entity like a normal cache setup).. anything else is just a
misconfiguration (aka design bug).

-P
Received on Sun Nov 14 1999 - 11:24:00 MST