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

end of the file.


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

When we cache an object with a "Vary:" header, we generate
a "vary matching string" which can be used to efficiently
check for compliance when doing a cache lookup.

Only very lightly tested (ie: cnn.com).

For a full description of the reasoning, please see
	http://varnish.projects.linpro.no/wiki/ArchitectureVary



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

perfectly good pipelined data.



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

strndup which might come from the former.


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

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

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

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

(Varnish Stream Sockets) as I intend to eventually add support for AF_UNIX
sockets.

This also moves the accept filter code out from VSS_listen() (previously
TCP_open()) and into a separate function in tcp.c


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

* Make http auth work



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

pointer gymnastics getting out of hand.

In addition to the obvious alloc/return primitives there are also 
reserve/release primitives for when we don't know the length yet.



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

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

require gcc 4), tune autogen.des accordingly.


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

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

and which is copied to the shared parameter block every time a parameter
changes as well as immediately before forking off a child.  This prevents a
hypothetical compromised child from changing the parent's idea of run-time
parameters (which would, for example, allow it to trick the the parent into
starting a new, hypothetically exploitable child with the attacker's choice
of uid / gid).

While I'm here, correct the use of the "volatile" qualifier - it is the
parmeter block itself which can change unpredictably, not the pointer.


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

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

user and group to which the child process will switch immediately after fork()
returns, before it starts accepting connections.  The default values are
"nobody" and "nogroup" (they should probably be tweakable at compile time...)

Note that this does not provide full privilege separation, as there are still
channels between the parent and child processes which need to be monitored,
but it is an improvement on the previous situation.


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

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

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

varnishncsa is now able to produce backend logs. A couple of problems still remain: missing hostname and timestamp for backend communication. This could be solved with some extra tags serving the same purpose as ReqStart and ReqEnd does for client communication, providing this information.



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

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

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

- Fixed initrc-script bug only visible on el4 (fixes #107)



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

references to the object, so HSH_Deref() will free its storage.


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

caching of backend issues.

Brief summary:

 - moved http_msg array from cache_response.c to cache_http.c,
   introduced http_StatusMessage() lookup function

 - introduced http_Put{Protocol,Status,Response} to complement
   http_PrintfHeader().

 - introduced SYN_ErrorPage() in a new file, cache_synthetic.c.
   SYN_ErrorPage() populates the session's current object with the
   specified error code and a corresponding HTML error page; it is the
   caller's responsibility to ensure that the session has a suitable
   object (i.e. one that doesn't already have headers or a body)

 - rewrote RES_Error() to simply call SYN_ErrorPage() (with ttl = 0) and
   RES_WriteObj().

 - rewrote cnt_fetch() to use SYN_ErrorPage() to create a 503 page with
   a TTL of 30 seconds when Fetch() fails.

 - removed the call to RES_Error() in cache_backend.c; the error
   trickles back up to cnt_fetch() anyway.

Comments from review:

 - Memory allocation and pointer gymnastics for the header and body
   are duplicated all over the place (in new and pre-existing code)
   and should be centralized and hidden behind a suitable API.

 - The http_*() API needs refactoring, we shouldn't need four
   different functions to manipulate four different entries in the
   same array.


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

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

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

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

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

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

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

successfully locked it.


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

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

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

Remove "oknodo" to actually provide an error message if we cannot stop the service.

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

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

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

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

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

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