Found & Fixed by:	Martin

Fixes	#978

Found & Fixed by:	Martin

Fixes	#979

	we transform (gzip/gunzip)
	we stream and backend didn't send c-l.

Fixes	#980

Testcase by:	Martin

If the first (policy-chosen) backend fails to get us a connection,
retry a random backend (still according to their weight) until
retries are exhausted.

Kristian sent a proof of concept patch, I just cleaned it up and made
it compile.

Thanks to:	Kristian

Fixes	#977

32 bit systems.

Spotted by:	Kristian

Explained the semantics quickly so people understand why not all objects survive a crash

more on transient.
didn't get it rigth the first time.
Thanks to scoof for pointing it out.
(cherry picked from commit 6a59dacc
and 0b23a0f0)

response code stuff and fully incorporate the fact that they are both
16 unsigned now.

No functional changes.

the silo into VM.  If this fails or we get garbage, the silo will
be cleared.

Fixes	#962

end of the UINT_MAX items we can support.

Found by adding a lot of asserts and brute force testing, both
of which I have left in.

Fixes       #967

May also be relevant to #827
(cherry picked from commit 726d93ff
and a6ddafc0)

also have the 206/range handling.

Instead of building the 304 response from scratch, dumb down the
200 response accordingly.

This implement the policy consideration of #970 led to.

Written by:	Martin

prefer IMS, it is less work and less data to transmit.

Fixes	#972

Thanks to:	Martin

into the RFC policy module where it belongs.

Put esi → do_esi in upgrade checklist, fix markup typo.

Fixes #974

Document the TTL record.

Simplify the move from sp->wrk to sp->obj accordingly.

Add a diagram that explains how ttl, grace & keep related to
each other.

Fix VCL's obj.ttl variable to appear to be relative to "now" rather
than obj->entered. (#956)

Also log SLT_TTL when we change obj.grace and obj.keep

Make SLT_TTL always have the same format:
	XID
	"RFC" or "VCL"
	obj.ttl
	obj.grace
	obj.keep
	obj.entered
	obj.age
In addition "RFC" has:
	obj.date
	obj.expires
	obj.max-age

Fixes	#956

Thanks to:	DocWilco

non-busy.  Not sure what I thought when I changed it last, but it
was clearly not smart thinking.

Spotted by:	Martin
Test case by:	Martin

Fixes	#963

fields in different ways.

Thanks a lot to Andreas Plesner Jacobsen for writing those up.

DocWilcos proposed fix in #956

XXX: the 64k fd limitation should probably be fixed.

dlopen typically only fails here if the child process does not have
access to the build directory and the user runs varnishtest as root
(meaning the child setuids to nobody).  Report the dlerror and give a
hopefully helpful hint to help diagnose the error.

Fixes: #959

dereferencing and destroying a busy objcore.

Free the busyobj in the case that the worker already has one
(potential race condition from the expiry/ban-lurker threads?)