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

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

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

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

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

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

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

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

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

isn't anything else we can do sensibly.

Fixes: #787



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

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

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

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

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

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

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

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

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

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

of symbol is much larger.



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

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

than have three different ones.



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

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

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

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

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

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

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

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

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

http_cache.h, and use the integer representation everywhere else.



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

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

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

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

beresp.backend.name (STRING)
	VCL name of backend fetched from.
	This name may have the form "somedirector[29]" if backends
	are declared directly in directors.

beresp.backend.ip (IP)
	IP number of remote end of connection.

beresp.backend.port (INT)
	TCP port number of remote end of connection.

Fixes:	#481


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

to expire now.

Reverse the order objects are inserted on the objhdr list to newest
first.



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

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

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

In general the "be liberal in what you accept" is a good thing, but
I am not going to be liberal about anything that could cause us to
return wrong content.

The truly consistent thing to do would be to error the fetch, but that
is a bit on the harsh-side for this specific cornercase, so I have
added a test to ignore the first character of the vary header, if it
is a colon.

Fixes:	#763



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

assert is bogus.

There is a window from our lookup until we lock the refcount where
a different thread conceiveably could loose the last reference to
the objhdr, before we get the lock to increase it.

The situation the assert was meant to protect, where we insert 
a new objhdr, is handled in the "oh == noh" clause earlier, were
the weaker "> 0" check is used (rather than "== 1") to cater for
the exact same race.

Fixes: #761
Fixes: #783



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