Fixes #600

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

Fixes #547



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

Fixes #591



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

This gives us backtraces on panic on when you're not using GCC.

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

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

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

This was originally a quick hack to allow purging to take the Host:
header into account.

We have a much better and precisely expressive purge syntax now, so
this hack can die.



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

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

Print out how long the testing took and which test took the longest.



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

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

Make the varnish accept address just use a random free TCP port.

Fix a couple of tests where we need to know the port number.



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

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

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

address(es)



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

the hardcoded server port here also



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

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

in VCL snippets.



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

parse.



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

explicitly specified, and use macros to pick up the result
as necessary.



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

and make the listen address explicit where we depend on it, rather
than rely on the default port to be 9080.



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

the vcl based on same.  This allows the port to be specified as
zero rather than a hardcoded number.



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

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

refer to things like servers ip/port rather than hardcode it.




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

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

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

Tip o' the hat to: tfheen



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

request, some backends gets confused by this.

Add a ".status" to backend polling, to configure the expected HTTP
status code for a good poll.

Fixes #584



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

my users have:

Do not load new segments opened after we started, even if multiple such
have been created, before we finish loading the old segments from the
silo.

Fixes	#564




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

Fixes #559



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

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

On 32 bit systems, it may be necessary to tweak this down to get high
numbers of worker threads squeezed into the address-space.

I have no idea how much stack-space a worker thread normally uses, so
no guidance is given, and we default to the system default.

Fixes #572


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

Previously we stored the esi-metadata in the object workspace, but since we
are trying to make that a snug fit and we cannot preestimate how much space
ESI parsing will need, this no longer works.

Instead parse the ESI metadata into the workers workspace and when
done, allocate a storage object and move it all into that.

Beware that this may increase the memory cost for ESI objects by the stevedores
granularity.

Fixes #578



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

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

We do not want to be dependent on GCC.

Fixes #577



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

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

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

Now that we need PCRE to build, we also do need pkg-config at
autoreconf time, so make autoconf complain as early as possible to not
confuse people.

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

Previously, running varnishd -V would sometimes say:

nm: 'varnishd': No such file

which is wrong.  Silence this message

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

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

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