the connection first.  This fixes #168.


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

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

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

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

shouldn't need to malloc() / free() at all, but I don't have time to
figure out how to avoid it right now.


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

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

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

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

look for complete requests.


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

So far we support only the <esi:remove> element.

All other <esi:...> elements are ignored.



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

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

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

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

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

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

This is the meat of the XML-dissecting code.

In theory the task is pretty simple, but it gets complicated by the fact
that the XML input can be split over multiple pieces of storage, with
an element we care about straddling a boundary.

I have not decided what to do about ESI violations or XML syntax errors,
SHMlogging them, possibly controlled by a parameter might make sense.
For now mark them in the source.



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

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

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

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

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

Always enforce the 2GB filesize limit on 32bit architectures.
Clean up a couple of messages


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

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

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

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

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

chew than necessary.


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

front of the linked list where they will be found faster later on.


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

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

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

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

I thought so previously.



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

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

Possibly ticket #164


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

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

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

legitimate error conditions.


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

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

Make HTC_Rx() return a distinct value for overflow/blast.
Teach vca_handover() to handle HTC_Rx() return status
Use HTC_Rx/vca_handover this way in all three acceptors.
Eliminate vca_pollsession()
Teach CNT_First() about HTC_Rx states.
Log which acceptor we use in shmlog



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

Drop leading whitespace if so informed.


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

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