[Varnish] #795: Conditional GETs based on modification time are not honored if Last-Modified was not explicitly set
Varnish
varnish-bugs at varnish-cache.org
Fri Oct 15 23:05:02 CEST 2010
#795: Conditional GETs based on modification time are not honored if Last-
Modified was not explicitly set
------------------+---------------------------------------------------------
Reporter: runa | Type: defect
Status: new | Priority: normal
Milestone: | Component: build
Version: 2.0 | Severity: normal
Keywords: |
------------------+---------------------------------------------------------
Varnish should add a last-modified (or at least set
sp->obj->last_modified) of/to now if it doesn't get one from the backend.
{{{
> GET / HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-pc-linux-gnu) libcurl/7.19.7
OpenSSL/0.9.8n zlib/1.2.3.3 libidn/1.15
> Host: www.x.com
> Accept: */*
> If-Modified-Since: Fri, 15 Oct 2010 20:09:12 GMT
< HTTP/1.1 200 OK
< Server: nginx/0.7.65
< Date: Fri, 15 Oct 2010 20:08:24 GMT
< Content-Type: text/html; charset=utf-8
< Connection: keep-alive
< Status: 200 OK
< X-Runtime: 37
< ETag: "735c2070da36d7ee8c24e57f4b0dbc88"
< Content-Length: 8356
< Cache-Control: max-age=86400, s-maxage=3600
< X-Varnish: 1825324525 1825143446
< Age: 31573
< Via: 1.1 varnish
< X-Cache: HIT
}}}
--
Ticket URL: <http://varnish-cache.org/trac/ticket/795>
Varnish <http://varnish-cache.org/>
The Varnish HTTP Accelerator
More information about the varnish-bugs
mailing list