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

prefix "VEV".

This is a general purpose eventmanager and as such should live in
the library where other programs can get at it.



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

Add a backend property ".host_header" to set default content of Host:
header if client didn't provide one.

If .host_header is not specified, it defaults to .host.

Add testcase for this logic.

(Incidental change: Use "interval" instead of "rate" for backend pollers.)





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

It doesn't actually do anything yet.



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

clear expression of intent in VCL.

We now fail backend hostnames that resolve to multiple IPv4 or multiple
IPv6 addresses, in other words, you cannot use "cnn.com" as a backend
hostname specification without the compiler yelling at you:

    % ./varnishd -d -d -b cnn.com -a :8080
    Backend host "cnn.com": resolves to multiple IPv4 addresses.
    Only one address is allowed.
    Please specify which exact address you want to use, we found these:
	    64.236.16.20
	    64.236.16.52
	    64.236.24.12
	    64.236.29.120
    [...]
    VCL compilation failed

However, you _can_ use a hostname that resolves to both an IPv4 and
an IPv6 address, and the new paramter "prefer_ipv6" will determine
which one we try first in such cases.

The other part of this change is that we now do the DNS lookup at
VCL compiletime, and only then.

If your backend's DNS record (or /etc/hosts entry) changes IP#, you
must reload your VCL code to notify varnish.

Finer technical points:

We build a bytestring representation of the sockaddr's in VCC and
include them in the concept of backend identity, for an existing
backend (+ connections) to be reused for a new VCL the backend must
now be defined exactly the same way AND have the same resolved
IPv4/IPv6 addresses.

Since we never muck about with the address in the backend struct
anymore, it's static for the life of the struct backend instance,
we can simplify and eliminate the locking dance around our connection
attempts.

Also eliminate the struct vrt_backend inclusion in struct backend,
and instead make the relevat fields full-blown members of struct
backend.  This eliminates a number of TRUST_ME() calls.

This is the companion commit to #2934 which prepared the VCL compiler.


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

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

IPv6 addresses, but accept one of each.

Emit a bytestring representation of the sockaddr we found for each
of these, into the shared object, so we avoid doing a DNS lookup
again in the cacher.



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

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

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

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

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

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

	<esi:include  foo=bar src=/body2 />



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

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

	<esi:include  src= />
would result in a NUL byte when looking for the next attribute.



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

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

Ignore unknown include attributes and
Warn about src attributes without value



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

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

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

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

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

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

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

backend hosts.



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

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

with each other.



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

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

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

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

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

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

"available" or "discarded".



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

VCL programs, but in practice it didn't happen because we fired the
GC function VCL_Idle() after 5 seconds of silence on the CLI port and
the manager pings every three (by default).

Instead change the name of VCL_Idle() to VCL_Poll() and call it
before every CLI command, so that any query command will get an
up to date status.



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

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

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

more complicated than a single file can carry.

cache_backend_cfg.c now contains the configuration and selection of
backends and directors.

cache_backend.c contains the connection and request management against
backends.



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

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

in VCL.



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

It is possible to specify just the URL to be probed, or to specify the
entire HTTP request:

	backend b0 {
		.host = "127.0.0.1";
		.probe = {
			.url = "/test.jpg";
			.timeout = 224 ms;
		}
	}

	backend b1 {
		.host = "127.0.0.1";
		.probe = {
			# NB: \r\n automatically inserted after each string!
			.request =
			    "GET / HTTP/1.1"
			    "Host: www.foo.bar"
			    "Connection: close";
			.timeout = 0.3 s;
		}
	}

If the full request has not been completed within the timeout, the
backend will be set to down.


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

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