- 13 Nov, 2020 4 commits
-
-
Dridi Boukelmoune authored
Seeing a test failure on vtest I think there might be a race here that I hope to make more explicit next time it occurs.
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
A nice and tidy single token to integrate with the parameters table. Refs #3250
-
Dridi Boukelmoune authored
This reverts commit 5367be3f.
-
- 12 Nov, 2020 6 commits
-
-
Nils Goroll authored
polish differently and more sensibly
-
Nils Goroll authored
constify and avoid (char *) = strchr((const char *), x) error: vtc_varnish.c 559 Error 158: Assignment to variable 'la' (line 548) increases capability
-
Nils Goroll authored
as copies of the respective client side flags
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
When a parameter set is associated at the director level, it should be in effect with resolve=NOW as with resolve=LAZY.
-
- 10 Nov, 2020 1 commit
-
-
Poul-Henning Kamp authored
-
- 09 Nov, 2020 8 commits
-
-
Martin Blix Grydeland authored
This adds VTCP_Assert() on the result of read and write calls that deals with TCP sockets.
-
Martin Blix Grydeland authored
-
Martin Blix Grydeland authored
When used to check the result of read() and write() calls, it is useful that a positive return value is accepted in VTCP_Check().
-
Martin Blix Grydeland authored
Now that VTCP_Assert() accepts EAGAIN as a legal errno value for read() errors, uncomment this check.
-
Martin Blix Grydeland authored
Since the input value is sometimes the result of a read()/write() call, avoid truncating the ssize_t value on calling it.
-
Martin Blix Grydeland authored
When a socket timeout is set on a socket and the timeout expires, read() and write() calls on that socket will return (-1) with errno set to EAGAIN/EWOULDBLOCK.
-
Martin Blix Grydeland authored
Consistently use VTCP_Assert when asserting on the result of VTCP_Check().
-
Poul-Henning Kamp authored
-
- 06 Nov, 2020 1 commit
-
-
Poul-Henning Kamp authored
-
- 05 Nov, 2020 5 commits
-
-
Nils Goroll authored
for VCL_* functions from cache_varnishd.h
-
Nils Goroll authored
Ref: 1e09f422
-
Dridi Boukelmoune authored
I find ":path: /foo" more descriptive than "/foo", even though I could infer which one it was...
-
Dridi Boukelmoune authored
-
Poul-Henning Kamp authored
-
- 04 Nov, 2020 1 commit
-
-
Guillaume Quintard authored
Long story short: newer coreutils use `statx` which isn't supported by old kernel, so the `debian:bullseye` images blew up.
-
- 02 Nov, 2020 9 commits
-
-
Dridi Boukelmoune authored
Similarly to Timestamp:Fetch, it is otherwise not possible to distinguish between time spent in VCL and time spent strictly fetching the response body.
-
Dridi Boukelmoune authored
If significant time is passed in vcl_backend_fetch it becomes difficult to interpret Timestamp:Connected, which this new timestamp remedies.
-
Dridi Boukelmoune authored
Depending on the settings, a timeout can be ambiguous. It's also generally useful to be able to tell how long it takes, monitor it and possibly notice a degradation before errors start manifesting themselves.
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
it is too far down the stack. Instead pass the objcore through the priv structure from ved_deliver() which has legitimate access.
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Nils Goroll authored
complement the existing c88 test with changing the path of a backend.
-
- 28 Oct, 2020 5 commits
-
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Dridi Boukelmoune authored
They are taking too long, needlessly holding onto job slots forever. Align with CircleCI for now, even though we could probably do more.
-
Dridi Boukelmoune authored
Except those present in varnishtest/vtest.
-