You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The application of declarativeNetRequest on proxies does not appear to have been discussed.
As an example, it can be useful for passing user/pass via headers, as an (easier!?) alternative to webRequest.onAuthRequired.
Note: It might require a special flag/property in DNR to separate it from other requests.
Scenario:Browser -> proxyurl.com -> target.com
It appears that the urlFilter refers to the target.com.
Passing user/pass was only an example. There might!? be occasions where DNR control might be needed for the proxy URL e.g. stripping some headers, or adding cookies, etc.
The application of
declarativeNetRequest
on proxies does not appear to have been discussed.As an example, it can be useful for passing user/pass via headers, as an (easier!?) alternative to
webRequest.onAuthRequired
.Note: It might require a special flag/property in DNR to separate it from other requests.
Scenario: Browser -> proxyurl.com -> target.com
It appears that the
urlFilter
refers to the target.com.See Also:
Issue 1318138: Add headers using declarativeNetRequest only if the request is being proxied
The text was updated successfully, but these errors were encountered: