untangle relationship between pushing, promising, and caching.

httpwg · Feb 19, 2014 · 3cec55e · 3cec55e
1 parent 7bcac2a
commit 3cec55e
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/draft-ietf-httpbis-http2.xml b/draft-ietf-httpbis-http2.xml
@@ -2956,9 +2956,9 @@ HTTP2-Settings    = token68
           <x:ref>PROTOCOL_ERROR</x:ref>.
         </t>
         <t>
-          A server can only push requests that are safe (see <xref target="HTTP-p2" x:fmt=","
-          x:rel="#safe.methods"/>), cacheable (see <xref target="HTTP-p6" x:fmt=","
-          x:rel="#response.cacheability"/>) and do not include a request body.
+          A server can only push responses that are cacheable (see <xref target="HTTP-p6" x:fmt=","
+          x:rel="#response.cacheability"/>); promised requests MUST be safe (see <xref
+          target="HTTP-p2" x:fmt="," x:rel="#safe.methods"/>) and MUST NOT include a request body.
         </t>
 
         <section title="Push Requests">