Merge lp://staging/~tribaal/squid-deb-proxy/refresh-ims into lp://staging/squid-deb-proxy
Proposed by
Chris Glass
| Status: | Merged | ||||
|---|---|---|---|---|---|
| Merged at revision: | 124 | ||||
| Proposed branch: | lp://staging/~tribaal/squid-deb-proxy/refresh-ims | ||||
| Merge into: | lp://staging/squid-deb-proxy | ||||
| Diff against target: |
16 lines (+3/-3) 1 file modified
squid-deb-proxy.conf (+3/-3) |
||||
| To merge this branch: | bzr merge lp://staging/~tribaal/squid-deb-proxy/refresh-ims | ||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| squid-deb-proxy-developers | Pending | ||
|
Review via email:
|
|||
Description of the change
This branch adds "refresh-ims" options to the refresh patterns for index files.
The reason for this is that archives usually set a cache-control header on them, and so in some cases the proxy will have mismatching indexes/packages (I see "Hash sum mismatch" errors when this happens).
The proposed change tells squid to forward the request upstream if it has a If-Modified-Since header (that apt sets), and so we let the upstream archive decide if the cache is fresh or not.
Since it answers only a simple 304, bandwidth overhead is minimal, and that prevents users from seeing errors in this rare but possible case (we see his more often on automated system deployments, obviously).
To post a comment you must log in.
Preview Diff
[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
