Closed Bug 1249172 Opened 8 years ago Closed 3 years ago

Make nsHttpAuthManager service e10s compliant

Categories

(Core :: Networking: HTTP, defect, P3)

defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
e10s + ---
firefox47 --- affected

People

(Reporter: qdot, Unassigned)

References

Details

(Whiteboard: [necko-backlog])

In bug 1237834, we were getting oranges in e10s tests. This is due to nsHttpAuthManager existing in both the parent and content processes, and information between the two getting desynced. We should only have an nsHttpAuthManager living in the parent process, and any content reference to the process should access that instance.
Should this block the roll out of e10s?
Flags: needinfo?(kyle)
I don't think so? The only test it affected was the one that's listed as a blocker on this bug, and that's fixed. All other tests that use it are either marked as skip on e10s (e.g. password manager tests), or don't break because they use anonymous credentials. mccr8, you got any opinion on this?
Flags: needinfo?(kyle) → needinfo?(continuation)
I don't really know anything about this, sorry.

jdm, it looks like you were the last person to make substantative changes to this class, back in 2012. Is this just not being used for much if we only notice in a few tests that it is broken in e10s?
Flags: needinfo?(continuation) → needinfo?(josh)
The only non-test usage of nsIHttpAuthManager (or the concrete class, nsHttpAuthManager) is in nsNPAPIPlugin.cpp. I have no idea how important retrieving HTTP authentication credentials is for Flash, but this feels like something that isn't a high priority in the list of e10s things.
Flags: needinfo?(josh)
Whiteboard: [necko-backlog]
Priority: -- → P2
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P2 → P1
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3

e10s has shipped and plugins are gone -> wfm.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.