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

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

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

gcc >= 3.3.
Now compiles on pristine etch-systems


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

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

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

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

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

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

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

WARNING: varnish will build and run, but the lack of a monotonic clock
may lead to strange behaviour if the clock is stepped (rather than skewed)
while varnish is running.

Thanks to Niklas Saers for providing a test environment.

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

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

even though it is not used, and will return EFAULT if one is not provided.

Also, instead of silently accepting EBADF from epoll_ctl(), check that
sp->fd != -1 before calling vca_del().  This can happen in some cases
where vca_pollsession() closes the session before returning.  This way,
we will still get an assertion failure if epoll_ctl() fails for some
other (unexpected) reason.

Thanks to airmax for his assistance in tracking this down.

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

the response, not the time of the request.  If the document was not in
cache and the backend took a long time to respond, the document would
end up with a negative computed age, which when printed with %u would
appear as a large positive number (a few seconds short of either 2^32
or 2^64 depending on the size of time_t).

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

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

own mechanism for specifying a required version doesn't seem to work.
Hack autogen.sh to check which version of automake is installed.

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

and Ubuntu) do not understand --force[-missing], and we can do without.

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

modified) responses MUST NOT include a message-body," so
Content-Length: is not needed in these cases (and Apache does indeed
not include it).  This causes PassBody() to call pass_straight() with
a NULL length argument, which waits until the connection is closed by
the server.  PassBody() should not call pass_*() at all for responses
that are known to be bodyless.

Submitted by:	Dagfinn Ilmari Mannsåker <ilmari@ping.uio.no>


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

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

that done later today.

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

varnishlog's request selection feature.

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

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

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

just -O is not enough to prevent gcc from optimizing away loop variables.

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

Ticket:		#46

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

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

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

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

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

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

on a production server, but it will on a test rig, and it may confuse and
alarm the admin.

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

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

Note: Still builds with warning.



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

Fixed: Status variable is not shown correctly.
Added: base64() decode of Remote User.

Note: Getting compile warning.



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

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

Detected by:	Xing Li <xing@litespeedtech.com>


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

Spotted by:	Anders Hanssen <anders@rethink.no>

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

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

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

varnishhist(1).

Spotted by:	Anders Hanssen <anders@rethink.no>

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