[master] fbc9e69 Removed the subs chapter.

Per Buer perbu at varnish-cache.org
Tue Feb 19 17:25:55 CET 2013

commit fbc9e698825cd222319745ede2a4e307c3316427
Author: Per Buer <perbu at varnish-software.com>
Date:   Tue Feb 19 17:26:06 2013 +0100

    Removed the subs chapter.
    It's in it's own file now, based on the VCL manpage.

diff --git a/doc/sphinx/index.rst b/doc/sphinx/index.rst
index 9d948b4..1cc29c6 100644
--- a/doc/sphinx/index.rst
+++ b/doc/sphinx/index.rst
@@ -16,7 +16,7 @@ our tutorial - :ref:`tutorial-index`.
 .. toctree::
-   :maxdepth: 2
+   :maxdepth: 1
@@ -30,6 +30,3 @@ Indices and tables
 * :ref:`genindex`
 * :ref:`search`
diff --git a/doc/sphinx/users-guide/vcl-subs.rst b/doc/sphinx/users-guide/vcl-subs.rst
deleted file mode 100644
index d759b2a..0000000
--- a/doc/sphinx/users-guide/vcl-subs.rst
+++ /dev/null
@@ -1,25 +0,0 @@
-vcl_recv (yes, we're skimpy with characters, it's Unix) is called at
-the beginning of a request, after the complete request has been
-received and parsed.  Its purpose is to decide whether or not to serve
-the request, how to do it, and, if applicable, which backend to use.
-In vcl_recv you can also alter the request. Typically you can alter
-the cookies and add and remove request headers.
-Note that in vcl_recv only the request object, req is available.
-vcl_fetch is called *after* a document has been successfully retrieved
-from the backend. Normal tasks her are to alter the response headers,
-trigger ESI processing, try alternate backend servers in case the
-request failed.
-In vcl_fetch you still have the request object, req, available. There
-is also a *backend response*, beresp. beresp will contain the HTTP
-headers from the backend.

More information about the varnish-commit mailing list