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

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

http header which we can use to build the object headers in.



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

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

and define this as the "start of request timestamp".

Define "end of request timestamp" as when we are ready to transmit
HTTP header back.

SHMlog the start and difference between start and stop with ReqServTime
tag.

Keep track of idle sessions using CLOCK_MONOTONIC to avoid trouble
here should our clock get stepped.




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

Added some more toying with the data. All is still a mess, and I am not sure of structure yet. PHK is also doing changes in areas that will be needed.

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

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

	{Rx,Tx,Obj}{Request,Response,Status,URL,Protocol,Header,LostHeader}

And log http header munching accordingly.



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

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

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

we checked if the request is a GET long after we should have.



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

Eliminate the header index from http_SetHeader() which is no unused.



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

we don't get two confusing batches of TxHeader in the sessions logentries.


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

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

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

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