Changeset 2311 for draft-ietf-httpbis/latest
- Timestamp:
- 27/07/13 10:30:12 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r2309 r2311 449 449 } 450 450 @bottom-center { 451 content: "Expires January 2 4, 2014";451 content: "Expires January 28, 2014"; 452 452 } 453 453 @bottom-right { … … 491 491 <meta name="dct.creator" content="Reschke, J. F."> 492 492 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 493 <meta name="dct.issued" scheme="ISO8601" content="2013-07-2 3">493 <meta name="dct.issued" scheme="ISO8601" content="2013-07-27"> 494 494 <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 495 495 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> … … 520 520 <tr> 521 521 <td class="left">Intended status: Standards Track</td> 522 <td class="right">July 2 3, 2013</td>522 <td class="right">July 27, 2013</td> 523 523 </tr> 524 524 <tr> 525 <td class="left">Expires: January 2 4, 2014</td>525 <td class="left">Expires: January 28, 2014</td> 526 526 <td class="right"></td> 527 527 </tr> … … 551 551 in progress”. 552 552 </p> 553 <p>This Internet-Draft will expire on January 2 4, 2014.</p>553 <p>This Internet-Draft will expire on January 28, 2014.</p> 554 554 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 555 555 <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 2974 2974 <p id="rfc.section.A.2.p.31">Some extraneous requirements about when servers are allowed to close connections prematurely have been removed. (<a href="#persistent.connections" title="Persistence">Section 6.3</a>) 2975 2975 </p> 2976 <p id="rfc.section.A.2.p.32">The semantics of the <a href="#header.upgrade" class="smpl">Upgrade</a> header field is now defined in responses other than 101 (this was incorporated from <a href="#RFC2817" id="rfc.xref.RFC2817.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>). (<a href="#header.upgrade" id="rfc.xref.header.upgrade.3" title="Upgrade">Section 6.7</a>)2976 <p id="rfc.section.A.2.p.32">The semantics of the <a href="#header.upgrade" class="smpl">Upgrade</a> header field is now defined in responses other than 101 (this was incorporated from <a href="#RFC2817" id="rfc.xref.RFC2817.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>). Furthermore, the ordering in the field value is now significant. (<a href="#header.upgrade" id="rfc.xref.header.upgrade.3" title="Upgrade">Section 6.7</a>) 2977 2977 </p> 2978 2978 <p id="rfc.section.A.2.p.33">Registration of Transfer Codings now requires IETF Review (<a href="#transfer.coding.registry" title="Transfer Coding Registry">Section 7.4</a>) -
draft-ietf-httpbis/latest/p1-messaging.xml
r2309 r2311 5037 5037 The semantics of the <x:ref>Upgrade</x:ref> header field is now defined in 5038 5038 responses other than 101 (this was incorporated from <xref 5039 target="RFC2817"/>). 5039 target="RFC2817"/>). Furthermore, the ordering in the field value is now 5040 significant. 5040 5041 (<xref target="header.upgrade"/>) 5041 5042 </t>
Note: See TracChangeset
for help on using the changeset viewer.