Why doesn't varnish cache these requests?

Andri Steiner | snowflake Hosting hosting at snowflake.ch
Tue Jan 26 17:35:18 CET 2016


Hi Rainer,

>> GET /the_url/ HTTP/1.1
>> Host: the_server
>> User-Agent: curl/7.46.0
>> Accept: */*
>>
> < HTTP/1.1 200 OK
> < Server: nginx
> < Date: Tue, 26 Jan 2016 15:30:39 GMT
> < Content-Type: text/html; charset=utf-8
> < Content-Length: 31195
> < Connection: keep-alive
> < Content-Language: de
> < Expires: Thu, 25 Feb 2016 15:07:05 GMT
> < ETag: "c8b13cf27951a887cd9e54f307456e2e"
> < Cache-Control: max-age=2590586
> < Pragma: public
> < TYPO3-Pid: 6
> < TYPO3-Sitename: 6a48956158576b1c9fcab0ff657e8ef8e337b750

I cannot see anything wrong with this response, the VCL checks on
beresp.http.TYPO3-Pid && beresp.http.Pragma == "public" which is both
fulfilled.

Can you share a varnishlog output of such a request?


> Note that varnish is on a different server than nginx.

Does not matter as it seems you have TYPO3 configured properly because
otherwise the TYPO3-* headers would not be there at all. BTW, you could
add your backend server to the "ban" ACL, without this the TYPO3 Backend
wont be allowed to purge the Varnish cache.

Cheers,
Andri



More information about the varnish-misc mailing list