Ignore:
Timestamp:
Jul 31, 2008, 1:18:42 PM (11 years ago)
Author:
julian.reschke@…
Message:

Resolve #125: s/request/response/ in note about Content-Location vs Location (closes #125).

File:
1 edited

Legend:

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

    r299 r300  
    15251525</pre><p id="rfc.section.10.4.p.5"> </p>
    15261526      <dl class="empty">
    1527          <dd> <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.11"><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 original location of the entity enclosed in the request.
     1527         <dd> <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.11"><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 original location of the entity enclosed in the response.
    15281528            It is therefore possible for a response to contain header fields for both Location and Content-Location.
    15291529         </dd>
     
    22982298         </li>
    22992299         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/119">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/119</a>&gt;: "Description of CONNECT should refer to RFC2817"
     2300         </li>
     2301         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/125">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/125</a>&gt;: "Location Content-Location reference request/response mixup"
    23002302         </li>
    23012303      </ul>
Note: See TracChangeset for help on using the changeset viewer.