- 26 Apr, 2017 1 commit
-
-
Denes Matetelki authored
Fixes: #2313 This is a back port of f1741d99 from master.
-
- 25 Apr, 2017 1 commit
-
-
Jonathan Huot authored
Conflicts: lib/libvmod_std/vmod.vcc lib/libvmod_std/vmod_std.c
-
- 24 Apr, 2017 2 commits
-
-
Dridi Boukelmoune authored
This should help diagnose #2253.
-
Poul-Henning Kamp authored
already failed. Fixes #2301
-
- 10 Apr, 2017 1 commit
-
-
Dridi Boukelmoune authored
Conflicts: configure.ac varnish.m4
-
- 07 Apr, 2017 1 commit
-
-
Pål Hermunn Johansen authored
-
- 06 Apr, 2017 11 commits
-
-
Martin Blix Grydeland authored
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
It shares a lot of parsing infrastructure with log records, but doesn't support the taglist syntax. Only a verbatim `vxid` token can be used as the LHS, and only integer operators are supported.
-
Pål Hermunn Johansen authored
There was a missing bracket that I fixed but forgot to amend the commit. Fixing with this one.
-
Reza Naghibi authored
By rounding Age down, we make sure Age < max-age while the object is fresh. Otherwise, we can prematurely get Age == max-age and Varnish will calculate that as a 0s TTL and create a pass scenario. Conflicts: bin/varnishd/cache/cache_req_fsm.c
-
Dag Haavi Finstad authored
This lets you set environment variables in a test case. Usage is setenv "FOO" "bar" which will set FOO=bar if FOO does not already exist. There is also an optional '-force' argument, which will overwrite the current variable if already set: setenv -force "FOO" "baz" The force argument corresponds to passing a non-zero third argument to setenv(3).
-
Dridi Boukelmoune authored
It uses `explicit_bzero` when available and falls back to `memset` otherwise. Conflicts: configure.ac
-
- 05 Apr, 2017 3 commits
-
-
Martin Blix Grydeland authored
VBE_Poll would not advance to test the next backend on the cooling list when the backend's n_conn is non-zero. This would create a spinlock effect, causing delays that could make the master kill the child because of CLI timeout. Fixes: #2295
-
Martin Blix Grydeland authored
The child expects mgt to be consistent in its VCL state changes, e.g. not ask the child to 'use' a VCL that isn't warm. Not doing so will cause the child to assert (see asserts in cache_vcl.c:ccf_config_use). This could trigger because the mgt erranously would set its recorded temp regardless of the child's reply in mgt_vcl_setstate. This patch changes it to only record the new temp in mgt if the child replied success. If the child isn't running the new temp is always recorded. Slightly update v00044.vtc test case to reflect the need to update the state before restarting the child. Ref: https://github.com/varnishcache/varnish-cache/pull/2273
-
Martin Blix Grydeland authored
Newly loaded VCLs didn't get their go cold timer set even when they were set to auto, causing them to never go cold automatically. Fixes: #2270 Conflicts: bin/varnishd/mgt/mgt_vcl.c
-
- 04 Apr, 2017 1 commit
-
-
Martin Blix Grydeland authored
Fix a stupid misstake where the segment counter in the VSL segment was set just before the entire struct was cleared during initialization. This didn't cause problems in the common case because it would be set correctly on the very first log line produced. But it did open a race where an unfortunate early log client would assume it was lagging indefinetely behind varnishd on the log reading and report overflow error. This was most commonly experienced with varnishtest. Fixes: #2241
-
- 03 Apr, 2017 3 commits
-
-
Federico G. Schwindt authored
Fixes #2233.
-
Poul-Henning Kamp authored
not be able to get enough iovec's to do Chunked transmission. Fixes #2275 And #2207 was probably misdiagnosed, but the fix is correct anyhow. Conflicts: bin/varnishd/http1/cache_http1_line.c
-
Dridi Boukelmoune authored
-
- 31 Mar, 2017 1 commit
-
-
Poul-Henning Kamp authored
Fixes: #2200
-
- 30 Mar, 2017 2 commits
-
-
Pål Hermunn Johansen authored
Bad cherry-pick again from me. Fixing the test case that needs to be 4.1 compatible.
-
Nils Goroll authored
Merges #2152
-
- 20 Feb, 2017 2 commits
-
-
Pål Hermunn Johansen authored
The previous cherry-pick was bad. This should fix it.
-
Matthias Viehweger authored
-
- 09 Feb, 2017 2 commits
-
-
Pål Hermunn Johansen authored
Fix the description of #2184 in the changelog.
-
Pål Hermunn Johansen authored
-
- 08 Feb, 2017 4 commits
-
-
Pål Hermunn Johansen authored
-
Pål Hermunn Johansen authored
The previous changelog update contained a formatting mistake which is corrected here.
-
Pål Hermunn Johansen authored
-
Federico G. Schwindt authored
-
- 07 Feb, 2017 5 commits
-
-
Poul-Henning Kamp authored
which means not in vcl_backend_error{} Fixes: #1865 Conflicts: lib/libvcc/generate.py
-
Dridi Boukelmoune authored
-
Pål Hermunn Johansen authored
This is an adaptation of 86ae6dcf to the 4.1 branch. The point is to avoid accidential ++ and -- in generated code.
-
Federico G. Schwindt authored
IOW if we ended up in vcl_backend_error{} or failed after returning delivery in vcl_backend_response{} (e.g. we did not receive enough bytes) we will bump this counter. Conflicts: bin/varnishd/cache/cache_fetch.c bin/varnishtest/tests/r01624.vtc include/tbl/vsc_f_main.h
-
Poul-Henning Kamp authored
Fixes: #2167 Conflicts: bin/varnishtest/tests/m00019.vtc lib/libvcc/vcc_expr.c
-