Changeset 1195
- Timestamp:
- 17/03/11 13:02:00 (11 years ago)
- Location:
- draft-ietf-httpbis-content-disp/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.html
r1192 r1195 371 371 } 372 372 @bottom-center { 373 content: "Expires September 1 6, 2011";373 content: "Expires September 18, 2011"; 374 374 } 375 375 @bottom-right { … … 412 412 <meta name="dct.creator" content="Reschke, J. F."> 413 413 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-content-disp-latest"> 414 <meta name="dct.issued" scheme="ISO8601" content="2011-03-1 5">414 <meta name="dct.issued" scheme="ISO8601" content="2011-03-17"> 415 415 <meta name="dct.abstract" content="RFC 2616 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard. This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization aspects."> 416 416 <meta name="description" content="RFC 2616 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard. This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization aspects."> … … 430 430 <td class="left">Updates: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved) 431 431 </td> 432 <td class="right">March 1 5, 2011</td>432 <td class="right">March 17, 2011</td> 433 433 </tr> 434 434 <tr> … … 437 437 </tr> 438 438 <tr> 439 <td class="left">Expires: September 1 6, 2011</td>439 <td class="left">Expires: September 18, 2011</td> 440 440 <td class="right"></td> 441 441 </tr> … … 466 466 in progress”. 467 467 </p> 468 <p>This Internet-Draft will expire on September 1 6, 2011.</p>468 <p>This Internet-Draft will expire on September 18, 2011.</p> 469 469 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 470 470 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 552 552 in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>. 553 553 </p> 554 <p id="rfc.section.2.p.2">This specification uses the augmented BNF notation defined in <a href="http://tools.ietf.org/html/rfc2616#section-2.1">Section 2.1</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, including its rules for implied linear whitespace (LWS).554 <p id="rfc.section.2.p.2">This specification uses the augmented BNF (ABNF) notation defined in <a href="http://tools.ietf.org/html/rfc2616#section-2.1">Section 2.1</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, including its rules for implied linear whitespace (LWS). 555 555 </p> 556 556 <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a id="conformance.and.error.handling" href="#conformance.and.error.handling">Conformance and Error Handling</a></h1> -
draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.xml
r1192 r1195 112 112 </t> 113 113 <t> 114 This specification uses the augmented BNF notation defined in114 This specification uses the augmented BNF (ABNF) notation defined in 115 115 <xref target="RFC2616" x:fmt="of" x:sec="2.1"/>, including its rules for 116 116 implied linear whitespace (LWS).
Note: See TracChangeset
for help on using the changeset viewer.