Varnish Cache source code repository
Switch branches/tags
varnish-6.1.1 varnish-6.1.0 varnish-6.0.2 varnish-6.0.1 varnish-6.0.0 varnish-5.2.1 varnish-5.2.0 varnish-5.2.0-rc2 varnish-5.2.0-rc1 varnish-5.1.3 varnish-5.1.2 varnish-5.1.1 varnish-5.1.0 varnish-5.0.0 varnish-5.0.0-beta1 varnish-4.1.10 varnish-4.1.9 varnish-4.1.8 varnish-4.1.7 varnish-4.1.6 varnish-4.1.5 varnish-4.1.5-beta2 varnish-4.1.5-beta1 varnish-4.1.4 varnish-4.1.4-beta3 varnish-4.1.4-beta2 varnish-4.1.4-beta1 varnish-4.1.3 varnish-4.1.3-beta2 varnish-4.1.3-beta1 varnish-4.1.2 varnish-4.1.2-beta2 varnish-4.1.2-beta1 varnish-4.1.1 varnish-4.1.1-beta2 varnish-4.1.1-beta1 varnish-4.1.0 varnish-4.1.0-tp1 varnish-4.1.0-beta1 varnish-4.0.5 varnish-4.0.4 varnish-4.0.4-beta1 varnish-4.0.3 varnish-4.0.3-rc3 varnish-4.0.3-rc2 varnish-4.0.3-rc2-proper varnish-4.0.3-rc1 varnish-4.0.2 varnish-4.0.2-rc1 varnish-4.0.1 varnish-4.0.0 varnish-4.0.0-tp2 varnish-4.0.0-tp1 varnish-4.0.0-beta1 varnish-3.0.7 varnish-3.0.7-rc1 varnish-3.0.6 varnish-3.0.6-proper varnish-3.0.5 varnish-3.0.4 varnish-3.0.4-rc1 varnish-3.0.3 varnish-3.0.3-rc1 varnish-3.0.2 varnish-3.0.2-rc1 varnish-3.0.1 varnish-3.0.1-rc1 varnish-3.0.0 varnish-3.0.0-beta2 varnish-3.0.0-beta1 varnish-2.1.5 varnish-2.1.4 varnish-2.1.3 varnish-2.1.2 varnish-2.1.1 varnish-2.1.0 varnish-2.0.6 varnish-2.0.5 varnish-2.0.4 varnish-2.0.3 varnish-2.0.2 varnish-2.0.1 varnish-2.0 varnish-2.0-tp2 varnish-2.0-tp1 varnish-2.0-rc1 varnish-2.0-beta2 varnish-2.0-beta1 varnish-1.1.2 varnish-1.1.1 varnish-1.1 varnish-1.0.4 varnish-1.0.3 varnish-1.0.2 varnish-1.0.1 varnish-1.0 varnish-0.9.1 varnish-0.9 live-test-1 key_header03
Nothing to show
Clone or download
nigoroll work around older libedit which fails to append rl_completion_append_…

I failed to find any issue in varnish and failed to find a
workaround for the code, so change the test to add an additional
space after the tab-completion.

If anyone has a better solution, please go head. Otherwise I feel
this is not worth any more time.

The test change, though not being ideal, should not cause any
harm at least.

Closes #2833
Latest commit 5765c9f Nov 15, 2018
Failed to load latest commit information.
.github no debuginfo packages on Mar 26, 2017
bin work around older libedit which fails to append rl_completion_append_… Nov 15, 2018
doc fix typo Nov 7, 2018
etc Make vcldir downstream-friendly in etc/ Feb 27, 2018
include Renovate libvarnisapi signal handling. Nov 12, 2018
lib Revert "Make FlexeLint a little bit happier" Nov 14, 2018
m4 update ax_pthread.m4 from upstream Aug 22, 2016
man Add VMOD proxy Mar 14, 2018
tools lost commit from ee9e0f6 Nov 6, 2018
.dir-locals.el Help emacs automatically follow project conventions. Apr 24, 2017
.gitignore Put all generated .rst files in doc/sphinx/include Oct 16, 2018
.syntastic_c_config Make life easier for vim/syntastic users Sep 5, 2016
.travis.yml Switch to clang 7 in our travis job Sep 26, 2018
CONTRIBUTING Final spit&polish before release Sep 15, 2016
ChangeLog remove old content from changelog May 18, 2013
INSTALL Remove mention of --enable-werror Nov 13, 2013
LICENSE Final spit&polish before release Sep 15, 2016 We don't want distcheck to exercise persistent by default, but we Mar 28, 2018
README.Packaging Remove referenses to Sep 12, 2017
README.rst Final spit&polish before release Sep 15, 2016
autogen.des Disable deprecated persistent storage by default Mar 5, 2018 Dedicated autoconf macros for libraries detection Nov 26, 2016 Also look for versioned rst2man scripts Oct 11, 2018
flint.lnt Move static asserts to vas.h, and decouple from OS #includes Nov 6, 2018
varnish-legacy.m4 Define PKG_CHECK_VAR for legacy systems Sep 13, 2016
varnish.m4 Python 3 takes priority over python 2 Sep 26, 2018 Install _all_ headers under ${prefix}/include/.. Nov 8, 2014 s/vcs/vsc/ Sep 13, 2017


Varnish Cache

This is Varnish Cache, the high-performance HTTP accelerator.

Documentation and additional information about Varnish is available on

Technical questions about Varnish and this release should be addressed to <>.

Please see CONTRIBUTING for how to contribute patches and report bugs.

Questions about commercial support and services related to Varnish should be addressed to <>.