in vcl_backend_response{}

Submitted by:	fgs

conceiveably be a race that might be able to cause #1405.

Spotted by:	Coverity

Spotted by:	daghf

This allows the parsed transaction reason to be visible in the
transactions returned from the API.

This is to pave the way for varnishncsa to see which req transactions
are ESI's and skip these.

This makes the logging API work again after the changes to the Begin
and Link log records.

Even though restarts are linked below the request that initiated them,
the API will report them at the same level as the initiating
request. This is to help makes queries depending on levels
predictable.

unsets are logged.

an object.

to a separate source file and open (and close) a socket specifically
for that purpose, so we can do the right thing with parameter
defaults.

first field to the type of entity.

Martin will commit corresponding and necessary changes to the
API in a matter of milliseconds or possibly hours or days, so
minor weirdness from varnishlog/ncsa can be expected for a brief
amount of time.

Testcase l00000 & l00001 are also broken until the API catches up.

Spotted by:	fgs

side, but staring at the wrong assert for hours on end did not
reveal that.

Many thanks to:		scoof
Fixes #1397

(and a typo)

It seems that browser writers also have trouble figuring out that
twisted logic in HTTP/1.1.

Fixes:	#1404
Spotted by:	Scoof

actually wanted to do.

Hat-tip:	scn

Fixes	#1395

for the bg-fetch, before we release the request to carry on.

Fixes	#1399