git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4764 d4fa192b-c00b-0410-8231-f00ffab90ce4

Fix one of those "nothing can possibly go wrong" bugs that are so
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/branches/2.1@4763 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4761 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4760 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4727 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4725 d4fa192b-c00b-0410-8231-f00ffab90ce4

Hit by: dormando


git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4724 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4723 d4fa192b-c00b-0410-8231-f00ffab90ce4

Spotted by: dormando
Testing by: Kristian

Fixes: #684


git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4722 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4721 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4720 d4fa192b-c00b-0410-8231-f00ffab90ce4

Patch by Robert Scheck <robert@fedoraproject.org> for varnish >= 2.1,
which adds the missing (former implicit) linking to libm. And as
implicit linking can be dangerous, this changed, see:
http://fedoraproject.org/wiki/Features/ChangeInImplicitDSOLinking

Commited by Ingvar. This is necessary to make varnish build on
fedora>13.



git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4714 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4713 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4711 d4fa192b-c00b-0410-8231-f00ffab90ce4

Also support: bytes=-%d bytes=%d- bytes=-

And ignore plain wrong cases, such as starter past end of object or
end before start etc.



git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4710 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4709 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4708 d4fa192b-c00b-0410-8231-f00ffab90ce4

By default it is disabled, enable with param http_range_support.



git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4707 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4705 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4704 d4fa192b-c00b-0410-8231-f00ffab90ce4

See test-case for details.


git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4703 d4fa192b-c00b-0410-8231-f00ffab90ce4

it was a really bad idea to call "bans" for "purges" some places.


git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4695 d4fa192b-c00b-0410-8231-f00ffab90ce4

changes it advertized:

Align all WS allocations.



git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4694 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4693 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4692 d4fa192b-c00b-0410-8231-f00ffab90ce4

Though it works fine, varnishhist and *sizes should probably be merged
together at some point.



git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4691 d4fa192b-c00b-0410-8231-f00ffab90ce4

early, since it also affects pipe and pass processing.

Move the HEAD->GET override to vcl_miss{} and do it on the bereq.* so
we do not tamper with the original request.

Fixes:  #679



git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4688 d4fa192b-c00b-0410-8231-f00ffab90ce4

Spotted by:     Mark Moseley



git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4687 d4fa192b-c00b-0410-8231-f00ffab90ce4

Add plenty of asserts until we see that the world don't end.



git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4685 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4684 d4fa192b-c00b-0410-8231-f00ffab90ce4

alignment of allocations in workspace.



git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4683 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4682 d4fa192b-c00b-0410-8231-f00ffab90ce4

functions and consume its token.



git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4681 d4fa192b-c00b-0410-8231-f00ffab90ce4

life easier for Kristian, and to eliminate some code duplication.



git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4680 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4679 d4fa192b-c00b-0410-8231-f00ffab90ce4

This was forgotten when number of HTTP headers was made dynamic.

The lack of this function may have made ESI includes weird.

Should be merged to 2.1



git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4678 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4677 d4fa192b-c00b-0410-8231-f00ffab90ce4

We clean the child process of unwanted open filedescriptors, but this
can
take time if there are hundreds of thousands of possible
filedescriptors.

Instead do it once, right at startup in the manager process, and then
keep track of the fd's we use there, and have the child clean only
up to the max seen, with an allowance for filedescriptors held by
libraries (syslog, resolver, pidfiles etc)

Fixes   #699



git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4676 d4fa192b-c00b-0410-8231-f00ffab90ce4

we forgot to close
the file descriptor, but this causes no trouble apart from a wasted
filedescriptor in the parent process.

But closing it is better :-)

Fixes:  #675
Spotted & Patch by:     Edmondas Girkantas



git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4675 d4fa192b-c00b-0410-8231-f00ffab90ce4

2.1 candidate



git-svn-id: http://www.varnish-cache.org/svn/branches/2.1@4674 d4fa192b-c00b-0410-8231-f00ffab90ce4