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

Timestamp:

19/05/11 08:43:51 (10 years ago)

Author:

julian.reschke@…

Message:

remove confusing comment about fragment ids in Location in 305 responses

File:

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

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

@@ -359 +359 @@
   } 
   @bottom-center {
-       content: "Expires November 2, 2011"; 
+       content: "Expires November 20, 2011"; 
   } 
   @bottom-right {
@@ -409 +409 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2011-05-01">
+      <meta name="dct.issued" scheme="ISO8601" content="2011-05-19">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and response header fields.">
@@ -440 +440 @@
             </tr>
             <tr>
-               <td class="left">Expires: November 2, 2011</td>
+               <td class="left">Expires: November 20, 2011</td>
                <td class="right">HP</td>
             </tr>
@@ -493 +493 @@
             <tr>
                <td class="left"></td>
-               <td class="right">May 1, 2011</td>
+               <td class="right">May 19, 2011</td>
             </tr>
          </tbody>
@@ -522 +522 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on November 2, 2011.</p>
+      <p>This Internet-Draft will expire on November 20, 2011.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -2032 +2032 @@
       <p>Examples are:</p>  <pre class="text">  Location: http://www.example.org/pub/WWW/People.html#tim
 </pre><div id="rfc.figure.u.15"></div><pre class="text">  Location: /index.html
-</pre><p id="rfc.section.9.4.p.7">There are circumstances in which a fragment identifier in a Location URI would not be appropriate: </p>
-      <ul>
-         <li>With a 201 Created response, because in this usage the Location header field specifies the URI for the entire created resource.</li>
-         <li>With 305 Use Proxy.</li>
-      </ul>
+</pre><p id="rfc.section.9.4.p.7">There are circumstances in which a fragment identifier in a Location URI would not be appropriate. For instance, when it appears
+         in a 201 Created response, where the Location header field specifies the URI for the entire created resource.
+      </p>
       <div class="note" id="rfc.section.9.4.p.8"> 
          <p> <b>Note:</b> This specification does not define precedence rules for the case where the original URI, as navigated to by the user agent,