Ignore:
Timestamp:
21/09/10 07:54:16 (10 years ago)
Author:
julian.reschke@…
Message:

editorial improvements, suggested by MNot

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.xml

    r1013 r1016  
    117117  The Content-Disposition response header field is used to convey additional
    118118  information about how to process the response payload, and also can be used
    119   to attach additional metadata, such as the filename.
     119  to attach additional metadata, such as the filename to use when saving the
     120  response payload locally.
    120121</t>
    121122
     
    154155<section title="Disposition Type" anchor="disposition.type">
    155156<t>
    156   If the disposition type matches "attachment" (case-insensitively), this indicates that the user agent should not display the response,
    157   but directly enter a "save as..." dialog.
    158 </t>
    159 <t>
    160   On the other hand, if it matches "inline" (case-insensitively), this implies default processing.
    161 </t>
    162 <t>
    163   Unknown or unhandled disposition types &SHOULD; be handled the same way as "attachment"
    164   (see also <xref target="RFC2183" x:fmt="," x:sec="2.8"/>).
     157  If the disposition type matches "attachment" (case-insensitively), this
     158  indicates that the user agent should prompt the user to save the response
     159  locally, rather than process it normally (as per its media type).
     160</t>
     161<t>
     162  On the other hand, if it matches "inline" (case-insensitively), this implies
     163  default processing.
     164</t>
     165<t>
     166  Unknown or unhandled disposition types &SHOULD; be handled the same way as
     167  "attachment" (see also <xref target="RFC2183" x:fmt="," x:sec="2.8"/>).
    165168</t>
    166169</section>
     
    207210      to hold type information in the file system, but rely on filename
    208211      extensions instead. Trusting the server-provided file extension could
    209       introduce a privilege escalation when later on the file is opened locally
     212      introduce a privilege escalation when the saved file is later opened
    210213      (consider ".exe"). Thus, recipients need to ensure that a file extension
    211214      is used that is safe, optimally matching the media type of the received
     
    358361<t>
    359362  Thanks to Rolf Eike Beer, Bjoern Hoehrmann, Alfred Hoenes, Roar Lauritzsen,
    360   and Henrik Nordstrom for their valuable feedback.
     363  Henrik Nordstrom, and Mark Nottingham for their valuable feedback.
    361364</t>
    362365</section> 
Note: See TracChangeset for help on using the changeset viewer.