git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4983 d4fa192b-c00b-0410-8231-f00ffab90ce4

otherwise use the first backend or director we find as default.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4982 d4fa192b-c00b-0410-8231-f00ffab90ce4

Fixes: #681



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4981 d4fa192b-c00b-0410-8231-f00ffab90ce4

transactions correctly.

Only Emmit Length and ReqEnd if we have an XID.

Fixes: #709
Fixes: #720



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4980 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4979 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4978 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4977 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4976 d4fa192b-c00b-0410-8231-f00ffab90ce4

tightfisted -smalloc would trigger.

Fixes: #719



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4975 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4974 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4973 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4972 d4fa192b-c00b-0410-8231-f00ffab90ce4

rather than panics.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4971 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4970 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4969 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4968 d4fa192b-c00b-0410-8231-f00ffab90ce4

We didn't create/destroy directors and backends in a consistent order,
and in some case we even destroyed directors more than once.

Always destroy in opposite order of creation (which follows VCL
source order).

Turn the bottom element of the array into (only) an indication
of which backend/director is the default.

Fixes:	#722



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4967 d4fa192b-c00b-0410-8231-f00ffab90ce4

this set of counters.

Backend stats counters are indexed purely by the backend name,
across all VCLs:  If you redefine or have conflicting definitions
of a backend with a given name, in different VCLs loaded at the
same time, they will share stats counters.

Not optimal, but I think the alternative would be worse.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4966 d4fa192b-c00b-0410-8231-f00ffab90ce4

Freeed (cooled) on child start.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4965 d4fa192b-c00b-0410-8231-f00ffab90ce4

to complete.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4964 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4963 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4962 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4961 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4960 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4959 d4fa192b-c00b-0410-8231-f00ffab90ce4

start abstracting this stuff to a common file (vsm.c).



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4958 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4957 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4956 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4955 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4954 d4fa192b-c00b-0410-8231-f00ffab90ce4

usage strings, before I continue.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4953 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4952 d4fa192b-c00b-0410-8231-f00ffab90ce4

is still on the loose.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4951 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4950 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4949 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4948 d4fa192b-c00b-0410-8231-f00ffab90ce4

Some text on purging and bans. I guess we would need to rename url.purge at some point. This is quite confusing.

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4947 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4946 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4945 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4944 d4fa192b-c00b-0410-8231-f00ffab90ce4