Changeset 1134 for draft-ietf-httpbis-content-disp
- Timestamp:
- Feb 21, 2011, 5:29:47 AM (9 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
r1133 r1134 599 599 to save the response locally, rather than process it normally (as per its media type). 600 600 </p> 601 <p id="rfc.section.4.2.p.2">On the other hand, if it matches "inline" (case-insensitively), this implies default processing.</p> 601 <p id="rfc.section.4.2.p.2">On the other hand, if it matches "inline" (case-insensitively), this implies default processing. Therefore, the disposition 602 type "inline" is only useful when it is augmented with additional parameters, such as the filename (see below). 603 </p> 602 604 <p id="rfc.section.4.2.p.3">Unknown or unhandled disposition types <em class="bcp14">SHOULD</em> be handled by recipients the same way as "attachment" (see also <a href="#RFC2183" id="rfc.xref.RFC2183.2"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a>, <a href="http://tools.ietf.org/html/rfc2183#section-2.8">Section 2.8</a>). 603 605 </p> -
draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.xml
r1133 r1134 209 209 <t> 210 210 On the other hand, if it matches "inline" (case-insensitively), this implies 211 default processing. 211 default processing. Therefore, the disposition type "inline" is only useful 212 when it is augmented with additional parameters, such as the filename (see 213 below). 212 214 </t> 213 215 <t>
Note: See TracChangeset
for help on using the changeset viewer.