Changeset 753


Ignore:
Timestamp:
Jan 31, 2010, 10:52:41 AM (10 years ago)
Author:
julian.reschke@…
Message:

Consistency: upper-case names of Status Code classes

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

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r748 r753  
    404404      <meta name="DC.Creator" content="Reschke, J. F.">
    405405      <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    406       <meta name="DC.Date.Issued" scheme="ISO8601" content="2010-01-21">
     406      <meta name="DC.Date.Issued" scheme="ISO8601" content="2010-01-31">
    407407      <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616">
    408408      <meta name="DC.Description.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 1 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 1 provides an overview of HTTP and its associated terminology, defines the &#34;http&#34; and &#34;https&#34; Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations.">
     
    435435            </tr>
    436436            <tr>
    437                <td class="left">Expires: July 25, 2010</td>
     437               <td class="left">Expires: August 4, 2010</td>
    438438               <td class="right">HP</td>
    439439            </tr>
     
    488488            <tr>
    489489               <td class="left"></td>
    490                <td class="right">January 21, 2010</td>
     490               <td class="right">January 31, 2010</td>
    491491            </tr>
    492492         </tbody>
     
    520520      <p>The list of Internet-Draft Shadow Directories can be accessed at &lt;<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>&gt;.
    521521      </p>
    522       <p>This Internet-Draft will expire in July 25, 2010.</p>
     522      <p>This Internet-Draft will expire in August 4, 2010.</p>
    523523      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    524524      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    12121212      </p>
    12131213      <p id="rfc.section.3.3.p.6">For response messages, whether or not a message-body is included with a message is dependent on both the request method and
    1214          the response status code (<a href="#status.code.and.reason.phrase" title="Status Code and Reason Phrase">Section&nbsp;5.1.1</a>). All responses to the HEAD request method <em class="bcp14">MUST NOT</em> include a message-body, even though the presence of entity-header fields might lead one to believe they do. All 1xx (informational),
     1214         the response status code (<a href="#status.code.and.reason.phrase" title="Status Code and Reason Phrase">Section&nbsp;5.1.1</a>). All responses to the HEAD request method <em class="bcp14">MUST NOT</em> include a message-body, even though the presence of entity-header fields might lead one to believe they do. All 1xx (Informational),
    12151215         204 (No Content), and 304 (Not Modified) responses <em class="bcp14">MUST NOT</em> include a message-body. All other responses do include a message-body, although it <em class="bcp14">MAY</em> be of zero length.
    12161216      </p>
     
    18821882      <p id="rfc.section.9.1.p.9">An HTTP/1.1 client that does not support persistent connections <em class="bcp14">MUST</em> include the "close" connection option in every request message.
    18831883      </p>
    1884       <p id="rfc.section.9.1.p.10">An HTTP/1.1 server that does not support persistent connections <em class="bcp14">MUST</em> include the "close" connection option in every response message that does not have a 1xx (informational) status code.
     1884      <p id="rfc.section.9.1.p.10">An HTTP/1.1 server that does not support persistent connections <em class="bcp14">MUST</em> include the "close" connection option in every response message that does not have a 1xx (Informational) status code.
    18851885      </p>
    18861886      <p id="rfc.section.9.1.p.11">A system receiving an HTTP/1.0 (or lower-version) message that includes a Connection header <em class="bcp14">MUST</em>, for each connection-token in this field, remove and ignore any header field(s) from the message with the same name as the
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r748 r753  
    12681268   &MUST-NOT; include a message-body, even though the presence of entity-header
    12691269   fields might lead one to believe they do. All 1xx
    1270    (informational), 204 (No Content), and 304 (Not Modified) responses
     1270   (Informational), 204 (No Content), and 304 (Not Modified) responses
    12711271   &MUST-NOT; include a message-body. All other responses do include a
    12721272   message-body, although it &MAY; be of zero length.
     
    26162616   An HTTP/1.1 server that does not support persistent connections &MUST;
    26172617   include the "close" connection option in every response message that
    2618    does not have a 1xx (informational) status code.
     2618   does not have a 1xx (Informational) status code.
    26192619</t>
    26202620<t>
Note: See TracChangeset for help on using the changeset viewer.