to the client or not.



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

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

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

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

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

stevedore which matches the name exactly.



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

inside vcl_fetch()



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

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

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

this is much cleaner and does not demand a brand new python interpreter.



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

bytes and make the two stevedore space variables that type.



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

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

Be a total CPP-show-off-douche and make it very easy to add further
variables in the future, provided you can find the magic table.

Presently define three variables:


	REAL storage.$stevedore.free_space
	REAL storage.$stevedore.used_space
	BOOL storage.$stevedore.happy

Still debating if I should add a "SPACE" type to VCL, so that you
can write:
	if (storage.foobar.free_space < 1 GB) {...}

until I decide, it is a REAL, which is less than useful, because
we have no relational operators besides identity for REAL.



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

Presently, you can only test for the existence of a given stevedore,
but it gets a lot of support code in place.



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

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

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

This is a generalization of the trick we have used for things like
req.http.foobar, which can now also be used with other parts of
the namespace.

The plan is to use it for storage.disk1.free and similar.



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

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

We will no longer allow an object to be split across multiple
stevedores, because the necessary logic to allow control of which
stevedores allow this (malloc, file) vs. those that cannot tolerate
this (persistent) is just not worth the effort.

It is very dubious if there are any non-disadvantages to splitting
objects across stevedores in the first place.



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

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

Re-open #310 for 2.1.4 - trunk checks out fine.

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

the fixed location HTTP fields.

Prodded by: email from anordby, in re r4603



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

Fixes: #411


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

Fixes #794

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

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

Spotted by:	sky



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

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

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

in critbit to avoid a malloc in the locked path.

Move the waitinglist to its own structure in preparation for Big
Things Afoot which will give it more work to do.  This saves a
pointer in objhead on average, always a good thing.

Have the worker thread preallocate a waitinglist structure.



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

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

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

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

	STRING vmod_std.fileread(STRING filename)
function, which will read the contents of a file, typically
for use in synthetic responses.

Submitted by:	Sanjoy Das


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

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

version 1.0 to mark support for here-documents.



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

them from becoming an out of memory DoS.



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

The last argument to any CLI command can use this feature.

Typical example:

	vcl.inline vcl_new << 42
	backend foo {...}
	sub vcl_recv {...}
	42

The advantage is that no escaping is needed, as long as the magic
marker, in this case "42" does not match any line anywhere in the 
lines that make up the argument.

Arguments encoded this way are not subject to the "cli_buffer"
parameters size limitation.



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

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

reflect the sum of obj.ttl and obj.grace.

Obj.grace if not set, default to $default_grace, which might have
a different value when we open the silo in a new run.

Solve this, by saving the ttl as the negative sum of (obj.ttl + obj.grace)
if obj.grace is set, or the positive obj.ttl if it is not, and by
adding $default_grace to obj.ttl in the latter case.



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

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