Ignore:
Timestamp:
06/03/11 11:01:07 (10 years ago)
Author:
julian.reschke@…
Message:

use RFC2119 keywords when discussing handling the filename parameter (see #278)

File:
1 edited

Legend:

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

    r1145 r1152  
    262262      extensions instead. Trusting the server-provided file extension could
    263263      introduce a privilege escalation when the saved file is later opened
    264       (consider ".exe"). Thus, recipients need to ensure that a file extension
     264      (consider ".exe"). Thus, recipients &SHOULD; ensure that a file extension
    265265      is used that is safe, optimally matching the media type of the received
    266266      payload.
    267267    </t></x:lt>
    268268    <x:lt><t>
    269       Recipients are advised to strip or replace character sequences that are
     269      Recipients &SHOULD; strip or replace character sequences that are
    270270      known to cause confusion both in user interfaces and in filenames, such as
    271271      control characters and leading and trailing whitespace.
     
    274274      Other aspects recipients need to be aware of are names that have a
    275275      special meaning in the file system or in shell commands, such as "." and "..",
    276       "~", "|", and also device names.
     276      "~", "|", and also device names. Recipients &SHOULD; ignore or substitute
     277      names like these.
    277278    </t></x:lt>
    278279  </list>
     
    10401041<section title="Since draft-ietf-httpbis-content-disp-06" anchor="changes.since.06">
    10411042<t>
    1042   None yet.
     1043  Closed issues:
     1044  <list style="symbols">
     1045     <t>
     1046      <eref target="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/278"/>:
     1047      "conformance language"
     1048    </t>
     1049  </list>
    10431050</t>
    10441051</section>
Note: See TracChangeset for help on using the changeset viewer.