Changeset 1073 for draft-ietf-httpbis-content-disp
- Timestamp:
- 02/11/10 15:20:18 (12 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
r1072 r1073 404 404 <meta name="dct.creator" content="Reschke, J. F."> 405 405 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-content-disp-latest"> 406 <meta name="dct.issued" scheme="ISO8601" content="2010-11-0 1">406 <meta name="dct.issued" scheme="ISO8601" content="2010-11-02"> 407 407 <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."> 408 408 <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."> … … 422 422 <td class="left">Updates: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved) 423 423 </td> 424 <td class="right">November 1, 2010</td>424 <td class="right">November 2, 2010</td> 425 425 </tr> 426 426 <tr> … … 429 429 </tr> 430 430 <tr> 431 <td class="left">Expires: May 5, 2011</td>431 <td class="left">Expires: May 6, 2011</td> 432 432 <td class="right"></td> 433 433 </tr> … … 458 458 in progress”. 459 459 </p> 460 <p>This Internet-Draft will expire on May 5, 2011.</p>460 <p>This Internet-Draft will expire on May 6, 2011.</p> 461 461 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 462 462 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 568 568 <p>Defined in <a href="#RFC5987" id="rfc.xref.RFC5987.1"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>: 569 569 </p> <pre class="inline"> ext-value = <ext-value, defined in <a href="#RFC5987" id="rfc.xref.RFC5987.2"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>, <a href="http://tools.ietf.org/html/rfc5987#section-3.2">Section 3.2</a>> 570 </pre><p id="rfc.section.3.1.p.4"> Parameter names <em class="bcp14">MUST NOT</em> be repeated; a header field value with multiple instances of the same parameter <em class="bcp14">SHOULD</em> be treatedas invalid.570 </pre><p id="rfc.section.3.1.p.4">Senders <em class="bcp14">MUST NOT</em> generate header field values with multiple instances of the same parameter name. Recipients <em class="bcp14">SHOULD</em> treat these values as invalid. 571 571 </p> 572 572 <p id="rfc.section.3.1.p.5">Note that due to the rules for implied linear whitespace (<a href="http://tools.ietf.org/html/rfc2616#section-2.1">Section 2.1</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.8"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>), OPTIONAL whitespace can appear between words (token or quoted-string) and separator characters. … … 928 928 </li> 929 929 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/253">http://tools.ietf.org/wg/httpbis/trac/ticket/253</a>>: "clarify what LWS means for the Content-Disp grammar" 930 </li> 931 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/258">http://tools.ietf.org/wg/httpbis/trac/ticket/258</a>>: "Avoid passive voice in message requirements" 930 932 </li> 931 933 </ul> -
draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.xml
r1072 r1073 156 156 157 157 <t> 158 Parameter names &MUST-NOT; be repeated; a header field value with 159 multiple instances of the same parameter &SHOULD; be treated as invalid. 158 Senders &MUST-NOT; generate header field values with multiple instances of 159 the same parameter name. Recipients &SHOULD; treat these values 160 as invalid. 160 161 </t> 161 162 <t> … … 884 885 "clarify what LWS means for the Content-Disp grammar" 885 886 </t> 887 <t> 888 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/258"/>: 889 "Avoid passive voice in message requirements" 890 </t> 886 891 </list> 887 892 </t>
Note: See TracChangeset
for help on using the changeset viewer.