- 14 Jun, 2016 22 commits
-
-
Dridi Boukelmoune authored
-
Federico G. Schwindt authored
Raise a ParseError exception if not. Fixes #1885.
-
Dridi Boukelmoune authored
-
Lasse Karstensen authored
-
Lasse Karstensen authored
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
When varnishtest creates a socket barrier, it will bind a socket and listen to incoming connections. Once the number of expected connections is open, connections are closed. Barrier users only need to connect to the socket, read "nothing" and block until the connection is closed. It allows virtually any process to sync with varnishtest. The barrier will provide macros with its socket information.
-
Dridi Boukelmoune authored
This is similar ASSERT_CLI, in order to make socket barriers creation thread-safe.
-
Dridi Boukelmoune authored
This is useful in HTTP loops where it's impossible to predict and use an array of barriers. All cycles expect the same number of waiters, unlike semaphores.
-
Dridi Boukelmoune authored
They work like semaphores, except that they need explicit initialization and can optionally be shared between processes. Conflicts: bin/varnishtest/tests/c00073.vtc
-
Federico G. Schwindt authored
-
Federico G. Schwindt authored
With this you can also filter based on logexpect's vsl arguments.
-
Lasse Karstensen authored
-
Poul-Henning Kamp authored
pattern in the body.
-
Lasse Karstensen authored
As suggested by Przemek Sobstel on github.
-
Guillaume Quintard authored
Spotted by: hermunn
-
Pål Hermunn Johansen authored
In most circumstances the counters vsm_overflow and vsm_overflowed should be zero. This patch tells the user what he should probably do when they are not.
-
Lasse Karstensen authored
(and test the commit email hook)
-
Lasse Karstensen authored
(But mostly for testing the commit email system.)
-
Lasse Karstensen authored
-
Lasse Karstensen authored
-
- 09 Jun, 2016 2 commits
-
-
Poul-Henning Kamp authored
Submitted by: rezan Fixes: #1931
-
Federico G. Schwindt authored
Disabled by default. phk@ ok.
-
- 07 Jun, 2016 1 commit
-
-
Lasse Karstensen authored
Fixes: #1967
-
- 06 Jun, 2016 2 commits
-
-
Nils Goroll authored
... in order to actually use it by default
-
Nils Goroll authored
fixes #1971
-
- 03 Jun, 2016 1 commit
-
-
Brandon Black authored
Commit e142a199 for Issue #1918 fixed up the case where the server sends an HTTP/1.1 response with no Content-Length, no Transfer-Encoding, but with Connection:close. This fixes the very similar case where all the conditions are the same except that there's also no Connection: close header, but the content is still implicitly delimited by the server closing the connection. This behavior has been observed from multiple versions of Apache with WSGI applications behind it, resulting in broken Content-Length:0 responses from Varnish. Ref: varnishcache/varnish-cache#1954
-
- 01 Jun, 2016 4 commits
-
-
Lasse Karstensen authored
Ref: #1847
-
Lasse Karstensen authored
Ref: #1873
-
Nils Goroll authored
Fixes #1873
-
Lasse Karstensen authored
Ref: #1806
-
- 31 May, 2016 7 commits
-
-
Pål Hermunn Johansen authored
Ref: #1955
-
Federico G. Schwindt authored
This might happen during pass'd requests or in a multi-tier setup. Fixes #1955.
-
Lasse Karstensen authored
Ref: #1855
-
Federico G. Schwindt authored
Early version of the patch OK'd by martin@. Fixes #1855.
-
Lasse Karstensen authored
Ref: #1928
-
Nils Goroll authored
Fixes #1928 Conflicts: bin/varnishd/http1/cache_http1_fsm.c
-
Pål Hermunn Johansen authored
When allocating ESI memory through objallocwithnuke, tell the sevedore in storage_simple.c that getting less than requested, is not interesting. Fixes #1941 This is a back port of #1961
-
- 30 May, 2016 1 commit
-
-
Lasse Karstensen authored
Ref: #1813 Ref: #1810 Ref: #1807 Ref: #1804 Ref: #1801 Ref: #1796 Ref: #1794
-