- 12 Sep, 2016 26 commits
-
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
Follow-up 9095c5cf Belongs to #2057
-
Nils Goroll authored
Follow-up 9095c5cf Belongs to #2057
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
Downstream packages can always replace it with a different version. End-users can override it in their `/etc` tree.
-
Dridi Boukelmoune authored
By default: /usr/share/vcl This directory becomes a drop-in, and standard location for library-like VCL files. It streamlines third-party VCL packaging, offering a blessed for installation, leaving the canonical /etc/varnish directory entirely to the end-user. While it is common to see VMOD packages in the wild, there are some VCL libraries (sometimes backed by VMODs) that would benefit some form of standardization. It then becomes possible to install packages, and use relative includes that JustWork(tm). This is especially true for VCL libraries that are split into several files, they can put themselves in a subdirectory in /usr/share/vcl and use it as a namespace for includes between files of the library: # somewhere in my awesome "foo" library include "foo/some_feature.vcl" Choosing a default path of `/etc/varnish:/usr/share/vcl` prevents VCLs dropped in the system from shadowing end-users VCLs but at the same empowers said users to override a "standard" VCL in their `/etc` tree, with no additional parameters fiddling.
-
Poul-Henning Kamp authored
-
Nils Goroll authored
Follow-up 9095c5cf Belongs to #2057
-
Federico G. Schwindt authored
-
Federico G. Schwindt authored
-
Federico G. Schwindt authored
-
Federico G. Schwindt authored
E.g. set req.http.foo = req.http.foo + req.http.bar ~ "foobar"
-
Federico G. Schwindt authored
-
Nils Goroll authored
Noticed that I've been missing this since the beginning of time when porting some ancient inline-C. We already have obj.uncacheable und obj.hits in vcl_deliver, so not having these seems arbitrary. Copying out the values in vcl_hit just to have them available in vcl_deliver, as it was possible previously, implies unnecessary overhead. One use case is to extend object lifetime downstream when delivering a stale object, e.g. sub vcl_deliver { if (! obj.uncacheable && obj.ttl < 0s) { set resp.http.Expires = now + 1m; set resp.http.Cache-Control = "public, max-age=60"; unset req.http.Age; } } merges #2057
-
Nils Goroll authored
-
Poul-Henning Kamp authored
-
Nils Goroll authored
... demonstrating that the PRIV_* states are per vmod, no matter if accessed from a function or method Fixes #1800 part of #2061
-
Nils Goroll authored
Part of #2061
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
- 11 Sep, 2016 3 commits
-
-
Federico G. Schwindt authored
-
Federico G. Schwindt authored
-
Federico G. Schwindt authored
Related to #2025.
-
- 10 Sep, 2016 11 commits
-
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Federico G. Schwindt authored
With input from nigoroll.
-
Federico G. Schwindt authored
-
Federico G. Schwindt authored
These versions implement previous drafts that will fail the upgrade.
-
Federico G. Schwindt authored
-
Poul-Henning Kamp authored
platforms
-
Poul-Henning Kamp authored
cost by correctly holding the mtx while examining it.
-
Poul-Henning Kamp authored
It's amazing how long time it can take to spot a bug like this :-(
-
Poul-Henning Kamp authored
See also: #2061
-
Poul-Henning Kamp authored
-