by keeping the current requests accounting stats in the worker thread.

For reasons which will be explained in the next commit, this is no
longer a good idea, and this commit moves these counters from
the worker thread to the session at a slight but all in all
trivial cost in memory footprint.

Remove the call to SES_Charge() when we hit a busy object, it is
not necessary to clean the worker thread counters here now.

Move these counters from the worker thread to the see


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

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

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

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

conditions to test.

This paves the way for a much more expressive ban/purge syntax where
things like:

	purge req.http.host ~ "web1.com" && req.url ~ "\.png"
	purge obj.age > 1w && obj.size > 1MB
	purge obj.http.set-cookie ~ "USER=838339" && req.url ~ "\.html"

become possible.

Not quite there yet though.



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

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

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

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

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

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

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

Fixes #376



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

the transaction.

Fixes #387



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

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

used to ignore the rest.

This is not a bright solution if crucial HTTP headers like
"Content-Length" or "Transfer-Encoding" are last and get ignored.

In general, it is highly suspect to randomly ignore HTTP headers,
as opposed to deliberately ignoring them, either by having first
looked at them and found them uninteresting, or by having looked
for the headers we care about, and having not matched some others.

Change too many headers to firm error condition: 400 if from the
client, and 503 (like every other trouble) if from the backend.

Fixes #416



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

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

Give it proper semantics



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

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

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

Fix indentation.



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

socket, but took to.



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

Assert that we read the C-source file.



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

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

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

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

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

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

This solves the "restart" procaction issue in a non-hackish way
and looks better overall.



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

elsewhere as required.

Remove unecessary args to VCL_[RM]ET_MAC().

Rely on VCL_RET_* definition in vcl.h



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

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

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

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

logging.


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

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

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

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

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

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

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

can be listend on.

Fixes #97


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