Prefer vcl_name(ipv4,ipv6,port) to the old vcl_name in output.

Fixes	#1046

Also optimise out a few strlen calls in favour of just tracking the
lengths.

Fixes: #1047

one byte reads for the hex-length headers.

catch trouble that materializes only when we destroy the VGZ instance.

Fixes	#1037
Fixes	#1043
Fixes	#1044

to fail, and act accordingly.

Convert all the old changelogs to restructured text, drop xsltproc
from the build system and adjust documentation appropriately.

FetchBody.

to clean those up non-fatal.

Fixes	#1036

The thread (s%d/c%d) still dies, but it does not mark this as
fatal with respect to the test as such.

This is useful where varnishd shuts the connection on a backend
prematurely, as part of the correct execution of a test.

Fix a undue recursion problem with asserts in the vtc_log code.

before all diagnostics have been gathered.

processing.

Convert a few http_PrintfHeader() to http_SetHeader() for good
measure: There is no reason to waste workspace on compiled in strings.

Fixes	#1038

This should make it possible to get a different worker thread to pull
the body in from the backend, without cloning the session structure,
with all the trouble that would cause.

parameter all the time.

Also decontaminate FetchStorage to not need session

code path, to pave the road for Martins streaming code.

Remove reference/purging_banning, since all info is now in tutorial/purging

Note that error wasn't actually working in vcl_deliver, and this just puts
VCC in line with the rest of Varnish. Syntax errors are better than assert
errors.

Re #1027

I'll leave it for later discussion to see if we close #1027, which is
technically a feature request now, though a request for a feature we used
to have (not sure how well it worked).

As per documentation, the ban lurker sleeps ban_lurker_sleep when it is
successful, but on failure it should only sleep 1.0s. No point hammering
the ban list every 0.01s if bans aren't even used.

Fixes #1030