Closed Bug 1509409 Opened 6 years ago Closed 5 years ago

Look at the proxy resolution API

Categories

(Core :: Networking, enhancement, P3)

Product:
Core
Component:
Networking
Type:
enhancement

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox65 --- affected

People

(Reporter: dragana, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged]) 

      No description provided.
This is a subproject of the SPI work, not necessarily blocking enabling it.  It's not strictly necessary to move proxy resolution to the dedicated process to deliver its main goals.  

We are using the system proxy API and PAC evaluation on the parent process right now.  

- PAC eval on a non-main process (maybe even a completely new PAC dedicated process) makes pretty much sense.  

- Moving proxy res service code to SP would be a perf win as proxy resolution result message dispatch we do for every request (default browser settings) would not have to go through the busy main proc main thread.
Priority: -- → P3
Whiteboard: [necko-triaged]
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.