* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Changeset 1283


Ignore:
Timestamp:
2011-05-19 01:43:51 (4 years ago)
Author:
julian.reschke@gmx.de
Message:

remove confusing comment about fragment ids in Location in 305 responses

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

Legend:

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

    r1276 r1283  
    359359  }  
    360360  @bottom-center { 
    361        content: "Expires November 2, 2011";  
     361       content: "Expires November 20, 2011";  
    362362  }  
    363363  @bottom-right { 
     
    409409      <meta name="dct.creator" content="Reschke, J. F."> 
    410410      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 
    411       <meta name="dct.issued" scheme="ISO8601" content="2011-05-01"> 
     411      <meta name="dct.issued" scheme="ISO8601" content="2011-05-19"> 
    412412      <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 
    413413      <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."> 
     
    440440            </tr> 
    441441            <tr> 
    442                <td class="left">Expires: November 2, 2011</td> 
     442               <td class="left">Expires: November 20, 2011</td> 
    443443               <td class="right">HP</td> 
    444444            </tr> 
     
    493493            <tr> 
    494494               <td class="left"></td> 
    495                <td class="right">May 1, 2011</td> 
     495               <td class="right">May 19, 2011</td> 
    496496            </tr> 
    497497         </tbody> 
     
    522522         in progress”. 
    523523      </p> 
    524       <p>This Internet-Draft will expire on November 2, 2011.</p> 
     524      <p>This Internet-Draft will expire on November 20, 2011.</p> 
    525525      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 
    526526      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 
     
    20322032      <p>Examples are:</p>  <pre class="text">  Location: http://www.example.org/pub/WWW/People.html#tim 
    20332033</pre><div id="rfc.figure.u.15"></div><pre class="text">  Location: /index.html 
    2034 </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> 
    2035       <ul> 
    2036          <li>With a 201 Created response, because in this usage the Location header field specifies the URI for the entire created resource.</li> 
    2037          <li>With 305 Use Proxy.</li> 
    2038       </ul> 
     2034</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 
     2035         in a 201 Created response, where the Location header field specifies the URI for the entire created resource. 
     2036      </p> 
    20392037      <div class="note" id="rfc.section.9.4.p.8">  
    20402038         <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, 
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1276 r1283  
    22902290<t> 
    22912291   There are circumstances in which a fragment identifier in a Location URI 
    2292    would not be appropriate: 
    2293    <list style="symbols"> 
    2294       <t>With a 201 Created response, because in this usage the Location header 
    2295       field specifies the URI for the entire created resource.</t> 
    2296       <t>With 305 Use Proxy.</t> 
    2297    </list> 
     2292   would not be appropriate. For instance, when it appears in a 201 Created 
     2293   response, where the Location header field specifies the URI for the entire 
     2294   created resource. 
    22982295</t> 
    22992296<x:note> 
Note: See TracChangeset for help on using the changeset viewer.