lör 2007-12-29 klockan 10:42 +0100 skrev Werner Baumann: > I have no idea what this would be. Can you give a *short* outline? > Please note: The weak Etags generated by Apache will *never* match. So > the only way I see, how Apache's weak Etags could be used, is to ignore > the weakness indicator, as I do in davfs2.
Intermediaries is proxies etc. These do their own condidionals processing, and some do follow the RFC and allows for weak etags to be used in conditionals. Clietn -> Squid -[internet]-> Apache the object in question is having a weak ETag but significant freshness assigned to it via mod_expires or similar. object gets cached by Squid & client with a weak etag client later issues an IF-None-Match request to Squid using the weak ETag. Squid considers the object still fresh and responds with 304. Regards Henrik
