[Varnish] #1672: Assert on cached object with non-200 status and bogus 304 backend reply
Varnish
varnish-bugs at varnish-cache.org
Mon Feb 9 11:27:58 CET 2015
#1672: Assert on cached object with non-200 status and bogus 304 backend reply
----------------------+----------------------------------------
Reporter: martin | Owner: Poul-Henning Kamp <phk@…>
Type: defect | Status: closed
Priority: normal | Milestone:
Component: varnishd | Version:
Severity: normal | Resolution: fixed
Keywords: |
----------------------+----------------------------------------
Changes (by Poul-Henning Kamp <phk@…>):
* owner: => Poul-Henning Kamp <phk@…>
* status: new => closed
* resolution: => fixed
Comment:
In [021ffeef1dbb9510d147f080795a568253a1a13a]:
{{{
#!CommitTicketReference repository=""
revision="021ffeef1dbb9510d147f080795a568253a1a13a"
If the backend sends 304 to a non-conditional fetch, we should not assert
but fail the fetch.
Fixes #1672
Based mostly on patch from martin
}}}
--
Ticket URL: <https://www.varnish-cache.org/trac/ticket/1672#comment:3>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator
More information about the varnish-bugs
mailing list