- Timestamp:
- Feb 16, 2011, 6:21:02 AM (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.html
r1117 r1118 365 365 } 366 366 @bottom-center { 367 content: "Expires August 16, 2011";367 content: "Expires August 20, 2011"; 368 368 } 369 369 @bottom-right { … … 405 405 <meta name="dct.creator" content="Reschke, J. F."> 406 406 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-content-disp-latest"> 407 <meta name="dct.issued" scheme="ISO8601" content="2011-02-1 2">407 <meta name="dct.issued" scheme="ISO8601" content="2011-02-16"> 408 408 <meta name="dct.abstract" content="HTTP/1.1 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."> 409 409 <meta name="description" content="HTTP/1.1 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."> … … 423 423 <td class="left">Updates: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved) 424 424 </td> 425 <td class="right">February 1 2, 2011</td>425 <td class="right">February 16, 2011</td> 426 426 </tr> 427 427 <tr> … … 430 430 </tr> 431 431 <tr> 432 <td class="left">Expires: August 16, 2011</td>432 <td class="left">Expires: August 20, 2011</td> 433 433 <td class="right"></td> 434 434 </tr> … … 459 459 in progress”. 460 460 </p> 461 <p>This Internet-Draft will expire on August 16, 2011.</p>461 <p>This Internet-Draft will expire on August 20, 2011.</p> 462 462 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 463 463 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 548 548 </p> 549 549 <p id="rfc.section.3.p.2">This specification also defines certain forms of the header field-value to be invalid, using both ABNF and prose requirements, 550 but it does not define special handling these invalid field-values.550 but it does not define special handling of these invalid field-values. 551 551 </p> 552 552 <p id="rfc.section.3.p.3">Sending implementations <em class="bcp14">MUST NOT</em> generate Content-Location header fields that are invalid.
Note: See TracChangeset
for help on using the changeset viewer.