about:networking has DNS lookup feature -- investigate proxy settings compliance

We should look at the DNS lookup code on about:networking and make sure it respects our proxy settings or is useful at all in our context.

added TorBrowserTeam201704 component::applications/tor browser ff52-esr owner::tbb-team priority::medium resolution::fixed severity::normal sponsor::4 status::closed tbb-7.0-must-alpha type::task labels

Trac:
Keywords: N/A deleted, tbb-7.0-must added

Getting those tickets on our March radar as well.

Trac:
Keywords: N/A deleted, TorBrowserTeam201703 added

Moving tickets over to April

Trac:
Keywords: TorBrowserTeam201703 deleted, TorBrowserTeam201704 added

Getting this on our radar for alpha release in less than two weeks.

Trac:
Keywords: tbb-7.0-must deleted, tbb-7.0-must-alpha added

function doLookup() {
  let host = document.getElementById("host").value;
  if (host) {
    gDashboard.requestDNSLookup(host, displayDNSLookup);
  }
}

(https://dxr.mozilla.org/mozilla-esr52/source/toolkit/content/aboutNetworking.js#389) is responsible for the lookup which goes to Dashboard::RequestDNSLookup() (https://dxr.mozilla.org/mozilla-esr52/source/netwerk/base/Dashboard.cpp#735) which calls mDnsService->AsyncResolve() which in turn calls nsDNSService::AsyncResolveExtended() which we have patched.

The browser console returns our error code: NS_ERROR_UNKNOWN_PROXY_HOST. So, we are good here I think.

Trac:
Status: new to closed
Resolution: N/A to fixed

closed

moved to tpo/applications/tor-browser#21611 (closed)