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

purges before we test their numbers.



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

Let purge.list prune the tail of the list before dumping.



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

For instance:

	purge req.http.host ~ www.foo.com && req.url ~ "\.png$"
	purge obj.http.set-cookie ~ USER=383839

Now, why would you want purge on request headers and not object headers ?

Simple, some information the object does not have, the Host: header is
a good example.

Assuming that the Host: header is part of the hash we use to lookup
an object (as is the default), we can avoid copying that field into
the object (saving memory: O(nObjects)) by using the request value
to purge against.




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

You can now purge using these four conditionals:

	purge req.url == "/diediedie.html"
	purge req.url != "/index.html"
	purge req.url !~ "\.html$"
	purge req.url ~ "\.jpg$"



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

Emit && \ for line continuation.



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

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

unused, "how" argument flag.

We currently have far too many "quote this string properly" implementations
in varnish, hopefully, this will replace most of them.

Once this stabilizes, vsb_quote() will be contributed back to FreeBSD.




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

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

the session a bit to transfer the per-request stats to the session
counters with SES_Charge().

Not only was it inconsistent to charge accounting data in the middle
of a request, it was also illegal because after the hash lock was
released we no longer owned the session.

Once a system is under sufficient load that there is a queue for the
CPU, a race could happen where upon hitting a busy object, the hash lock
was released, another thread would schedule, finish the busy object,
start the sessions on the waiting list, finish off the request we had
and then when we get the cpu again and access it, it's gone.

The previous commit (r3512) eliminated the need to call SES_Charge,
this commit removes the (option) shmlog message inside the hash lock
thus, hopefully, eliminating the race that caused #418.

Fixes: #418


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

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@3512 d4fa192b-c00b-0410-8231-f00ffab90ce4

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

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

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

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

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

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

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

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

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

Fixes #376



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

the transaction.

Fixes #387



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

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

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

Give it proper semantics



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

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

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

Fix indentation.



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

socket, but took to.



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

Assert that we read the C-source file.



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

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

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

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

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

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

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