Changeset 2003
- Timestamp:
- 28/11/12 07:31:16 (9 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r2001 r2003 514 514 </tr> 515 515 <tr> 516 <td class="left">Updates: <a href="http://tools.ietf.org/html/rfc2817">2817</a> (if approved)516 <td class="left">Updates: <a href="http://tools.ietf.org/html/rfc2817">2817</a>, <a href="http://tools.ietf.org/html/rfc2818">2818</a> (if approved) 517 517 </td> 518 518 <td class="right">greenbytes</td> … … 723 723 </li> 724 724 </ul> 725 <p id="rfc.section.1.p.2">This HTTP/1.1 specification obsoletes and moves to historic status <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.1">RFC 2616</cite>, its predecessor <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.1">RFC 2068</cite>, <cite title="Use and Interpretation of HTTP Version Numbers" id="rfc.xref.RFC2145.1">RFC 2145</cite> (on HTTP versioning), and <cite title="Upgrading to TLS Within HTTP/1.1" id="rfc.xref.RFC2817.1">RFC 2817</cite> (on using CONNECT for TLS upgrades).725 <p id="rfc.section.1.p.2">This HTTP/1.1 specification obsoletes and moves to historic status <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.1">RFC 2616</cite>, its predecessor <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.1">RFC 2068</cite>, and <cite title="Use and Interpretation of HTTP Version Numbers" id="rfc.xref.RFC2145.1">RFC 2145</cite> (on HTTP versioning). This specification also updates the use of CONNECT to establish a tunnel, previously defined in <cite title="Upgrading to TLS Within HTTP/1.1" id="rfc.xref.RFC2817.1">RFC 2817</cite>, and defines the "https" URI scheme that was described informally in <cite title="HTTP Over TLS" id="rfc.xref.RFC2818.1">RFC 2818</cite>. 726 726 </p> 727 727 <p id="rfc.section.1.p.3">HTTP is a generic interface protocol for information systems. It is designed to hide the details of how a service is implemented … … 1084 1084 Cookie protocol <a href="#RFC6265" id="rfc.xref.RFC6265.1"><cite title="HTTP State Management Mechanism">[RFC6265]</cite></a>, can allow information set by one service to impact communication with other services within a matching group of host domains. 1085 1085 </p> 1086 <p id="rfc.section.2.7.2.p.6">The process for authoritative access to an "https" identified resource is defined in <a href="#RFC2818" id="rfc.xref.RFC2818. 1"><cite title="HTTP Over TLS">[RFC2818]</cite></a>.1086 <p id="rfc.section.2.7.2.p.6">The process for authoritative access to an "https" identified resource is defined in <a href="#RFC2818" id="rfc.xref.RFC2818.2"><cite title="HTTP Over TLS">[RFC2818]</cite></a>. 1087 1087 </p> 1088 1088 <h3 id="rfc.section.2.7.3"><a href="#rfc.section.2.7.3">2.7.3</a> <a id="uri.comparison" href="#uri.comparison">http and https URI Normalization and Comparison</a></h3> … … 3283 3283 </ul> 3284 3284 </li> 3285 <li><em>RFC2818</em> <a href="#rfc.xref.RFC2818.1"> 2.7.2</a>, <a href="#RFC2818"><b>10.2</b></a></li>3285 <li><em>RFC2818</em> <a href="#rfc.xref.RFC2818.1">1</a>, <a href="#rfc.xref.RFC2818.2">2.7.2</a>, <a href="#RFC2818"><b>10.2</b></a></li> 3286 3286 <li><em>RFC3040</em> <a href="#rfc.xref.RFC3040.1">2.3</a>, <a href="#RFC3040"><b>10.2</b></a></li> 3287 3287 <li><em>RFC3864</em> <a href="#rfc.xref.RFC3864.1">7.1</a>, <a href="#RFC3864"><b>10.2</b></a></li> -
draft-ietf-httpbis/latest/p1-messaging.xml
r1997 r2003 69 69 <?rfc-ext allow-markup-in-artwork="yes" ?> 70 70 <?rfc-ext include-references-in-index="yes" ?> 71 <rfc obsoletes="2145,2616" updates="2817 " category="std" x:maturity-level="proposed"71 <rfc obsoletes="2145,2616" updates="2817,2818" category="std" x:maturity-level="proposed" 72 72 ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p1-messaging-&ID-VERSION;" 73 73 xmlns:x='http://purl.org/net/xml2rfc/ext'> … … 158 158 This HTTP/1.1 specification obsoletes and moves to historic status 159 159 <xref target="RFC2616" x:fmt="none">RFC 2616</xref>, its predecessor 160 <xref target="RFC2068" x:fmt="none">RFC 2068</xref>, 161 <xref target="RFC2145" x:fmt="none">RFC 2145</xref> (on HTTP versioning), 162 and <xref target="RFC2817" x:fmt="none">RFC 2817</xref> (on using CONNECT 163 for TLS upgrades). 160 <xref target="RFC2068" x:fmt="none">RFC 2068</xref>, and 161 <xref target="RFC2145" x:fmt="none">RFC 2145</xref> (on HTTP versioning). 162 This specification also updates the use of CONNECT to establish a tunnel, 163 previously defined in <xref target="RFC2817" x:fmt="none">RFC 2817</xref>, 164 and defines the "https" URI scheme that was described informally in 165 <xref target="RFC2818" x:fmt="none">RFC 2818</xref>. 164 166 </t> 165 167 <t>
Note: See TracChangeset
for help on using the changeset viewer.