no need to waste time printf'ing in this case, and no need to waste workspace.


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

have space for composing the reply as well.

Without this fix, the entire workspace could be filled with pipelined
requests and we would have no space to compose the reply.



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

NCSA-style (common / combined) logs.

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

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

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

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

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

Have WRK_Write() and friends return number of bytes (we can't use
WRK_Flush() as that may act on both header and body).

Collect more stats.



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

We (will) collect data in unlocked per workerthread accumulators
and whenever the workerthread leaves the session, we charge the
bill to the srcaddr (issuing a StatAddr shmrecord), to the session
and to the global counters in the stats struct.

When sessions die we issue a StatSess shmrecord.

StatAddr and StatSess has the same format:
	address
	port (always zero for StatAddr)
	duration (seconds)
	#sessions
	#requests
	#pipe
	#pass
	#fetch
	#hdrbytes
	#bodybytes



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

We fill it in with backend.hostname, but this may not be optimal
(direct IP# etc etc) so VCL should be able to override it.



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

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

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

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

For now we default to REG_EXTENDED, but it might make sense
to let the user control this flag and the case sensitivity.

Another concern is the stringification of regexps, it may lead
to backslash madness.  Maybe we should define '...' string types
also and do no backslash substitution in those at all.



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

the rule (ie: also !  and /mask if present).

Implement matching for IPv4.

Acl tests are shmlogged as follows (doc candidate):

	shmlog tag:	VCL_actl

	"NO_MATCH $acl"
		client did not match access list $acl
	"FAIL $acl $rule"
		getaddrinfo(3) failed on $rule which had a '!'
	"MATCH $acl $rule"
		client matched $rule
	"NEG_MATCH $acl $rule"
		client matched negated (!) $rule




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

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

	add two sbufs for "init" and "fini" actions.

VCL ACLs:  Change syntax and implementation as follows.

ACL Syntax now works the following way:

	acl $name {
		! ( "myhost.com" ) ;
		"10.0.0.1" /8 ;
	}

The '!' means not.  If the address matches the rest of the rule
the address does NOT match the acl and the search terminates here.

Enclosing the string in paranthesis means that the rule will be ignored
if the string cannot be converted to an address (with getaddrinfo).

When a string can not be looked up, and is not enclosed in a
paranthesis, a positive rule (ie: without !) will not match and a
negative rule (with !) will match.

A mask can always be supplied, no matter the style of the string
given, so it is possible to do things like:

	{ "fw.ourcompany.dom" / 24 }

Which means "any host on the same /24 subnet as fw.ourcompany.dom".


Unfortunately getaddrinfo() does not return a TTL for the results,
in the future we may want to use some kind of timeout to refresh
the lookups.




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

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

on 32 bit architectures to avoid running out of address room

Make FlexeLint happy.


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

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

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

Log in shmem where the TTL came from (doc-candidate):

	696613561 RFC 900 1153517009 1153517014 1153517914 900 0
        |         |   |   |          |          |          |   |
        |         |   |   |          |          |          |   age
        |         |   |   |          |          |          max-age
        |         |   |   |          |          Expires: header
        |         |   |   |          Date: header
        |         |   |   "now"
        |         |   TTL relative to "now"
        |         who set the TTL
        xid of object

or
	
	696613561 VCL 20 1153517009
	|         |   |  |
	|         |   |  "now"
	|         |   TTL relative to "now"
	|         who set the TTL
        xid of object




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

Use macros for trivial objects which are just a field in a struct.



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

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

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

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

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

VCL programs can manipulate.



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

Split some stuff into separate files while we're at it.



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

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

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

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

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

By default, start at the last entry in shared memory.  To dump the
entire segment from the start, specify '-d' option.

Terminate programs when '-r $file' reaches EOF



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

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

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

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

Remove sbuf from workerthread, it is only used in the Error handling
now and it will probably not even survive that in the long run.




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

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

NB: Only pass mode (lightly) tested right now.

Give up on the three element array per header and use a two element struct
instead, it reduces obfuscation and removes risk of pointer fandango.

Introduce #defined filtercontrol in http_headers.h, use them in a new
field.  Only Pass is there for now.

Use the http-workspace for building headers instead of sbuf.

Move uiovec handling to cache_pool.c where it more naturally belongs
and so we can use it on both backends and sessions.

Add http header munging functiosn for copying, printf'ing, filtering and
writing headers.




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