This is how long time we wait for a TCP connection to the backend to
become established.

Typical usage:

		backend b1 {
			.host = "hex";
			.port = "80";
			.connect_timeout = 500 ms;
		}

It can also be used in backends in director declarations.

Also add a parameter called "connect_timeout" which sets the default
to 400 msec (a number pulled out of my old black magicians hat).




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

any connections at all, that they didn't even consider that maybe
connect(2) should have a timeout argument.

Add TCP_connect() which addresses this shortcoming, using what I
belive is a widely supported workaround.

Not to POSIX: please fix.



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

It works just like regsub(), but replaces all occurrences of the regexp.

	regsub("1foofoofoo2", "foo", "bar") -> "1barfoofoo2"

	regsuball("1foofoofoo2", "foo", "bar") -> "1barbarbar2"

Fixes ticket 238



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

Accept sockets are non-blocking, to avoid races where the client closes
before we get to accept it.  (Spotted by: "chen xiaoyong")

Unfortunately, that means that session sockets inherit non-blocking mode,
which is the opposite of what we want in the worker thread but correct
for the acceptor thread.

We prefer to have the extra syscalls in the worker thread, that complicates
things a little bit.

Use ioctl(FIONBIO) instead of fcntl(2) which is surprisingly expensive.


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

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

fondling fcntl(2) directly.


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

Closes ticket #239


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

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

(not-RFC2616 compliant) request.



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

are passed to it.

If no method is provided, we fall back to vca_pipes.

closes #227


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

Spotted by:	"postwait"


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

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

debugging:

Implement an upper limit for allocated memory, specify as:
	-smalloc,40M

Give the malloc allocator its own stats counters so we can see deeply
into what it does.



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

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

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

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

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

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

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

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

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

Two really bad ones in Vary processing, found by Arjan (noosius).

One isignificant one related to -b arguments being wrong,
found by FlexeLint after I taught it how to spot this kind of issue.



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

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

"Authentication" for this long without anybody noticing until now.

Mea Culpa.



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

string for the status code as found in RFC2616.


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

changelog entries, cleaned debian/rules.


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

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

(IOV_MAX < (HTTP_HDR_MAX * 2)) is equivalent to (IOV_MAX < (0 * 2)),
which obviously is never true.  Fixes #222.

Submitted by:	Jyri J. Virkki <jyri@virkki.com>


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

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

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

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

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

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

possible for various modules to add cli functions so they can
be manipulated on the fly.

CLI_AddFuncs() registers a set of CLI functions.  We operate
with three lists: the ones not shown in "help" because the
manager already showed them, the normal ones and the debug
commands which are also not shown in a plain "help".

Move the registration of cli functions out to the code they
belong in: VCL, BAN and VCA.

Give VCA a real Init function, and have the cli function ("start")
initiate the acceptor thread which listens for incoming connections.

Split CLI_Init() into CLI_Init() and CLI_Run()



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

in malloc'ed memory.


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

of overloading common cli function namespace "cli_func".


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

not have to grope around in the cacher's data structures.

Whenever the manager gets a CLI command it does not understand, it
will pass it to the cacher process, if it is running.

This complicated "help" a little bit, because we want to show the
combined commands of the manager and cacher.

Since we're dealing with help anyway, hide undocumented debug
commands from it.



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

with '-'.

Remove header line.

If argument is not found, return CLIS_UNKNOWN.


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

tiny braino.


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

Noticed by:	Jyri J. Virkki <jyri@virkki.com>


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