[master] 9336043 RFC OCD

[Dridi Boukelmoune]

commit 9336043547d0f1567cb32ad5bc8d2f9029b2730a
Author: Dridi Boukelmoune <dridi.boukelmoune at gmail.com>
Date:   Wed Sep 14 13:06:28 2016 +0200

    RFC OCD
    
    rfc7231#section-4.3.3
    
    Responses to POST requests are only cacheable when they include
    explicit freshness information (see Section 4.2.1 of [RFC7234]).
    
    rfc7231#section-4.3.4
    
    Responses to the PUT method are not cacheable.
    
    rfc5789#section-2
    
    A response to this method is only cacheable if it contains explicit
    freshness information (such as an Expires header or "Cache-Control:
    max-age" directive) as well as the Content-Location header matching
    the Request-URI, indicating that the PATCH response body is a resource
    representation.  A cached PATCH response can only be used to respond to
    subsequent GET and HEAD requests; it MUST NOT be used to respond to other
    methods (in particular, PATCH).

diff --git a/doc/changes.rst b/doc/changes.rst
index bea3095..6ba0022 100644
--- a/doc/changes.rst
+++ b/doc/changes.rst
@@ -15,8 +15,9 @@ Major items:
 
 * (Very!) experimental support for HTTP/2.
 
-* Always send the request body to the backend, allowing caching of
-  POST, PUT, PATCH etc with appropriate custom VCL and/or vmods.
+* Always send the request body to the backend, making possible to cache
+  responses of POST, PATCH requests etc with appropriate custom VCL and/or
+  vmods.
 
 * hit-for-pass is now actually hit-for-miss.