fre 2009-07-03 klockan 00:27 +1200 skrev Amos Jeffries: > Henrik, > do you know what change(s) need to be made or ported make this work? > > http://www.squid-cache.org/bugs/show_bug.cgi?id=2624
Ugh.. that's a rather bad one.. Don't think there is anything that needs to be ported. Smells unique to Squid-3 to me, probably from refactoring of the 304 processing. Needs to keep close track if the conditional (If-Modified-Since/If-None-Match) is set by Squid or the client and select to respond with 304/200 as appropriate. Any returned ETag is also very valuable in this as it allows verification if the cached entity is current or not regardless of how the validators were set up. The closest Squid-2 change I can remember is the ETag addition, which rewrote 304 processing and If-None-Match quite a bit. Hmm.. looking at the request traces I notice that Squid-3 do not even send If-None-Match with the cached objects etag. That's a good start, but not the actual cure (just improves things considerably). I think this was added to Squid-2 some time during 2.6, but probably easier to just reimplement these things than trying to port from squid-2. It's a reasonably good idea to look into processing received If-None-Match conditionals as well as part of that if not done already. Regards Henrik
