Open
Bug 1510510
Opened 7 years ago
Updated 2 years ago
Extension webRequest features cannot force re-auth for proxy server after successful auth
Categories
(WebExtensions :: Request Handling, enhancement, P3)
Tracking
(Not tracked)
UNCONFIRMED
People
(Reporter: tdriley, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36
Steps to reproduce:
1. In a Web Extension, have a username and password ready in the JavaScript or storage that is correct for this proxy.
2. Add a handler for event webRequest.onAuthRequired which provides the username and password when challenged.
3. Set a proxy with browser.proxy.register.
4. Make a request (and auth) through the proxy.
5. Subsequent requests to this proxy will always use the same details in the `Proxy-Authorization`header, there is no way to force re-auth.
Actual results:
The same authentication details are always used in requests through that proxy.
Expected results:
There should be a way to "clear" out those details being used in the browser.
Update: can be recreated using the code examples here: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/webRequest/onAuthRequired#Examples
Updated•7 years ago
|
Product: Firefox → WebExtensions
Comment 2•7 years ago
|
||
This works as expected, but it might be nice to be able to clear.
Severity: normal → enhancement
Priority: -- → P3
| Comment hidden (offtopic) |
Comment 4•5 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'WebExtensions::Request Handling' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Component: Untriaged → Request Handling
Updated•4 years ago
|
Severity: normal → S3
Experiencing this as well, in Chrome I was able to do:
const clearProxyCache = async (proxyHostname: string) => {
const origins = [`http://${proxyHostname}`, `https://${proxyHostname}`]
await chrome.browsingData.remove(
{
origins,
},
{ cookies: true, cacheStorage: true, serviceWorkers: true },
)
}
Does not seem to work on Firefox for me, requiring browser restart. Would be nice if it worked
You need to log in
before you can comment on or make changes to this bug.
Description
•