- 23 Nov, 2015 4 commits
-
-
Guillaume Quintard authored
-
Guillaume Quintard authored
-
Guillaume Quintard authored
-
Poul-Henning Kamp authored
-
- 22 Nov, 2015 1 commit
-
-
Federico G. Schwindt authored
-
- 19 Nov, 2015 1 commit
-
-
Poul-Henning Kamp authored
-
- 18 Nov, 2015 1 commit
-
-
Poul-Henning Kamp authored
-
- 17 Nov, 2015 2 commits
-
-
Federico G. Schwindt authored
P.S. It requires -t 80.
-
Federico G. Schwindt authored
-
- 16 Nov, 2015 5 commits
-
-
Martin Blix Grydeland authored
-
Francisco Velázquez authored
-
Francisco Velázquez authored
-
Francisco Velázquez authored
-
franciscovg authored
-
- 12 Nov, 2015 1 commit
-
-
Federico G. Schwindt authored
AC_PREPROC_IFELSE is frowned upon. Take into account installations outside the compiler's default search path.
-
- 11 Nov, 2015 8 commits
-
-
Federico G. Schwindt authored
Fixes #1814 and more.
-
Federico G. Schwindt authored
Output whether pcre jit is usable at configure time.
-
Federico G. Schwindt authored
-
Poul-Henning Kamp authored
it working across platforms.
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
- 10 Nov, 2015 1 commit
-
-
Poul-Henning Kamp authored
can when we check a batch of lurkable bans. For obj.* only bans, this should concentrate the entire list at the very top. If there are req.* bans, the oc's end up on the bans right below the req.* bans. Fixes #1635 (As much as we can fix it)
-
- 09 Nov, 2015 5 commits
-
-
Lasse Karstensen authored
-
Kristian Grønfeldt Sørensen authored
varnishncsa for specifying the logging format by reading the log format from a file using the option "-f". Since -f means prefer X-Forwarded-For over client.ip in Varnish 3, maybe we should use another option letter.
-
Federico G. Schwindt authored
Also sort see also correctly. Fix #1795
-
Poul-Henning Kamp authored
This can happen in a number of obscure corner-cases, which do not warrant a panic. Fixes: #1807
-
Poul-Henning Kamp authored
-
- 07 Nov, 2015 1 commit
-
-
Federico G. Schwindt authored
Most likely missed when #1727 was addressed. Submitted by: Rafael Zalamena on varnish-dev
-
- 05 Nov, 2015 1 commit
-
-
Poul-Henning Kamp authored
have all (but one) caller do it.
-
- 04 Nov, 2015 2 commits
-
-
Federico G. Schwindt authored
Fixes #1801.
-
Lasse Karstensen authored
-
- 02 Nov, 2015 3 commits
-
-
Federico G. Schwindt authored
Indentation while I'm here.
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
Fixes #1813
-
- 30 Oct, 2015 4 commits
-
-
Federico G. Schwindt authored
This is consistent with what we do in other cases.
-
Lasse Karstensen authored
-
Poul-Henning Kamp authored
If we send the backend a HTTP/1.0 request, and it doesn't have a Content-Length, it cannot use Chunked and must fall back to EOF. However, the protocol field in the response tells us what version backend *could* have used, not what it *does* use. So we can get a response with HTTP/1.1 and EOF, following HTTP/1.0 semantics - because we asked for it. Most sensible backends avoid this, either by buffering and creation of a C-L or, smartly, returning "HTTP/1.0", even though that is strictly speaking against the apocrphal texts. Anyway, now we cope... Fixes: #1810
-
Poul-Henning Kamp authored
Fixes: #1796 Also triggered by: The Wemm-Field
-