Caching responses with "Vary" header
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Squid |
Fix Released
|
High
|
|||
squid3 (Debian) |
Fix Released
|
Undecided
|
Unassigned | ||
squid3 (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Trusty |
Fix Released
|
Medium
|
Diogo Matsubara |
Bug Description
See the upstream bug report for more details [1], but it seems as though squid in trusty isn't caching any response which includes a vary header [2]. The upstream bug was fixed in 3.3.12 [3].
Steps to reproduce:
* Setup an application returning responses with "Vary: User-Agent"
* Add squid in front of an application server
* Make multiple requests to squid
Expected result:
* Second request is a Hit
Actual result:
* Second (and subsequent) requests are all misses.
Repeat without a Vary header and things are cached as expected. Note, I've only reproduced this with a specific setup (as in [2]), I've not yet reproduced with a simplified setup to be certain I'm seeing the upstream bug.
[1] http://
[2] http://
[3] http://
Related branches
- Sebastien Bacher: Needs Information
-
Diff: 88 lines (+68/-0)3 files modifieddebian/changelog (+7/-0)
debian/patches/91-caching-with-vary-3806.patch (+60/-0)
debian/patches/series (+1/-0)
Changed in squid3 (Ubuntu): | |
status: | New → Triaged |
Changed in squid3 (Ubuntu Trusty): | |
status: | New → Triaged |
Changed in squid3 (Ubuntu): | |
importance: | Undecided → Medium |
Changed in squid3 (Ubuntu Trusty): | |
importance: | Undecided → Medium |
tags: | added: bitesize |
Changed in squid: | |
importance: | Unknown → High |
status: | Unknown → Fix Released |
When objects retrieved from web server return with a vary header, object is never cached and all future requests are always logged as a MISS.
Disabling the vary header on web server causes the same object to be cached as expected.
Seems to be same issues as discussed here : http:// www.squid- cache.org/ mail-archive/ squid-dev/ 201207/ 0100.html