P.S. It requires -t 80.

AC_PREPROC_IFELSE is frowned upon.  Take into account installations
outside the compiler's default search path.

Fixes #1814 and more.

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