Ignore:
Timestamp:
Mar 21, 2012, 5:30:28 AM (8 years ago)
Author:
julian.reschke@…
Message:

replace a few instances of lowercase "must"

File:
1 edited

Legend:

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

    r1590 r1604  
    460460  }
    461461  @bottom-center {
    462        content: "Expires September 13, 2012";
     462       content: "Expires September 22, 2012";
    463463  }
    464464  @bottom-right {
     
    507507      <meta name="dct.creator" content="Reschke, J. F.">
    508508      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    509       <meta name="dct.issued" scheme="ISO8601" content="2012-03-12">
     509      <meta name="dct.issued" scheme="ISO8601" content="2012-03-21">
    510510      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    511511      <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.">
     
    538538            </tr>
    539539            <tr>
    540                <td class="left">Expires: September 13, 2012</td>
     540               <td class="left">Expires: September 22, 2012</td>
    541541               <td class="right">greenbytes</td>
    542542            </tr>
    543543            <tr>
    544544               <td class="left"></td>
    545                <td class="right">March 12, 2012</td>
     545               <td class="right">March 21, 2012</td>
    546546            </tr>
    547547         </tbody>
     
    573573         in progress”.
    574574      </p>
    575       <p>This Internet-Draft will expire on September 13, 2012.</p>
     575      <p>This Internet-Draft will expire on September 22, 2012.</p>
    576576      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    577577      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    16611661         <li>1xx: Informational - Request received, continuing process</li>
    16621662         <li>2xx: Success - The action was successfully received, understood, and accepted</li>
    1663          <li>3xx: Redirection - Further action must be taken in order to complete the request</li>
     1663         <li>3xx: Redirection - Further action needs to be taken in order to complete the request</li>
    16641664         <li>4xx: Client Error - The request contains bad syntax or cannot be fulfilled</li>
    16651665         <li>5xx: Server Error - The server failed to fulfill an apparently valid request</li>
     
    20812081      </p>
    20822082      <div class="note" id="rfc.section.7.5.4.p.3">
    2083          <p> <b>Note:</b> The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers might
     2083         <p> <b>Note:</b> The existence of the 503 status code does not imply that a server has to use it when becoming overloaded. Some servers might
    20842084            wish to simply refuse the connection.
    20852085         </p>
     
    30053005      </p>
    30063006      <p id="rfc.section.A.p.8">Deprecate 305 Use Proxy status code, because user agents did not implement it. It used to indicate that the target resource
    3007          must be accessed through the proxy given by the Location field. The Location field gave the URI of the proxy. The recipient
     3007         needs to be accessed through the proxy given by the Location field. The Location field gave the URI of the proxy. The recipient
    30083008         was expected to repeat this single request via the proxy. (<a href="#status.305" id="rfc.xref.status.305.3" title="305 Use Proxy">Section&nbsp;7.3.5</a>)
    30093009      </p>
Note: See TracChangeset for help on using the changeset viewer.