- 16 Aug, 2018 40 commits
-
-
Nils Goroll authored
in order to have it build first and cleaned up fixes this issue when switching to an older branch: $ git checkout ... error: The following untracked working tree files would be overwritten by checkout: bin/varnishtest/vtc_h2_dectbl.h Please move or remove them before you switch branches. Aborting
-
Dag Haavi Finstad authored
This still lacks error handling and thus is not a fix for #2589, but at least we're not writing past the end of the workspace any more.
-
Poul-Henning Kamp authored
header lines. Fixes: #2678
-
Poul-Henning Kamp authored
Fixes: #2682
-
Poul-Henning Kamp authored
after the headers. Fixes: #2731
-
Poul-Henning Kamp authored
Start pylinting while here anyway.
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Poul-Henning Kamp authored
Submitted by: Frederic Lecaille <flecaille@haproxy.com>
-
Geoff Simmons authored
Closes: #2737
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
Fixes: #2729
-
Poul-Henning Kamp authored
counting deck-chairs on the Titanic.
-
Poul-Henning Kamp authored
-
Guillaume Quintard authored
-
Guillaume Quintard authored
-
Valentin Matei authored
client content -> client context
-
Nils Goroll authored
this tests d912ffe4 Tweaked: bin/varnishtest/tests/d00007.vtc In 6.0 this bug doesn't exist and directors behave slightly differently so the test case needed some adjustments to both show that a backend can be added to an already warm VCL with a probe, and that requests succeed.
-
Guillaume Quintard authored
-
Valentin Matei authored
-
Geoff Simmons authored
-
Geoff Simmons authored
This was a proof of concept for an alternative WS interface -- write incrementally to reserved workspace as an "open buffer". That may be generally useful for Varnish, but for now we return to the usual WS_* idiom.
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
The error may be status 500 on 32-bit systems.
-
Geoff Simmons authored
On the various platforms, esp 32-bit, workspace may be exhausted before it gets to the VMOD at all, so we can't reliably expect specific error messages. This has nevertheless improved GCOV coverage, which was the goal.
-
Geoff Simmons authored
To get some better GCOV coverage. So far just IDENTITY encoding.
-
Poul-Henning Kamp authored
Submitted by: Frederic Lecaille <flecaille@haproxy.com>
-
Geoff Simmons authored
Closes #2722
-
Federico G. Schwindt authored
I've been torturing varnish with this change for some time and was not able to reproduce the problem. Should fix #2719.
-
Poul-Henning Kamp authored
Fixes 2727
-
Dridi Boukelmoune authored
Unless -1 is used too, but -1 already implies -d so it doesn't really count. Fixes #2721
-
Dridi Boukelmoune authored
This reverts commit d1b78e8d. The problem is that upon exiting the screen is likely to be cleared on most terminals (not the one we embed in varnishtest for example) so it doesn't give any chance to the user to read the output. The consensus is to restore the previous behavior and fix the manual instead. Conflicts: bin/varnishtest/tests/u00004.vtc bin/varnishtop/varnishtop.c Breaks: bin/varnishtest/tests/r02686.vtc Refs #2721
-
Federico G. Schwindt authored
-
Dag Haavi Finstad authored
Fixes: #2572
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
with varnish user etc.
-
Nils Goroll authored
With the req.grace reintroduction, we got two identical cases where we insert a busy object: When there is no exp_oc (obviously) or when the exp_oc does not fulfil the req.grace limit. This lead to some code duplication. IMHO, handling first the case where we need to insert a busy object (with or without exp_oc) and then handling the exception that we do not wait on a busy object if the exp_oc is in grace is cleaner. Please note that comparing this change using diff -u does not make much sense, I believe the simplicity of the reshuffling change becomes clear when looking at the old and new code side-by-side
-
Nils Goroll authored
-