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

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

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

Improve a couple of type related error messages.



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

Make TIME - TIME = DURATION work



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

Fixes #777



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

Fixes #629



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

Fixes #670
Fixes #671



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

we drop the session before we have rendered the clients address.

Report IP and port as "-" rather than passing NULL pointers, which
is not nice under any, and core dump solaris under some circumstances.

Fixes:	#598



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

Refuse assignment of empty strings to line1 proto fields, issue VSL
record LostHdr.

line1 proto fields are request, url, proto and response. status is
numeric and not affected.

Fixes: #781



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

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

private pointers.



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

Will describe evil details in sphinx docs in a moment.



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

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

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

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

Don't try to trim a storage segment we filled completely.

Fixes: #776



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

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

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

new structs are added.



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

This allows us to collect lock collision information without
incurring the overhead of VSL, which should give more relevant
and precise information.



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

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

Fixes: #769


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

Fixes: #768



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

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

Fixes: #762


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

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

client connection:

	VOID set_ip_tos(INT)

Fixes:	#773



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

A procedure is simply a function which returns VOID.



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

in expressoins.



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

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

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

attempted imported more than once.



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

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

a default.vcl file we know will exist.



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

fleshed out the directors a bit more. unsure about if the hash/client dir take the retries parameter

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

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

We want to access files in the build directory, not the source
directory.


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

The effect of this is that the root object in the binheap could be
wrong and thus hold the expiry thread hostage, even though other objects
were ripe for expiry. 

This would show up as inflated obj/objcore/objhdr counts, but have no
other deleritous effects.

Detected, conclusively, by:	sky


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