Amos Jeffries wrote: [dd] > > I dont think anything is wrong wth either. Its more a collision in how > the features work vs the protocols. > > Cache Digests (CD) are exchanged periodically and updated approx hourly. > Also they are based on just the URL. So there is always a gap where they > may not be accurate for any highly volatile objects, and variant objects > (using Vary headers) will have a high false-positive rate. > > only-if-cached requires the *right now* state of the object to be fresh > and in cache. It takes account of both the URL and the entire HTTP > headers. So > > The ICP protocol used as a backup to confirm objects existence also > suffers the same URL basis problem as CD. They work fine for HTTP/1.0 > but HTTP/1.1 features dont fare quite so well. Thank you Amos, now I understand the mechanics behind this. However, I'd prefer that users do not receive this frustrating error in a setup with has nothing inherently wrong about it (especially frustrating is the fact that they receive the error from the wrong proxy server, not the one they have configured in the browser settings). Do I understand correctly that the only way to avoid this error message is to switch to HTCP (and ditch both ICP and CD)? -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:sudakov@xxxxxxxxxxxxxxxx _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
