Closed Bug 1319630 Opened 8 years ago Closed 6 years ago

FindProxyForURL().type should be able to use new value "system"

Categories

(WebExtensions :: Request Handling, defect, P3)

Product:
WebExtensions
Component:
Request Handling
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1443259

People

(Reporter: mattw, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [proxy] triaged) 

The "SYSTEM" return type should work similarly to the system proxy mode in the Chrome API, which takes the proxy configuration from the operating system.

For more information, see the proxy API design document: https://docs.google.com/document/d/1W45o5X2bFRPrTaQDFp9IzTJ8njCVfEgyENS7i2owaUI/edit?usp=sharing
How is this fixed/resolved? Is it already supported by the implementation in bug #1295807?
Flags: needinfo?(mwein)
This bug isn't fixed/resolved, it just depends on bug 1295807 which was recently fixed/resolved. Bug 1295807 sets up the infrastructure for these bugs to be worked on, and the next stage in the development is to land these bugs. The main tracking bug for the Proxy API is bug 1283639.
Flags: needinfo?(mwein)
webextensions: --- → ?
webextensions: ? → ---
This should become a new return type as part of bug 1381290.
Priority: -- → P3
Summary: Add support for the new "SYSTEM" return type to FindProxyForURL → FindProxyForURL().type should be able to use new value "system"
Mozilla, please fix this bug please as soon as possible, without foxy proxy and similar web-extensions use your browser completely impossible.

If you have already decided to use web-extensions, then make like on Chrome. Chrome does not have this problem.

Thanks.
Given the new asyn api we will deprecate the non-complaint pac script initially done for webextensions.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Product: Toolkit → WebExtensions
You need to log in before you can comment on or make changes to this bug.