Changeset 954

Timestamp:

Jul 27, 2010, 8:59:10 AM (9 years ago)

Author:

julian.reschke@…

Message:

remove a silly RFC 2219 MAY

Location:

draft-ietf-httpbis/latest

Files:

• p2-semantics.html (modified) (5 diffs)
• p2-semantics.xml (modified) (1 diff)

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

@@ -403 +403 @@
       <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="2010-07-24">
+      <meta name="dct.issued" scheme="ISO8601" content="2010-07-27">
       <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.">
@@ -434 +434 @@
             </tr>
             <tr>
-               <td class="left">Expires: January 25, 2011</td>
+               <td class="left">Expires: January 28, 2011</td>
                <td class="right">HP</td>
             </tr>
@@ -487 +487 @@
             <tr>
                <td class="left"></td>
-               <td class="right">July 24, 2010</td>
+               <td class="right">July 27, 2010</td>
             </tr>
          </tbody>
@@ -514 +514 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire in January 25, 2011.</p>
+      <p>This Internet-Draft will expire in January 28, 2011.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -1318 +1318 @@
       <div id="rfc.iref.s.18"></div>
       <h3 id="rfc.section.8.3.8"><a href="#rfc.section.8.3.8">8.3.8</a>&nbsp;<a id="status.307" href="#status.307">307 Temporary Redirect</a></h3>
-      <p id="rfc.section.8.3.8.p.1">The requested resource resides temporarily under a different URI. Since the redirection <em class="bcp14">MAY</em> be altered on occasion, the client <em class="bcp14">SHOULD</em> continue to use the Effective Request URI for future requests.
+      <p id="rfc.section.8.3.8.p.1">The requested 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.
       </p>
       <p id="rfc.section.8.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

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

@@ -1521 +1521 @@
 <t>
    The requested resource resides temporarily under a different URI.
-   Since the redirection &MAY; be altered on occasion, the client &SHOULD;
+   Since the redirection can change over time, the client &SHOULD;
    continue to use the Effective Request URI for future requests.
 </t>