started fixing that, and then I fixed another couple of nits and polished
the naming a bit and ...

Well, you know how it is.

Changed the backend matching function to take a call-back function
to eliminate the need for the memory which got leaked.

This meant that backend.list could also use it, if only the parsing
code accepted a blank input.

So I rewrote the parsing code to also allow empty names, so you can:
	backend.list (:80)
	backend.list (192.168)
etc.

And then I added a summary report of the probing, if it is happening,
and explicitly say that no probing is happening if it isn't.

Make it possible to mark backends as sick or healthy by way of

  backend.set_health $backendname (sick|healthy|auto)

document gzip'ed.

Fixes	#1029

Fixes	#1046

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

Fixes: #1047

Conflicts:

	bin/varnishd/cache_fetch.c

one byte reads for the hex-length headers.

Conflicts:

	bin/varnishd/cache_fetch.c

Conflicts:

	bin/varnishd/cache_esi_fetch.c
	bin/varnishd/cache_fetch.c
	bin/varnishd/cache_gzip.c

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

Fixes	#1037
Fixes	#1043
Fixes	#1044

Conflicts:

	bin/varnishd/cache.h
	bin/varnishd/cache_center.c
	bin/varnishd/cache_esi_deliver.c
	bin/varnishd/cache_esi_fetch.c
	bin/varnishd/cache_fetch.c
	bin/varnishd/cache_gzip.c
	bin/varnishd/cache_response.c

to fail, and act accordingly.

Conflicts:

	bin/varnishd/cache_fetch.c

to clean those up non-fatal.

Fixes	#1036

Conflicts:

	bin/varnishd/cache_gzip.c

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.

Conflicts:

	bin/varnishtest/vtc.c

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

Conflicts:

	bin/varnishd/cache_center.c
	bin/varnishd/cache_response.c

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

Submitted by:	Nils Goroll

crashing child to do so, and then explicitly start it again.

avoid fixed sleeps waiting for the child process to start.

1 thread is a bit on the low side, make the default on RPM based
distros 50.

instead of asserting.

Inspired by:	Patch from DocWilco