Output whether pcre jit is usable at configure time.

it working across platforms.

can when we check a batch of lurkable bans.

For obj.* only bans, this should concentrate the entire list at the
very top.

If there are req.* bans, the oc's end up on the bans right below
the req.* bans.

Fixes	#1635

(As much as we can fix it)

varnishncsa for specifying the logging format by reading the log
format from a file using the option "-f". Since -f means prefer
X-Forwarded-For over client.ip in Varnish 3, maybe we should use
another option letter.

Also sort see also correctly.

Fix #1795

This can happen in a number of obscure corner-cases, which do not
warrant a panic.

Fixes:	#1807

Most likely missed when #1727 was addressed.

Submitted by: Rafael Zalamena on varnish-dev

have all (but one) caller do it.

Fixes #1801.

Indentation while I'm here.

Fixes	#1813

This is consistent with what we do in other cases.

If we send the backend a HTTP/1.0 request, and it doesn't have a
Content-Length, it cannot use Chunked and must fall back to EOF.

However, the protocol field in the response tells us what version
backend *could* have used, not what it *does* use.

So we can get a response with HTTP/1.1 and EOF, following HTTP/1.0
semantics - because we asked for it.

Most sensible backends avoid this, either by buffering and creation
of a C-L or, smartly, returning "HTTP/1.0", even though that
is strictly speaking against the apocrphal texts.

Anyway, now we cope...

Fixes: 	#1810

Fixes:	#1796
Also triggered by:	The Wemm-Field

The proxy log records were attempted to be logged on the request' log
buffer, which at that point in time has not yet been set up and does
not posess a VXID. This caused VXID==0 log records to be inserted in
the beginning of the log for the first request on the session when
using proxy protocol, and subsequently the VSL to fail picking them
out as valid request log transactions.

Fix by logging the PROXY handling related messages on the session, in
which they belong.

Fixes: #1804

Change SIGHUP handling depending on whether we're running in daemon mode
or foreground. The former will continue rotating the logs, the latter
will abort the loop and die gracefully.

Fixes #1794.

Fixes #1809.

Found by ingvar while packaging 4.1.0.

Use `python' as with the other Python scripts.

makes work for it.  Have it sleep as long as possible, rather
than hot-polling for work to do.

Amazingly JEMALLOC didn't spot this one.

from the data structure we use to store and operate on the ban (ban).

on the ban lurker not starting.

Move cache_hash's access to bans into cache_priv.h