On Sat, Oct 08, 2005 at 01:34:37AM +0200, Pierre Pronchery wrote: > On Fri, 2005-10-07 at 19:24 -0400, Justin Pryzby wrote: > > On Sat, Oct 08, 2005 at 01:10:18AM +0200, Pierre Pronchery wrote: > > > Package: lynx > > > Version: 2.8.5-2 > > > Severity: normal > > > > > > Hi, > > > > > > if I connect lynx to a minimal HTTP server which sends just this: > > > > > > HTTP/1.1 401 Permission Denied > > > Connection: close > > > > > > without actually closing the connection, lynx asks this: > > > "Show the 401 message body? (y/n)" > > > then a "y" answer makes lynx completly unresponsible. > > > > > > I hope this is not "expected" behaviour from lynx. > > What should the expected behaviour be? > > A timeout I guess, or let a key interrupt current operation. I don't > know, but C-c seems a bit "violent" to me, say, if you'd just like to go > back some time. TCP guarantees a timeout of some duration, anyway.
> Maybe this could be just "wishlist" then, but my thought was what if any > web server you visit can force you to exit lynx? Isn't this a security > problem? Hardly a security problem, I don't think. You viewed the web page, and all it can do is prevent you from continuing to use that lynx process. (And I suspect you can regain control by using gdb -p $(pidof lynx): return -1). I agree, though, that lynx could be improved with an "abort" button. And also a way to not stop for 3 seconds after each status line! I suggest to retitle the bug, and change the severity, by sending appropriate commands (as documented on http://bugs.debian.org/). -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
