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

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

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

reStructure'ized the old Trac faq and sorted the stuff into their temporary sections. Deleted old-faq.rst from filesystem and updated the index.rst. Now it's time to qualitycheck the content and remove old examples and outdated info.

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

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

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

Cleaned up some code in the general section. Used the ** marker for bolding the questions. Added a internal ref to the installation doc so we could use best-practice referencing. Added som stuff to FAQ/configuration.

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

Started some work on the FAQ. Split into different sections and ported some of the old faq from wikisyntax into ReST.\nNo real plan behind the split, just adding sections that seem useful to have as I go through the old FAQ.

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

Started some work on the FAQ. Split into different sections and ported some of the old faq from wikisyntax into ReST.\nNo real plan behind the split, just adding sections that seem useful to have as I go through the old FAQ.

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

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

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

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

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

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

In Learn mode, a backend port can be specified as

	backend fs {
		.host = "127.0.0.1";
		.port = Learn(2);
	}

which complements the varnishtest server::-listen directive:

	server s1 -listen 2 {
		rxreq
		txresp -hdr "Foo: bar" -body "Hello World!"
	} -start -wait

Obviously, the 127.0.0.1 is mandatory for this to work.


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

- enable -d
- set listen address to ($L)
- set telnet address to ($L + 1)
- if no storage configured, use "-smalloc, 1m"
- set -n to /tmp/varnish_L_$L
- set ping_interval to zero

Still missing:  VCC magic to hack backends port number.




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

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

- make struct VSL_data the uniform handle.
- eliminate global variables (this allows a program to have multiple
  shmlogs open at the same time).
- add a VSL_Delete() to clean up

This breaks libvarnishapi compatibility with the 2.x series.






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

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

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