- From: Justin Chapweske <justin@chapweske.com>
- Date: Mon, 6 Nov 2006 16:03:36 -0600
- To: Lisa Dusseault <lisa@osafoundation.org>
- Cc: Henrik Nordstrom <hno@squid-cache.org>, Jamie Lokier <jamie@shareable.org>, HTTP Working Group <ietf-http-wg@w3.org>
I think you guys are too quick to state that Squid and Apache define the entire HTTP world. There are a lot of load balancers, switches, content delivery networks, etc. out there that make use of these features and continue to improve their support over time. On Nov 4, 2006, at 1:14 PM, Lisa Dusseault wrote: > Sounds like a trigger to at least consider obsoleting, dropping or > deprecating the feature. > > Lisa > > On Oct 22, 2006, at 5:22 AM, Henrik Nordstrom wrote: > >> >> What we see today is that neither component really cares. Most >> servers >> forgets to send Vary headers when they should, instead using no- >> cache to >> solve the problem. And most caches sees Vary too complex and reads it >> the same as no-store, or in some user-agent cases reads Vary >> wrongly as >> "no-cache" (need to revalidate on every request) and additionally >> getting the validation completely wrong. >
Received on Monday, 6 November 2006 22:03:51 UTC