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

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

address(es)



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

the hardcoded server port here also



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

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

in VCL snippets.



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

parse.



git-svn-id: http://www.varnish-cache.org/svn/trunk@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@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@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@4362 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk@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@4360 d4fa192b-c00b-0410-8231-f00ffab90ce4

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

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

Tip o' the hat to: tfheen



git-svn-id: http://www.varnish-cache.org/svn/trunk@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@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@4355 d4fa192b-c00b-0410-8231-f00ffab90ce4

Fixes #559



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

git-svn-id: http://www.varnish-cache.org/svn/trunk@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@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@4351 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk@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@4349 d4fa192b-c00b-0410-8231-f00ffab90ce4

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

git-svn-id: http://www.varnish-cache.org/svn/trunk@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@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@4338 d4fa192b-c00b-0410-8231-f00ffab90ce4

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

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

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

We no longer use POSIX style regexes, but rather PCRE regexes.  This
introduces a hard dependency on libpcre.

Test suite passes, but only lightly tested.

The regex functions are in its own source file to make it easy to
change the decision if somebody wants to use non-PCRE for some reason.

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

Fixes #420


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

Previously, trying to build from SVN without xsltproc installed would
get you errors like:

  --xinclude -o changes-2.0.1.html changes-2.0.1.xml
  --xinclude:No such file or directory

which is quite confusing.

We now rather just skip the docs completely if we can't find any
xsltproc.  If we actually do need to rebuild the docs (which should
only happen when running make dist), we error out with a useful error
message.



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

Fixes #557


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

When saintmode_threshold items have been added to the trouble-list, the
backend will be considerd sick until one has timed out. Setting the
threshold to 0 disables saintmode and any lock contention associated with
it.

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

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

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

Move the objindex pointer and length to the segment table, having it
in the segment signatures is just a waste of disk-access on startup.

Put empty signatures at segment head, objidx and segment tail.

Align allocations to 16 bytes boundaries, for cache and hexdump
convenience.

Discard unsused segments on close.



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

Only delete empty segments from front of list.

Preallocate the temporary object-index buffer at open time.



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

using malloc space.

Otherwise -spersistent would resurrect objects without their Vary
specifications.


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