Submitted by:	rezan
Fixes:		#1931

Disabled by default.  phk@ ok.

Fixes: #1967

... in order to actually use it by default

fixes #1971

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

Ref: #1847

Ref: #1873

Fixes #1873

Ref: #1806

Ref: #1955

This might happen during pass'd requests or in a multi-tier setup.
Fixes #1955.

Ref: #1855

Early version of the patch OK'd by martin@.

Fixes #1855.

Ref: #1928

Fixes #1928

Conflicts:
	bin/varnishd/http1/cache_http1_fsm.c

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

Ref: #1813
Ref: #1810
Ref: #1807
Ref: #1804
Ref: #1801
Ref: #1796
Ref: #1794

Ref: #1905

Raise a ParseError exception if not.

Fixes #1885.

Fixes #1869

OK'd by phk@.

Fixes #1883.

Fixes #1918.

Submitted by:	Pål Hermunn Johansen

All bans on olist can get marked completed as duplicates while we're
working on them, in particular as we start at an offset of
ban_lurker_age.

Fixes #1919

Fixes a bug where we wait for an event to fire on the backend socket
prior to passing the request body.

The VBT_Wait call is now handled in vbe_dir_finish.

Test case by thomaslc

Fixes: #1806

Updated formatter %{VSL:tag}x to mirror the VQL. The documentation has
been updated accordingly.

The formatters %{Varnish:vxid}x and %{VSL:key[:field]} are introduced,
with documentation. Also updated copyright in the varnishncsa.c file.

Fixes #1912

A new mode, backend mode, in varnishncsa is introduced. It lets you
log trafic from varnish to the backends. The normal (default) mode is
now named "client mode" and can be explicitly selected using -c. You
can run varnishncsa in backend mode in addition to varnishncsa in
client mode, but it is also possible to run in mixed mode by
specifying both -b and -c.

New formatter added: %{Varnish:side}x will be either "b" or "c",
depending on where the request was made.