Ignore:
Timestamp:
26/01/12 16:43:02 (9 years ago)
Author:
julian.reschke@…
Message:

State that the Content-Type describes the payload only one (related to #332)

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

Legend:

Unmodified
Added
Removed

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

    r1514 r1515  
    16291629      </ul>
    16301630      <p id="rfc.section.7.p.2">Each Status-Code is described below, including any metadata required in the response.</p>
     1631      <p id="rfc.section.7.p.3">For most status codes the response can carry a payload, in which case a Content-Type header field indicates the payload's
     1632         media type (<a href="p3-payload.html#header.content-type" title="Content-Type">Section 6.8</a> of <a href="#Part3" id="rfc.xref.Part3.9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).
     1633      </p>
    16311634      <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a id="status.1xx" href="#status.1xx">Informational 1xx</a></h2>
    16321635      <p id="rfc.section.7.1.p.1">This class of status code indicates a provisional response, consisting only of the Status-Line and optional header fields,
    … …  
    16821685         by the URI(s) returned in the payload of the response, with the most specific URI for the resource given by a Location header
    16831686         field. The response <em class="bcp14">SHOULD</em> include a payload containing a list of resource characteristics and location(s) from which the user or user agent can choose
    1684          the one most appropriate. The payload format is specified by the media type given in the Content-Type header field.
     1687         the one most appropriate.
    16851688      </p>
    16861689      <p id="rfc.section.7.2.2.p.2">The origin server <em class="bcp14">MUST</em> create the resource before returning the 201 status code. If the action cannot be carried out immediately, the server <em class="bcp14">SHOULD</em> respond with 202 (Accepted) response instead.
    … …  
    17681771         </li>
    17691772         <li>
    1770             <p>Redirection offering a choice of matching resources for use by agent-driven content negotiation (<a href="p3-payload.html#agent-driven.negotiation" title="Agent-driven Negotiation">Section 5.2</a> of <a href="#Part3" id="rfc.xref.Part3.9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>). This is status code 300 (Multiple Choices).
     1773            <p>Redirection offering a choice of matching resources for use by agent-driven content negotiation (<a href="p3-payload.html#agent-driven.negotiation" title="Agent-driven Negotiation">Section 5.2</a> of <a href="#Part3" id="rfc.xref.Part3.10"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>). This is status code 300 (Multiple Choices).
    17711774            </p>
    17721775         </li>
    … …  
    17961799      <h3 id="rfc.section.7.3.1"><a href="#rfc.section.7.3.1">7.3.1</a>&nbsp;<a id="status.300" href="#status.300">300 Multiple Choices</a></h3>
    17971800      <p id="rfc.section.7.3.1.p.1">The target resource has more than one representation, each with its own specific location, and agent-driven negotiation information
    1798          (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</a> of <a href="#Part3" id="rfc.xref.Part3.10"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) is being provided so that the user (or user agent) can select a preferred representation by redirecting its request to that
     1801         (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</a> of <a href="#Part3" id="rfc.xref.Part3.11"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) is being provided so that the user (or user agent) can select a preferred representation by redirecting its request to that
    17991802         location.
    18001803      </p>
    18011804      <p id="rfc.section.7.3.1.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include a representation containing a list of representation metadata and location(s) from which the user or user agent can
    1802          choose the one most appropriate. The data format is specified by the media type given in the Content-Type header field. Depending
    1803          upon the format and the capabilities of the user agent, selection of the most appropriate choice <em class="bcp14">MAY</em> be performed automatically. However, this specification does not define any standard for such automatic selection.
     1805         choose the one most appropriate. Depending upon the format and the capabilities of the user agent, selection of the most appropriate
     1806         choice <em class="bcp14">MAY</em> be performed automatically. However, this specification does not define any standard for such automatic selection.
    18041807      </p>
    18051808      <p id="rfc.section.7.3.1.p.3">If the server has a preferred choice of representation, it <em class="bcp14">SHOULD</em> include the specific URI for that representation in the Location field; user agents <em class="bcp14">MAY</em> use the Location field value for automatic redirection.
    … …  
    19401943      <h3 id="rfc.section.7.4.7"><a href="#rfc.section.7.4.7">7.4.7</a>&nbsp;<a id="status.406" href="#status.406">406 Not Acceptable</a></h3>
    19411944      <p id="rfc.section.7.4.7.p.1">The resource identified by the request is only capable of generating response representations which have content characteristics
    1942          not acceptable according to the Accept and Accept-* header fields sent in the request (see <a href="p3-payload.html#header.field.definitions" title="Header Field Definitions">Section 6</a> of <a href="#Part3" id="rfc.xref.Part3.11"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).
     1945         not acceptable according to the Accept and Accept-* header fields sent in the request (see <a href="p3-payload.html#header.field.definitions" title="Header Field Definitions">Section 6</a> of <a href="#Part3" id="rfc.xref.Part3.12"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).
    19431946      </p>
    19441947      <p id="rfc.section.7.4.7.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include a representation containing a list of available representation characteristics and location(s) from which the user
    1945          or user agent can choose the one most appropriate. The data format is specified by the media type given in the Content-Type
    1946          header field. Depending upon the format and the capabilities of the user agent, selection of the most appropriate choice <em class="bcp14">MAY</em> be performed automatically. However, this specification does not define any standard for such automatic selection.
     1948         or user agent can choose the one most appropriate. Depending upon the format and the capabilities of the user agent, selection
     1949         of the most appropriate choice <em class="bcp14">MAY</em> be performed automatically. However, this specification does not define any standard for such automatic selection.
    19471950      </p>
    19481951      <div class="note" id="rfc.section.7.4.7.p.3">
    … …  
    19751978         being PUT included changes to a resource which conflict with those made by an earlier (third-party) request, the server might
    19761979         use the 409 response to indicate that it can't complete the request. In this case, the response representation would likely
    1977          contain a list of the differences between the two versions in a format defined by the response Content-Type.
     1980         contain a list of the differences between the two versions.
    19781981      </p>
    19791982      <div id="rfc.iref.49"></div>
    … …  
    23132316      </div>
    23142317      <div class="note" id="rfc.section.9.5.p.10">
    2315          <p> <b>Note:</b> The Content-Location header field (<a href="p3-payload.html#header.content-location" title="Content-Location">Section 6.7</a> of <a href="#Part3" id="rfc.xref.Part3.12"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) differs from Location in that the Content-Location identifies the most specific resource corresponding to the enclosed representation.
     2318         <p> <b>Note:</b> The Content-Location header field (<a href="p3-payload.html#header.content-location" title="Content-Location">Section 6.7</a> of <a href="#Part3" id="rfc.xref.Part3.13"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) differs from Location in that the Content-Location identifies the most specific resource corresponding to the enclosed representation.
    23162319            It is therefore possible for a response to contain header fields for both Location and Content-Location.
    23172320         </p>
    … …  
    36443647                     </ul>
    36453648                  </li>
    3646                   <li><em>Part3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.1">3.1</a>, <a href="#rfc.xref.Part3.2">3.1</a>, <a href="#rfc.xref.Part3.3">3.2</a>, <a href="#rfc.xref.Part3.4">3.2</a>, <a href="#rfc.xref.Part3.5">3.2</a>, <a href="#rfc.xref.Part3.6">3.2</a>, <a href="#rfc.xref.Part3.7">5</a>, <a href="#rfc.xref.Part3.8">6.5</a>, <a href="#rfc.xref.Part3.9">7.3</a>, <a href="#rfc.xref.Part3.10">7.3.1</a>, <a href="#rfc.xref.Part3.11">7.4.7</a>, <a href="#rfc.xref.Part3.12">9.5</a>, <a href="#Part3"><b>13.1</b></a><ul>
     3649                  <li><em>Part3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.1">3.1</a>, <a href="#rfc.xref.Part3.2">3.1</a>, <a href="#rfc.xref.Part3.3">3.2</a>, <a href="#rfc.xref.Part3.4">3.2</a>, <a href="#rfc.xref.Part3.5">3.2</a>, <a href="#rfc.xref.Part3.6">3.2</a>, <a href="#rfc.xref.Part3.7">5</a>, <a href="#rfc.xref.Part3.8">6.5</a>, <a href="#rfc.xref.Part3.9">7</a>, <a href="#rfc.xref.Part3.10">7.3</a>, <a href="#rfc.xref.Part3.11">7.3.1</a>, <a href="#rfc.xref.Part3.12">7.4.7</a>, <a href="#rfc.xref.Part3.13">9.5</a>, <a href="#Part3"><b>13.1</b></a><ul>
    36473650                        <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.2">3.1</a></li>
    3648                         <li><em>Section 5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.10">7.3.1</a></li>
    3649                         <li><em>Section 5.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.9">7.3</a></li>
     3651                        <li><em>Section 5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.11">7.3.1</a></li>
     3652                        <li><em>Section 5.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.10">7.3</a></li>
    36503653                        <li><em>Section 6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.3">3.2</a></li>
    3651                         <li><em>Section 6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.11">7.4.7</a></li>
     3654                        <li><em>Section 6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.12">7.4.7</a></li>
    36523655                        <li><em>Section 6.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.4">3.2</a></li>
    36533656                        <li><em>Section 6.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.5">3.2</a></li>
    36543657                        <li><em>Section 6.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.6">3.2</a></li>
    3655                         <li><em>Section 6.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.8">6.5</a>, <a href="#rfc.xref.Part3.12">9.5</a></li>
    3656                         <li><em>Section 6.8</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.1">3.1</a></li>
     3658                        <li><em>Section 6.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.8">6.5</a>, <a href="#rfc.xref.Part3.13">9.5</a></li>
     3659                        <li><em>Section 6.8</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.1">3.1</a>, <a href="#rfc.xref.Part3.9">7</a></li>
    36573660                     </ul>
    36583661                  </li>

  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1514 r1515  
    14061406   in the response.
    14071407</t>
     1408<t>
     1409   For most status codes the response can carry a payload, in which case a
     1410   Content-Type header field indicates the payload's media type
     1411   (&header-content-type;).
     1412</t>
    14081413
    14091414<section title="Informational 1xx" anchor="status.1xx">
    … …  
    15111516   &SHOULD; include a payload containing a list of resource
    15121517   characteristics and location(s) from which the user or user agent can
    1513    choose the one most appropriate. The payload format is specified by
    1514    the media type given in the Content-Type header field.
     1518   choose the one most appropriate.
    15151519</t>
    15161520<t>
    … …  
    17311735   Unless it was a HEAD request, the response &SHOULD; include a representation
    17321736   containing a list of representation metadata and location(s) from
    1733    which the user or user agent can choose the one most appropriate. The
    1734    data format is specified by the media type given in the Content-Type
    1735    header field. Depending upon the format and the capabilities of
     1737   which the user or user agent can choose the one most appropriate. Depending
     1738   upon the format and the capabilities of
    17361739   the user agent, selection of the most appropriate choice &MAY; be
    17371740   performed automatically. However, this specification does not define
    … …  
    20272030   containing a list of available representation characteristics and location(s)
    20282031   from which the user or user agent can choose the one most
    2029    appropriate. The data format is specified by the media type given
    2030    in the Content-Type header field. Depending upon the format and the
     2032   appropriate. Depending upon the format and the
    20312033   capabilities of the user agent, selection of the most appropriate
    20322034   choice &MAY; be performed automatically. However, this specification
    … …  
    20882090   to indicate that it can't complete the request. In this case, the
    20892091   response representation would likely contain a list of the differences
    2090    between the two versions in a format defined by the response
    2091    Content-Type.
     2092   between the two versions.
    20922093</t>
    20932094</section>
Note: See TracChangeset for help on using the changeset viewer.