Changeset 300 for draft-ietf-httpbis

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).

Location:

draft-ietf-httpbis/latest

Files:

• p2-semantics.html (modified) (2 diffs)
• p2-semantics.xml (modified) (2 diffs)

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

@@ -1525 +1525 @@
 </pre><p id="rfc.section.10.4.p.5"> </p>
       <dl class="empty">
-         <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.
+         <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.
             It is therefore possible for a response to contain header fields for both Location and Content-Location.
          </dd>
@@ -2298 +2298 @@
          </li>
          <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"
+         </li>
+         <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"
          </li>
       </ul>

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

@@ -1947 +1947 @@
       <x:h>Note:</x:h> The Content-Location header field (&header-content-location;) differs
       from Location in that the Content-Location identifies the original
-      location of the entity enclosed in the request. It is therefore
+      location of the entity enclosed in the response. It is therefore
       possible for a response to contain header fields for both Location
       and Content-Location.
@@ -3286 +3286 @@
       "Description of CONNECT should refer to RFC2817"
     </t>
+    <t>
+      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/125"/>:
+      "Location Content-Location reference request/response mixup"
+    </t>
   </list>
 </t>