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

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

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

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

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

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

	sub vcl_deliver {
		set resp.http.phk = "Beastie" "Rules";
	}

Would result in a new header line:

	phk: BeastieRules

Notice that strings are concatenated directly, you add spaces, commas etc
where you want them.

Other variables which have STRING format (or which can be converted to
STRING format) can also be used:

	sub vcl_deliver {
		set resp.http.phk = "Server is: " resp.http.server ;
	}

Could result in:

	phk: Server is: Apache/1.3.x LaHonda (Unix)




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

	sub vcl_deliver {
		remove resp.http.etag ;
		remove resp.http.server ;
	}



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

default VCL



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

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

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

the VCL methods vcl_miss and vcl_pass.



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

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

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

wires, rather than when they get manipulated in memory.


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

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

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

There should be no functional change as a result of this.



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

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

of timestamps and clock_gettime() throughout Varnish needs reviewing (as
per IRC discussion with phk)


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

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

current time, the latter returns the number of seconds since an object
was last requested.  The exact semantics of both are slightly fluid at
the moment, and will be revisited at a later date.


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

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

script.


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

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

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

processing pending messages before we exit.

Note that VSL_Dispatch() will read in log data as fast as it can, so when
working from a log file, varnishreplay will usually read in the entire file
into memory within the first few seconds.


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

(See architect notes on wiki for reasoning)


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

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

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

we still reuse the structure.


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

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

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

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

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

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

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

be performed.


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

the various VCL methods.

Loose the state names, they're obvious in the source code.



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

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