Changeset 333


Ignore:
Timestamp:
Nov 5, 2008, 2:13:33 AM (11 years ago)
Author:
julian.reschke@…
Message:

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

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.html

    r331 r333  
    477477         <tr>
    478478            <td class="header left"></td>
    479             <td class="header right">November 1, 2008</td>
     479            <td class="header right">November 5, 2008</td>
    480480         </tr>
    481481      </table>
     
    992992         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
    993993         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,
    994          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.
     994         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.
    995995      </p>
    996996      <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.
     
    23112311      <p id="rfc.section.B.6.p.1">Closed issues: </p>
    23122312      <ul>
     2313         <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-*"
     2314         </li>
    23132315         <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"
    23142316         </li>
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r331 r333  
    891891   error response &SHOULD; be given that reflects the nature of the
    892892   problem. The recipient of the entity &MUST-NOT; ignore any Content-*
    893    (e.g. Content-Range) headers that it does not understand or implement
     893   headers (headers starting with the prefix 'Content-') that it does
     894   not understand or implement
    894895   and &MUST; return a 501 (Not Implemented) response in such cases.
    895896</t>
     
    33083309  <list style="symbols">
    33093310    <t>
     3311      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/103"/>:
     3312      "Content-*"
     3313    </t>
     3314    <t>
    33103315      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/132"/>:
    33113316      "RFC 2822 is updated by RFC 5322"
Note: See TracChangeset for help on using the changeset viewer.