Hi, My name is Mati and I study computer sciense at Warsaw Uniwersity.
Together with Michal Matusiak, who I believe introduced himself earlier, I want to contribute to squid. Our area of interests is ETag support in squid 3. That's enough about me. I have a question concerning semantics of ETags. During our tests with etag-patched squid 2.5 we discovered some differences between squid's behavior and rfc2616... One of them is major. I would like to know whether this difference is based on some considerations about nature of ETags and therefore should be ported to squid 3, or not... section 13.3.4 of rfc2616 states: "proxy, upon receiving a conditional request that includes both a Last-Modified date and one or more entity tags as cache validators, MUST NOT return a locally cached response to the client unless that cached response is consistent with all of the conditional header fields in the request" We understand that if request has both If-Modified-Since and If-None-Match, squid should return cached responce if the validation holds true for both conditional headers. But, patched squid 2.5 returns cached response if either of conditional headers validates correctly... Is it correct? Are there some other documents or opinions (beside rfc2616) justifying this difference? best wishes, Mati.
