This can happen if you get an IPv6 address for the -a argument, but
runs without IPv6 enabled in your kernel.  Typically happens only
for localhost.



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

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

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

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

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

Remove bogus "has_string" variable marking, it can be derived from the type.

Make obj.* variables valid in vcl_timeout() and vcl_discard()



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

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

their scope.  One example of this is the "req.hash" variable which only
exists in the vcl_hash method.



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

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

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

when -C is specified, this makes it easier to do completeness test on the
VRT interface.


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

This is for DES' work on LRU list.



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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

juggling file names and simply do everything relative to our cwd.


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

error handling; use a regexp to check the name syntax; check CLI errors after
the getopt() loop.

Discussed with:	ceciliehf


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

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

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

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

wording, constify varnish_name, move default name logic into VSL_Open*().


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

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

Added the -n option for specifying a name for varnishd. All files are now stored under /tmp/<name> where 
<name> is either a specified name or the hostname. All the varnish tools have also been updated to let the user 
specify the name of the varnish instance to use. The name must conform to the hostname standard, but a test 
for this is not yet implemented.



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

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

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

end of the file.


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

When we cache an object with a "Vary:" header, we generate
a "vary matching string" which can be used to efficiently
check for compliance when doing a cache lookup.

Only very lightly tested (ie: cnn.com).

For a full description of the reasoning, please see
	http://varnish.projects.linpro.no/wiki/ArchitectureVary



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

perfectly good pipelined data.



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

strndup which might come from the former.


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