- 13 Jan, 2016 40 commits
-
-
Lasse Karstensen authored
-
Lasse Karstensen authored
Trips up my syntax highlighting.
-
Lasse Karstensen authored
To get this into the normal Sphinx build, move it to bin/varnishstat/ (where it feels like it belongs the most), and use our normal build flow for man pages.
-
Lasse Karstensen authored
-
Lasse Karstensen authored
We don't maintain any history, and the man page is covered by the distribution copyright.
-
Lasse Karstensen authored
-
Federico G. Schwindt authored
-
Poul-Henning Kamp authored
Conflicts: include/tbl/locks.h Merge note: Keeping persistence locks are they were, due to non-merged SML reorganisation.
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
Use the hash_classic class as proof of concept
-
Poul-Henning Kamp authored
-
Federico G. Schwindt authored
-
Poul-Henning Kamp authored
Spotted by: FlexeLint
-
Federico G. Schwindt authored
Rather than copying one char at the time extend the buffer as needed and use memcpy.
-
Poul-Henning Kamp authored
that needs to know about oc->busyobj semantics
-
Federico G. Schwindt authored
-
Federico G. Schwindt authored
-
Federico G. Schwindt authored
This is enough to get the warnings fixed in the previous commit on Linux.
-
Federico G. Schwindt authored
-
Federico G. Schwindt authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
VCC's own complaint instead.
-
Poul-Henning Kamp authored
-
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.
-
Federico G. Schwindt authored
As per RFC 7232. Fixes #1816.
-
Federico G. Schwindt authored
-
Federico G. Schwindt authored
-
Poul-Henning Kamp authored
Conflicts: bin/varnishd/cache/cache.h 4.1 merge note: req_body_iter_f interface kept.
-
Federico G. Schwindt authored
-
Dag Haavi Finstad authored
It's needed for the vdi_healthy_f invocation.
-
Poul-Henning Kamp authored
-
Dridi Boukelmoune authored
-
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
-
Federico G. Schwindt authored
Broken implementations do it contrary to what the RFC mandates. Fixes #1826.
-