Package: lynx Version: 2.8.5-2 Severity: normal Given the following form:
<FORM ENCTYPE="multipart/form-data" ...> <INPUT NAME="quot;foo"" ... ... </FORM> lynx will naively submit the following: Content-Disposition: form-data; name=""foo"" which is clearly wrong. RFC 1867 never actually bothers to formally define Content-Disposition, but it does refer to RFC 1806, which (via RFC 822) mandates that this header's value be a quoted-string, and must be escaped properly. -- 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]
