Closed Bug 1371270 Opened 8 years ago Closed 8 years ago

WebExtensions ProxyAPI: support digest authentication

Categories

(WebExtensions :: Untriaged, enhancement, P2)

Product:
WebExtensions
Component:
Untriaged
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: ericjung, Unassigned)

Details

(Whiteboard: [Proxy, outreach] triaged [awe:client@anonymox.net])

Digest access authentication is needed for the WebExtensions Proxy API. Probably need bug 1359543 to be done first so that WebExtensions have an easy way to provide a username/password.
We may be able to get auth to work with https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/webRequest/onAuthRequired. That wouldn't be as clean as providing auth info in the ProxyAPI's FindProxyForPAC() function, but could be a good workaround for now. See also bug 1360404 - Accept credentials in proxyInfo object (non-SOCKS)
Blocks anonymoX
Whiteboard: [outreach]
Priority: -- → P2
Whiteboard: [outreach] → [Proxy, outreach] triaged
Whiteboard: [Proxy, outreach] triaged → [Proxy, outreach] triaged [awe:client@anonymox.net]
> We may be able to get auth to work with https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/webRequest/onAuthRequired. Confirmed this works, and I have an example extension. However, it does *not* work for SOCKS proxy servers. Only HTTP and HTTPS/SSL proxy servers. So this is not a complete solution.
SOCKS auth is handled now in bug 1381290. Auth types are handled at the http or socks layer, nothing we need in the api for it.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
Product: Toolkit → WebExtensions
You need to log in before you can comment on or make changes to this bug.