Add a stevedore named "Transient" if the user did not already do that.
By default it is a size-unconstrained -smalloc.

Do not select the stevedore named "Transient" automatically.



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

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

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

magic symbols instead for consistency.

Various tightening of bolts and painting of scratches.



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

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

Fixes: #686



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

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

subject to refcounting.

Fixes: #812



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

contain comma-separated lists, can be spread over multiple header
lines.

There is no way of knowing if this rule applies to any header not
in RFC2616, short of chasing down the relevant standards document,
if any, for the particular header.
 
Considering the fact that HTTP header lines have no natural
limitation on length AND that RFC2616 already specifies a mechanism
for header-continuation, this doesn't add any value, at all.
 
It is hardly a surprise that nobody used this either, so until now,
we have ignored this silly stuff and just used the first header we
found.
 
But now Chromium, of all things, seems to find it necessary to
spread its Cache-Control across two lines, and we get to deal
with this crap.
 
Add a function for stitching multiple header lines into one, and
call it on Cache-Control in requests to deal with Chromiums issues.

Since we have it, call it preemptively on Cache-Control and Vary
in backend responses, since the C-code examines these fields.

XXX: At some point, add VCL support for collecting specific headers
this way.

Fixes: #686



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

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

They do what you expect.

Remove the native VCL "log" action.

Add generic VRT_StringList() which will build a STRING_LIST into
any sized buffer, so that std.log() can build the string on the stack.



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

(on error and unconditionally).

Drop the LOG into the /tmp/vtc.* directory if we leave it behind.

Sync usage() to reality.



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

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

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

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

specified:  -d, -b, -f, -S or -T

In human terms, this means that it is legal to start varnishd without
a Vcl or backend, but only if you have a CLI channel of some kind.



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

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

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

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

documented return, restart, reordered some docs for readability and elaborated on saint and grace mode

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

VM interfaces.

Fix an assert to be correct.




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

Run tests in fork'ed subprocesses.
Support for running tests in parallel.
Command arguments straightened out.

Needs polishing, but I need to sleep.



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

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

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

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

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

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

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

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

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

like Solaris which do not have pthread_timedjoin_np()

Fixes: #800


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

Fixes: #789



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

header.

Until now, we have not allowed IMS on objects without LM header but
after due consideration of our role as web-server, that restriction is
found too hard:  Varnish will, by definition, not find and object which
is not valid, so we can trust the time we put it into the cache to
be the LM date.

But we can not synthesize a LM header based on this, as this would allow
down-stream client-side caches to make unwarranted decisions (see RFC2616
13.3.4 p88)

Fixes: #795



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

of the present time.



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

otherwise we cannot pass a 304 with a Content-Length.

(RFC2616 p33 4.4)

Fixes: #806


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

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

redhat/fedora initscript: Default-Start and Default-Stop for lsb compliance. The defaults are empty.

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

redhat/fedora initscript: Default-Start and Default-Stop for lsb compliance. The defaults are empty.

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

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

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