bug#53941: 27.2; socks + tor dont work with https

[J.P.]

"J.P." <jp@neverwas.me> writes:

> There's also the issue of DNS lookups for verifying domain certs. Last I
> looked, we can't run `nsm' checks without involving the system resolver,
> which may be a deal breaker for the more privacy minded. If that's true,
> we may want to find an acceptable way of cluing folks in to the
> situation.

Just a tiny update to the POC `url' integration stuff in case anyone
ever tries it. Previously, when connecting to a .onion domain over TLS,
e.g.,

  https://www.dwnewsgngmhlplxy6o2twtfgjnrnjxbegbwqx6wnotdhkzt562tszfid.onion/en/

you'd get spammed with "name or service unknown" messages in the echo
area with every EWW link clicked (at least on GNU Linux, probably from
something like GAI EAI_NONAME). Anyway, no longer. Also added a test, a
news entry, and some doc tweaks. Thanks.

0000-v3-v4.diff
Description: Text Data

0001-Don-t-hard-code-server-ports-in-SOCKS-tests.patch
Description: Text Data

0002-Improve-SOCKS-error-handling-and-add-support-for-4a.patch
Description: Text Data

0003-POC-Simplify-network-stream-openers-in-socks.el.patch
Description: Text Data

0004-POC-Integrate-the-socks-and-url-libraries.patch
Description: Text Data