-------- [Jack Ryan <nore...@remailer.cpunk.us> writes:] > Having a commandline "--proxy" option would ensure that the users > expectation is known to the tool. Then if anything is wrong with the > users syntax or something goes wrong with the proxy, lynx can fail > safely and print an error.
If user safety is the priority here, but we otherwise want to minimize our disconnect with the upstream Lynx developer, we might want to consider instead a --must-proxy flag; connections which are not proxied do not succeed. I would propose that this be applied globally; it would inhibit Gopher, FTP, and others as well as http[s]. Comments welcome. I can cook this up if it passes the laugh test. Andy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
