This repository has been archived by the owner on May 25, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 37
Improve Varnish config #85
Milestone
Comments
stevenrombauts
pushed a commit
that referenced
this issue
Aug 29, 2016
Although we simply return(pass) in vcl_fetch() when we disabled Varnish, headers are still being modified in vcl_backend_response(). We should return(deliver) if Varnish disabled.
stevenrombauts
pushed a commit
that referenced
this issue
Aug 29, 2016
If you skip the built-in subroutine and set 0 as TTL value, you are effectively removing objects from cache that could eventually be used to avoid request serialization. See: http://book.varnish-software.com/4.0/chapters/VCL_Basics.html\#vcl-backend-response
stevenrombauts
pushed a commit
that referenced
this issue
Oct 16, 2017
Although we simply return(pass) in vcl_fetch() when we disabled Varnish, headers are still being modified in vcl_backend_response(). We should return(deliver) if Varnish disabled.
stevenrombauts
pushed a commit
that referenced
this issue
Oct 28, 2017
stevenrombauts
pushed a commit
that referenced
this issue
Oct 28, 2017
stevenrombauts
pushed a commit
that referenced
this issue
Oct 28, 2017
stevenrombauts
pushed a commit
that referenced
this issue
Oct 28, 2017
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The VCL should be made smarter:
Cache-Control: no-cacheheader (code). Only if Varnish cache is effectively enabled. (Related to Do not modify headers in backend response #52) Note: also not if a user is logged in, but we don't have any logic for this because Joomla always sets a session cookie.The text was updated successfully, but these errors were encountered: