Closed
Bug 1222352
Opened 9 years ago
Closed 9 years ago
Resource Timing - nextHopProtocol does not work in e10s
Categories
(Core :: Networking, defect)
Core
Networking
Tracking
()
RESOLVED
FIXED
mozilla45
People
(Reporter: valentin, Assigned: valentin)
References
(Blocks 1 open bug)
Details
(Keywords: productwanted)
Attachments
(1 file)
|
6.51 KB,
patch
|
u408661
:
review+
|
Details | Diff | Splinter Review |
No description provided.
|
Assignee | |
Comment 2•9 years ago
|
||
The problem is that mSecurityInfo in HttpChannelChild doesn't QI to nsISSLSocketControl, so we can't get the negotiated NPN token from that. Instead we use the protocol version from the response head, which is always http/1.1 for e10s. I need to pass it from the parent to the child channel.
Flags: needinfo?(valentin.gosu)
|
||
Updated•9 years ago
|
tracking-e10s:
--- → -
Keywords: productwanted
|
|
Assignee | |
Comment 3•9 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=4df4d69b4bfe
|
|
Assignee | |
Comment 4•9 years ago
|
||
Attachment #8691071 -
Flags: review?(hurley)
Attachment #8691071 -
Flags: review?(hurley) → review+
|
|
Assignee | |
Comment 5•9 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/1e426f4d6f3625d2b3f51bee8f003bb1a0bec635 Bug 1222352 - Resource Timing - nextHopProtocol does not work in e10s r=nwgh
|
||
Comment 6•9 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/1e426f4d6f36
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla45
You need to log in
before you can comment on or make changes to this bug.
Description
•