[pkg-lynx-maint] Bug#791452: Bug#791452: lynx: http_proxy variable silently ignored!

[Andy Valencia]

--------
[Axel Beckert <abe at debian.org> writes:]

> * according to the man page there is no https_proxy variable,
> * http_proxy should work for https as well as I read it,
> * it doesn't work with the mentioned host but http instead of https
>   for me either.

I read lynx as thinking of the world as proto://path

Thus, when "proto" is "https", they expect https_proxy.
(My thinking may be polluted by having read some of the proxy handling
code in Lynx src.)

Oh, yeah, also in the source:

LYrcFile.h:#define RC_HTTPS_PROXY                  "https_proxy"
LYrcFile.h:#define RC_HTTP_PROXY                   "http_proxy"

Distinct.

> "telnet localhost 8118" works as well as "telnet ::1 8118" works, but
> "telnet 127.0.0.1 8118" does not work: Connection refused

I tested with "tinyproxy", in an all-IPv4 network (residue of some
bad regressions a while back in various apps, I'll have to revisit
some day soon).

I have two Internet feeds, and my host goes out one and I set the proxy
to go out the other.  So then I can visit a page on an external web
server of mine and see from the logs what client IP address was
involved.  It definitely works in this basic configuration.

So I try two versions.  My dev build (for -g symbols):
    Lynx Version 2.8.8rel.2 (09 Mar 2014)
and Wheezy repo:
    Lynx Version 2.8.8dev.12 (22 Feb 2012)

Both work, with verification in the logs that the proxy is used when
http_proxy is set.

I'm not well set up to test IPv6 aspects; if you don't have time I'll
have to put together a lab network which will be later this week.
Let me know and I'll put it on the calendar.

Also, if there's some other Lynx version in play, point me at it and
I'll test.

Finally(!), haven't heard from the submitter.  Should I try and ping
his email directly?  What's the usual practice?

Thanks,
Andy