Bug#318034: lynx: doesn't escape variable names for multipart/form-data

On Wed, Jul 13, 2005 at 03:00:13AM +0200, Frederic Briere wrote: > Package: lynx > Version: 2.8.5-2 > Severity: normal > > Given the following form: > > > ... > > > lynx will naively submit the following: > > Content-Disposition: form-data; name=""foo"" This is still wrong in lynx

Bug#318034: lynx: doesn't escape variable names for multipart/form-data

On Wed, Jul 13, 2005 at 03:55:00PM -0400, Frédéric Brière wrote: > On Wed, Jul 13, 2005 at 06:49:52AM -0400, Thomas Dickey wrote: > > >> > > did you mean > > > > > Yeah, sorry. I knew I'd screw up somehow. :) thanks (on my to-do list) -- Thomas E. Dickey http://invisible-island.net ft

Bug#318034: lynx: doesn't escape variable names for multipart/form-data

On Wed, Jul 13, 2005 at 03:00:13AM +0200, Frederic Briere wrote: > Package: lynx > Version: 2.8.5-2 > Severity: normal > > Given the following form: > > > http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe".

Bug#318034: lynx: doesn't escape variable names for multipart/form-data

Package: lynx Version: 2.8.5-2 Severity: normal Given the following 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