the handling of if() expressions.



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

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

We now require python to build and we always regenerate the generated files.



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

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

Unbreak the build


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

This allows logging to varnishlog with the VCL_Log tag.


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

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

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

variables.



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

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

a property of the VCC instance.



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

fix some rst2man rendering issues

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

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

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

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

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

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

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

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