Some minor nitpicking and some slightly ugly stuff. It currently fails a
regression test (v00017.vtc). I'm on it.



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

The DNS director allows Varnish to pick backend based on the Host header
provided by the client, and how it resolves in DNS. A suffix can be added
to make it "internal" (see vcl(7)).

There's still some quirks that I want to work out, but this seems fairly
commit-ready and non-intrusive.



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

- Replaced specific include files with a wildcard glob
- Needs python-sphinx to build sphinx documentation
- Builds html and latex documentation. Put that in a subpackage varnish-docs



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

- Made to work with trunk again, see specfile changelog


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

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

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

Candidate for merging into 2.1 branch



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

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

You can now say:

	if (beresp.ttl >= beresp.grace + 30 s) {
	}

and similar.




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

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

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

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