Changeset 333 for draft-ietf-httpbis/latest/p2-semantics.html

Timestamp:

05/11/08 10:13:33 (14 years ago)

Author:

julian.reschke@…

Message:

Resolve #103: explain shorthand notation "Content-*" (closes #103).

File:

• draft-ietf-httpbis/latest/p2-semantics.html (modified) (3 diffs)

draft-ietf-httpbis/latest/p2-semantics.html

@@ -477 +477 @@
          <tr>
             <td class="header left"></td>
-            <td class="header right">November 1, 2008</td>
+            <td class="header right">November 5, 2008</td>
          </tr>
       </table>
@@ -992 +992 @@
          the resource with that URI. If a new resource is created at the Request-URI, the origin server <em class="bcp14">MUST</em> inform the user agent via the 201 (Created) response. If an existing resource is modified, either the 200 (OK) or 204 (No
          Content) response codes <em class="bcp14">SHOULD</em> be sent to indicate successful completion of the request. If the resource could not be created or modified with the Request-URI,
-         an appropriate error response <em class="bcp14">SHOULD</em> be given that reflects the nature of the problem. The recipient of the entity <em class="bcp14">MUST NOT</em> ignore any Content-* (e.g. Content-Range) headers that it does not understand or implement and <em class="bcp14">MUST</em> return a 501 (Not Implemented) response in such cases.
+         an appropriate error response <em class="bcp14">SHOULD</em> be given that reflects the nature of the problem. The recipient of the entity <em class="bcp14">MUST NOT</em> ignore any Content-* headers (headers starting with the prefix 'Content-') that it does not understand or implement and <em class="bcp14">MUST</em> return a 501 (Not Implemented) response in such cases.
       </p>
       <p id="rfc.section.8.6.p.2">If the request passes through a cache and the Request-URI identifies one or more currently cached entities, those entries <em class="bcp14">SHOULD</em> be treated as stale. Responses to this method are not cacheable.
@@ -2311 +2311 @@
       <p id="rfc.section.B.6.p.1">Closed issues: </p>
       <ul>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/103">http://tools.ietf.org/wg/httpbis/trac/ticket/103</a>&gt;: "Content-*"
+         </li>
          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/132">http://tools.ietf.org/wg/httpbis/trac/ticket/132</a>&gt;: "RFC 2822 is updated by RFC 5322"
          </li>