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

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

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

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

obj.http.*



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

single sourcefile, which appears in both libvarnish and libvarnishapi.



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

typical of "lets just try to get this into the release" features.

The resent addition of experimental Range: header support, broke
a cornercase in normal content delivery.

If an object was delivered from the backend using chunked encoding,
and was larger than the storage segment size (default: 128k) this
bug may bite.

The effect of the bug is that up to storage segment worth of junk
may be appended to the transmitted object.

This is mostly harmless, because the Content-Length header will make
the browser do the right thing, but certain load-balancers will
go cross-eyed and act really weird at the TCP level, spewing
interesting RST packets to the client.

This bug is only in 2.1.1, not in 2.1.0.

Fixes:			#694
Isolated by:		ay
Fool who did this:	phk


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

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

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

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

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

be used for the examples in the tutorial.

The argument is the base port TCP number for the examples.

Servers listen on ports starting 10 above the base.

Server -listen oand client -connect arguments are numeric offsets to
the base TCP port number.

Polish the log-message output a bit, both with and without -L.



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

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

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

mapping more VM than a 32bit machine can cope with, if /tmp is huge.



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

we are not trying to create a file but a directory.



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

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

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

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

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

work as expected.



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

VCC infrastructure to do so.

Fixes:	#638



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

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

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

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

bitmaps for read and write.



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

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

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

that looks like that.



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

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

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

version of the VCC generator script



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

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

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

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

through the hands-on.  Ended up starting a glossary instead.



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

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

Hit by:	dormando



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

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

Spotted by:	dormando
Testing by:	Kristian

Fixes:	#684



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