[master] 05d0d53 rewrite for readability

Per Buer perbu at varnish-software.com
Thu Feb 20 20:23:20 CET 2014

commit 05d0d5306e558096d39f57641559ab4f9a08e834
Author: Per Buer <perbu at varnish-software.com>
Date:   Thu Feb 20 19:28:48 2014 +0100

    rewrite for readability

diff --git a/doc/sphinx/tutorial/introduction.rst b/doc/sphinx/tutorial/introduction.rst
index 5241575..3f65968 100644
--- a/doc/sphinx/tutorial/introduction.rst
+++ b/doc/sphinx/tutorial/introduction.rst
@@ -8,23 +8,23 @@ clients and tries to answer them from its cache. If it cannot answer
 the request from its cache it will forward the request to the backend,
 fetch the response, store it and deliver it to the client.
+When Varnish has a cached response ready it is typically delivered in
+a matter of microseconds, several orders of magnitude faster than your
+typical application server, so you want to make sure to have it answer
+as many of the requests as possible.
 Varnish decides whether it can store the content or not based on the
 response it's gets back from the backend. The backend can instruct
 Varnish to cache the content with the HTTP response header
-Varnish will be very careful when it encounters cookies, either coming
-from the client or from the origin server. When Varnish sees a
-Set-Cookie header on a response it decides that the object is not
-cacheable. When there is a Cookie header in the request it will also
-refuse to serve a cached object and rather ask the backend for version
-of the object that is tailored to the request.
+Cache-Control. There are a few other conditions where Varnish will not
+cache, the most common one being cookies. Since cookies is a good
+indication that a web object is personlised, Varnish will with it's
+default configuration, not cache it.
 This behaviour and most other behaviour can be changed using policies
 written in the Varnish Configuration Language. See the Users Guide
 for more information on how to do that.

More information about the varnish-commit mailing list