- 14 Dec, 2015 2 commits
-
-
Poul-Henning Kamp authored
VCC's own complaint instead.
-
Poul-Henning Kamp authored
-
- 12 Dec, 2015 2 commits
-
-
Federico G. Schwindt authored
The latter takes precedence as per RFC 7232. Also if we have an I-N-M but no entity don't check I-M-S, just do a non-conditional request.
-
Federico G. Schwindt authored
That is, if both If-None-Match and Range are present we need to use a strong comparison as the representation needs to be byte-for-byte identical.
-
- 11 Dec, 2015 2 commits
-
-
Federico G. Schwindt authored
As per RFC 7232. Fixes #1816.
-
Federico G. Schwindt authored
-
- 10 Dec, 2015 7 commits
-
-
Federico G. Schwindt authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Federico G. Schwindt authored
Send your kudos to POSIX for failing to provide a standard here.
-
Federico G. Schwindt authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
- 09 Dec, 2015 8 commits
-
-
Poul-Henning Kamp authored
with a single one.
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
- 08 Dec, 2015 2 commits
-
-
Dag Haavi Finstad authored
It's needed for the vdi_healthy_f invocation.
-
Poul-Henning Kamp authored
-
- 07 Dec, 2015 2 commits
-
-
Dridi Boukelmoune authored
This is for the 4.1 ABI, since the next major release will have a VRT_MAJOR_VERSION bump instead. The two functions may also change semantics before the next 4.1.x, but will still be _new_ as far as releases are concerned.
-
Dridi Boukelmoune authored
-
- 05 Dec, 2015 7 commits
-
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
By default the reference is released as soon as the VCL goes cold, which doesn't harm the existing tests yet allows to cover the new VRT_ref_vcl and VRT_rel_vcl functions. It is possible to ask the vmod to release the reference after a delay.
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
Now that VCLs can be referenced, there are two different situations stalling the cooldown. The "cooling" one is kept for VCLs that have received a COLD event, and the "busy" one is introduced to wait for ongoing transactions. Basically, if there are transactions, the VCL is still active even though it's not *the* active VCL and should therefore be considered warm. This guarantees that WARM and COLD events are balanced, and also that a "busy" VCL doesn't need to warm up if it is set to warm again. The new VCL temperature engine looks like this: .----------W>---------------. | .--W>---. v init ---> cold --| |-- warm --. ^ ^ '---<C--' | | | | | | | '--- cooling <C--' | | ^ | | C | | | .---<---. | '--<C-- busy --| |--' '--->---' The transitions marked with a 'W' or a 'C' are the one dispatching WARM and COLD events respectively. Since the "busy" state is considered warm, VMODs should operate as such and backend creation remains possible.
-
Federico G. Schwindt authored
-
- 04 Dec, 2015 8 commits
-
-
Federico G. Schwindt authored
Broken implementations do it contrary to what the RFC mandates. Fixes #1826.
-
Federico G. Schwindt authored
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
-
Martin Blix Grydeland authored
This works around a Linux kernel bug where the epoll_wait will return EINTR when the process is subjected to a ptrace or the OS wakes from suspend. Fixes: #1763
-
Lasse Karstensen authored
-