Changeset 1723
- Timestamp:
- 05/07/12 09:16:14 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p0-introduction.html
r1719 r1723 527 527 <ul> 528 528 <li>HTTP/1.1 Introduction - this document</li> 529 <li><a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> HTTP/1.1 Message Parsing and Connection Handling- How to parse a HTTP/1.1 (or below) message, and layer it onto connection-oriented530 protocols. 529 <li><a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> HTTP/1.1 Message Parsing, Connection Handling and URIs - How to parse a HTTP/1.1 (or below) message, and layer it onto connection-oriented 530 protocols. Also includes the HTTP and HTTPS URI schemes. 531 531 </li> 532 532 <li><a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a> HTTP/1.1 Core Semantics - Protocol elements such as methods, status codes, and payload-specific headers. Also includes content … … 535 535 <li><a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a> HTTP/1.1 Conditional Requests - An extension to make requests contingent upon their current state. 536 536 </li> 537 <li><a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a> HTTP/1.1 Partial Content- An extension to request that only a portion of a response be sent back.537 <li><a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a> HTTP/1.1 Range Requests - An extension to request that only a portion of a response be sent back. 538 538 </li> 539 539 <li><a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a> HTTP/1.1 Caching - An extension to allow storage and reuse of responses. … … 543 543 </ul> 544 544 <p id="rfc.section.1.p.4">The "core" of HTTP/1.1 is defined by the first two specifications. The remaining specifications in the series are generally 545 optional, but may be required in some implementation or deployment scenarios; when this is the case, it will be noted. 545 not mandatory for implementations, but might be required in some implementation or deployment scenarios; when this is the 546 case, it will be noted. 546 547 </p> 547 548 <p id="rfc.section.1.p.5">Collectively, these documents obsolete <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>. Note that many other specifications extend and refine the use of HTTP (generally, as protocol extensions, where allowed
Note: See TracChangeset
for help on using the changeset viewer.