Package: lynx
Version: 2.8.5-2
Severity: normal
When doing a file upload, lynx pastes the filename as-is, even if it
includes non-ASCII characters. However, RFC 1521 states that "in no
event are headers (either message headers or body-part headers) allowed
to contain anything other than ASCII characters."
RFC 1867 says that the filename "might be approximated or encoded using
the method of RFC 1522". It doesn't mandate any particular encoding,
though, so that makes it rather useless.
FWIW, all the other browsers out there (IE, Mozilla, Opera) don't bother
at all, and merely encode the filename the same way as the other fields.
("Standards? We don't need no stinkin' standards!")
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11-2
Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1)
Versions of packages lynx depends on:
ii libbz2-1.0 1.0.2-7 high-quality block-sorting file co
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii libgnutls11 1.0.16-13.1 GNU TLS library - runtime library
ii libncursesw5 5.4-8 Shared libraries for terminal hand
ii zlib1g 1:1.2.2-7 compression library - runtime
Versions of packages lynx recommends:
ii mime-support 3.34-1 MIME files 'mime.types' & 'mailcap
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
