Changeset 1635 for draft-ietf-httpbis/latest/p1-messaging.html
- Timestamp:
- 29/03/12 11:28:19 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1632 r1635 460 460 } 461 461 @bottom-center { 462 content: "Expires September 29, 2012";462 content: "Expires September 30, 2012"; 463 463 } 464 464 @bottom-right { … … 502 502 <meta name="dct.creator" content="Reschke, J. F."> 503 503 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 504 <meta name="dct.issued" scheme="ISO8601" content="2012-03-2 8">504 <meta name="dct.issued" scheme="ISO8601" content="2012-03-29"> 505 505 <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 506 506 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> … … 534 534 </tr> 535 535 <tr> 536 <td class="left">Expires: September 29, 2012</td>536 <td class="left">Expires: September 30, 2012</td> 537 537 <td class="right">greenbytes</td> 538 538 </tr> 539 539 <tr> 540 540 <td class="left"></td> 541 <td class="right">March 2 8, 2012</td>541 <td class="right">March 29, 2012</td> 542 542 </tr> 543 543 </tbody> … … 572 572 in progress”. 573 573 </p> 574 <p>This Internet-Draft will expire on September 29, 2012.</p>574 <p>This Internet-Draft will expire on September 30, 2012.</p> 575 575 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 576 576 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1078 1078 </p> 1079 1079 <p id="rfc.section.2.7.1.p.6">When an "http" URI is used within a context that calls for access to the indicated resource, a client <em class="bcp14">MAY</em> attempt access by resolving the host to an IP address, establishing a TCP connection to that address on the indicated port, 1080 and sending an HTTP request message (<a href="#http.message" title="Message Format">Section 3</a>) containing the URI's identifying data (<a href="#message.routing" title="Message Routing">Section 5</a>) to the server. If the server responds to that request with a non-interim HTTP response message, as described in <a href="p2-semantics.html#status.code .and.reason.phrase" title="Status Code and Reason Phrase">Section 4</a> of <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, then that response is considered an authoritative answer to the client's request.1080 and sending an HTTP request message (<a href="#http.message" title="Message Format">Section 3</a>) containing the URI's identifying data (<a href="#message.routing" title="Message Routing">Section 5</a>) to the server. If the server responds to that request with a non-interim HTTP response message, as described in <a href="p2-semantics.html#status.codes" title="Status Codes">Section 4</a> of <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, then that response is considered an authoritative answer to the client's request. 1081 1081 </p> 1082 1082 <p id="rfc.section.2.7.1.p.7">Although HTTP is independent of the transport protocol, the "http" scheme is specific to TCP-based services because the name … … 1199 1199 <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.29"></span> <a href="#status.line" class="smpl">status-line</a> = <a href="#http.version" class="smpl">HTTP-version</a> <a href="#core.rules" class="smpl">SP</a> <a href="#status-code" class="smpl">status-code</a> <a href="#core.rules" class="smpl">SP</a> <a href="#reason-phrase" class="smpl">reason-phrase</a> <a href="#core.rules" class="smpl">CRLF</a> 1200 1200 </pre><div id="status-code"> 1201 <p id="rfc.section.3.1.2.p.3">The status-code element is a 3-digit integer result code of the attempt to understand and satisfy the request. See <a href="p2-semantics.html#status.code .and.reason.phrase" title="Status Code and Reason Phrase">Section 4</a> of <a href="#Part2" id="rfc.xref.Part2.5"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a> for further information, such as the list of status codes defined by this specification, the IANA registry, and considerations1201 <p id="rfc.section.3.1.2.p.3">The status-code element is a 3-digit integer result code of the attempt to understand and satisfy the request. See <a href="p2-semantics.html#status.codes" title="Status Codes">Section 4</a> of <a href="#Part2" id="rfc.xref.Part2.5"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a> for further information, such as the list of status codes defined by this specification, the IANA registry, and considerations 1202 1202 for new status codes. 1203 1203 </p>
Note: See TracChangeset
for help on using the changeset viewer.