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

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

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

the first deflate block, the 'last' bit and the first (padding) bit after
the laste deflate block.

We need to know these in order to do the multi-evil gzip surgery for
ESI compression.



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

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

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

don't replicate common code.



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

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

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

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

sp->wrk variable where everybody can find it.



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

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

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

clash with the version hacks near the end of zlib.h

Will revisit once I know which subset of this library I actually need,
it will probably be possible to remove the entire gz* family functions.



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

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

when the client does not support gzip.



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

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

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

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

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

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

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

When there is no idle workerthread available, an incoming requests will
get queued until a thread becomes available.

We called this "overflow" because it overflowed the worker thread pool.

However, "overflow" gives the impression that the request is somehow
lost, which it is not.

"queued" gives a much more precise idea what goes on.



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

Rename 'purges' to 'bans' so that we can implement _real_ purges
also.

They really have been called 'bans' internally all the way through,
but for reasons now forgotten, we thought it would be too hard to
explain to people that purges were called bans in Varnish, so
the user-fronting side were named purges.

As it transpired, people were surprised that purges in varnish
did not free the storage right away, and various other kinds of
confusion also materialized.

The sky convinced me to implement real purges for efficiency
reasons when Vary is used, and of course now the name "purge"
was taken.

I'm sure people will curse about this change in the 2.x to 3.x
migration, but sooner or later it had to happen, and now it did.



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

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

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

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

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

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

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