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

Changeset 1508


Ignore:
Timestamp:
2012-01-24 10:13:15 (3 years ago)
Author:
julian.reschke@gmx.de
Message:

Align description of 307 with 302 (307 isn't "new" anymore) (related to #332)

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

Legend:

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

    r1505 r1508  
    358358  }  
    359359  @bottom-center { 
    360        content: "Expires July 7, 2012";  
     360       content: "Expires July 27, 2012";  
    361361  }  
    362362  @bottom-right { 
     
    410410      <meta name="dct.creator" content="Reschke, J. F."> 
    411411      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 
    412       <meta name="dct.issued" scheme="ISO8601" content="2012-01-04"> 
     412      <meta name="dct.issued" scheme="ISO8601" content="2012-01-24"> 
    413413      <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 
    414414      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext 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."> 
     
    441441            </tr> 
    442442            <tr> 
    443                <td class="left">Expires: July 7, 2012</td> 
     443               <td class="left">Expires: July 27, 2012</td> 
    444444               <td class="right">HP</td> 
    445445            </tr> 
     
    494494            <tr> 
    495495               <td class="left"></td> 
    496                <td class="right">January 4, 2012</td> 
     496               <td class="right">January 24, 2012</td> 
    497497            </tr> 
    498498         </tbody> 
     
    524524         in progress”. 
    525525      </p> 
    526       <p>This Internet-Draft will expire on July 7, 2012.</p> 
     526      <p>This Internet-Draft will expire on July 27, 2012.</p> 
    527527      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 
    528528      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 
     
    18801880      <p id="rfc.section.7.3.8.p.1">The target resource resides temporarily under a different URI. Since the redirection can change over time, the client <em class="bcp14">SHOULD</em> continue to use the effective request URI for future requests. 
    18811881      </p> 
    1882       <p id="rfc.section.7.3.8.p.2">The temporary URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. Unless the request method was HEAD, the representation of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s), since many pre-HTTP/1.1 user agents do not understand the 
    1883          307 status code. Therefore, the note <em class="bcp14">SHOULD</em> contain the information necessary for a user to repeat the original request on the new URI. 
     1882      <p id="rfc.section.7.3.8.p.2">The temporary URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. Unless the request method was HEAD, the representation of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s). 
    18841883      </p> 
    18851884      <p id="rfc.section.7.3.8.p.3">If the 307 status code is received in response to a request method that is known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;6.1.1</a>, then the request <em class="bcp14">MAY</em> be automatically redirected by the user agent without confirmation. Otherwise, the user agent <em class="bcp14">MUST NOT</em> automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which 
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1505 r1508  
    19031903   response. Unless the request method was HEAD, the representation of the 
    19041904   response &SHOULD; contain a short hypertext note with a hyperlink to 
    1905    the new URI(s), since many pre-HTTP/1.1 user agents do not 
    1906    understand the 307 status code. Therefore, the note &SHOULD; contain the 
    1907    information necessary for a user to repeat the original request on 
    1908    the new URI. 
     1905   the new URI(s). 
    19091906</t> 
    19101907<t> 
Note: See TracChangeset for help on using the changeset viewer.