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

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

hask-key build process to look like a function call instead:
	hash_data(req.http.foo_bar) 
and allow string concatenation while we're at it.

the name "hash_data()" is not quite to my liking, but I want to avoid
"hash()" since that clashes with previous syntax for "return(hash)".



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

Rename RTIME->DURATION in the python code and regenerate output.

Remove fluff from python script



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

rename "RTIME" to "DURATION", to appease the POLA.



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

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

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

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

a sub process, to make contamination of the MGR process impossible.



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

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

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

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

list of tokens and we need it to learn even more tricks now, which
will expose the type name outside this source directory.



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

(vcl.load/include)

Does not do anything yet.



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

the Length header match the actual composite object sent to the client.



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

Fixes: #723



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

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

default



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

them by name:

	probe foo {
	    .url = "/";
	    .timeout = 1s;
	}

	director default random {
	    { .backend = {.host = "10.0.0.1"; .probe = foo; } .weight = 1; }
	    { .backend = {.host = "10.0.0.2"; .probe = foo; } .weight = 1; }
	    { .backend = {.host = "10.0.0.3"; .probe = foo; } .weight = 1; }
	    { .backend = {.host = "10.0.0.4"; .probe = foo; } .weight = 1; }
	    { .backend = {.host = "10.0.0.5"; .probe = foo; } .weight = 1; }
	    { .backend = {.host = "10.0.0.6"; .probe = foo; } .weight = 1; }
	    { .backend = {.host = "10.0.0.7"; .probe = foo; } .weight = 1; }
	}



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

to them from backend specs.



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

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