The returned Proxy info from nsIProtocolProxyService contains the flags used to perform the proxy resolution. The async version of that resolution wasn't recording the flags correctly. We almost never actually use the async resolution (which I'm fixing in another bug) and the only thing the flags are really important to are websockets. so it doesn't seem to be a problem for any in-tree code, but its a problem for the code I'm writing.
Created attachment 646613 [details] [diff] [review] patch 0
Assignee: nobody → mcmanus
Status: NEW → ASSIGNED
Attachment #646613 - Flags: review?(cbiesinger)
Comment on attachment 646613 [details] [diff] [review] patch 0 heh. "oops"
Attachment #646613 - Flags: review?(cbiesinger) → review+
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla17
You need to log in before you can comment on or make changes to this bug.