assert before the parent carried out the assignment of the thread
id to the variable.

Detected by:	OSX

And yes, why ptrdiff_t even exists and why it can be different,
semantically or otherwise, from ssize_t is beyond me...

The regression test and sensible error message was missing, so merge
those bits.

from sphinx. It was never properly maintained.

storage.

Fixes	#1176

If people only specify Transient, run only on Transient.

Fixes	#1176

Submitted by:	Federico G. Schwindt

Submitted by:	Federico G. Schwindt

Old indentation made the :ref: into a literal block, thus not a real
reference. This should do the trick.

from RFC5737's TEST-NET-1 and put a comment there to explain.

I fear this is a loosing battle, but at least this is more "official"
than the previous "10.255.255.255" choice.

Fixes #1159

Inspired by:	patch from geoff

size of the request, probably sleep copy&paste ?

Fixed	#1175
Submitted by:	martin

Increase the id field in VSM to 128 bytes to make space for 64 backend
VCL name + IPv4, IPv6 and portnumber.

This is the same as a9e5d350.

Fixes: #1224

Fixes #1167

With fix for #1275 we can now do a proper 503 when malformed
Vary-headers are received from backend. Error out instead of accepting
bogus ':'.

Conflicts:
	bin/varnishd/cache_vary.c

(out limit) characters long.

Fixes: #1274

Test case by: Dag Haavi Finstad

Fixes: #1275

Test case by: Dag Haavi Finstad

headers, and do 503 on parse error.

Conflicts:
	bin/varnishd/cache.h
	bin/varnishd/cache/cache_req_fsm.c
	bin/varnishd/cache_vary.c

This should not have any impact on the "normal" deliveries, as these
will as before be done through a single writev operation.

For deliveries involving chunked encoding (e.g. ESI or gunzip), this
should prevent an unnecessary delay where the Nagle algorithm kicks in
on the end-chunk write. This should give higher throughput and better
utilization of a single connection, especially for clients not doing
pipelining.

Conflicts:

	bin/varnishd/cache_acceptor.c

Fixes: #1261

This makes varnishncsa behave the same way as varnishlog, and prevents
overly large memory allocations if it should see a bogus fd (shmlog
overrun?).

XXX: This will not fix varnishncsa for current trunk, as that is using
XIDs instead of FDs breaking some functionality in the tools. This
will be handled in the API rewrite.

Fixes #1233