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

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

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

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

(Varnish Stream Sockets) as I intend to eventually add support for AF_UNIX
sockets.

This also moves the accept filter code out from VSS_listen() (previously
TCP_open()) and into a separate function in tcp.c


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

* Make http auth work



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

pointer gymnastics getting out of hand.

In addition to the obvious alloc/return primitives there are also 
reserve/release primitives for when we don't know the length yet.



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

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

require gcc 4), tune autogen.des accordingly.


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

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

and which is copied to the shared parameter block every time a parameter
changes as well as immediately before forking off a child.  This prevents a
hypothetical compromised child from changing the parent's idea of run-time
parameters (which would, for example, allow it to trick the the parent into
starting a new, hypothetically exploitable child with the attacker's choice
of uid / gid).

While I'm here, correct the use of the "volatile" qualifier - it is the
parmeter block itself which can change unpredictably, not the pointer.


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

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

user and group to which the child process will switch immediately after fork()
returns, before it starts accepting connections.  The default values are
"nobody" and "nogroup" (they should probably be tweakable at compile time...)

Note that this does not provide full privilege separation, as there are still
channels between the parent and child processes which need to be monitored,
but it is an improvement on the previous situation.


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

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

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

varnishncsa is now able to produce backend logs. A couple of problems still remain: missing hostname and timestamp for backend communication. This could be solved with some extra tags serving the same purpose as ReqStart and ReqEnd does for client communication, providing this information.



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

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