Without this we could start running ban_lurker_test_ban with an empty
list of bans to test, causing a lot of unnecessary ban and oh mutex
contention on every ban lurker invocation until the REQ ban triggering
it is gone.

Also don't call ban_lurker_test_ban when our destination ban is the
same as the one being tested. This would be wasted work.

Adjust the c00049.vtc test case for the bans now not being
unnecessarily tested.

Resetting the pointer would race against the ban lurker moving the OC
in the ban list and any object event listeners wanting to see the new
ban timestamp on OEV_BANCHG.

Fixes: #1863

Without this we could ban an object erranously if the ban lurker has
moved the OC in the ban list while we were evaluating.

Spotted by:	Martin

ban-list if the lurker washes this OC while we check it.

Mostly diagnosed by:	Martin

Fixes:	#1864

Both contents and formatting were off.

Cause:

  9e07b947 Add a new VRT_acl_match function to the VMODs ABI

0a05e52c and friends are missing in 4.1.

VRT_MINOR_VERSION needs to be incremented for the 4.1 branch.

We'll need to change a couple of signatures in the call paths getting here
to propagate up the failure.

Pointed out by nirn on irc.

Original test case by fgsch

Fixes: #1858

This fix avoids a WS_Alloc panic when pushing fetch processors
and should thus avoid panics by overflowing the backend workspace in vcl.

This overflow is logged as FetchError "Bo workspace overflowed".

Other panic points due to workspace_backend being set too low still exist.

Sizing estimate for workspace_backend:

	sizeof(struct busyobj)
	+ 3 * HTTP_estimate(cache_param->http_max_hdr)
	+ cache_param->vsl_buffer
	+ cache_param->http_resp_size
	+ fetch processor memory
	+ space required in VCL

Fixes #1739

Allow to split https URI in the request line

Some submitted by: github::sublimino

None of it was important or troubling.

MERGE NOTE: Changes for gcc 4.9 in the spirit of 2039d8 added.

WS_Assert allows the workspace to be full in its check that `ws->f <= ws->e`.
WS_Reset does not honor this; if a snapshot was taken of a full workspace, and
that snapshot is reverted with WS_Reset, we panic.

This issue was identified by Jozef Hatala <jozef@fastly.com>

Just warn unless --strict is used.  This allows to use the same .vcc in
4.0 and 4.1.

When building multiple vmods from the same source directory,
vmodtool would trample on other concurrent jobs' vcc_if.[ch].

Discussed with phk@.  Fix confirmed by geoff@.

Fixes #1844.

Pointed out by phk@.

I've verified the rest and only these 2 were affected.