Open Bug 1254891 Opened 9 years ago Updated 2 years ago

Implement HTTP Proxy support for ICE TCP active connetions

Categories

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

defect

Tracking

()

People

(Reporter: drno, Unassigned)

References

(Blocks 1 open bug)

Details

If Firefox is being used in enterprise networks which blocks outgoing TCP connections and only allows connecting through a HTTP proxy, then we should be able to connect to a WebRTC service via TURN TCP right now. If the WebRTC service supports ICE TCP we could connect directly to it by going through the HTTP proxy directly to the service and avoiding the TURN relay.
backlog: --- → webrtc/webaudio+
Rank: 29
In case it is of interest, this is implemented and I've tested it as working in Chrome 60.
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
This should be fixed by bug 1203503. Previously a TURN socket wrapper was used to create proxied relay candidates [1]. In that bug, we override the default socket constructor [2] to pass an optional proxy configuration to create proxied sockets [3]. If my patches in bug 1416220 land, the proxy socket will provide secure connections [4]. bwc, I think this is accurate? https://searchfox.org/mozilla-central/source/media/mtransport/third_party/nICEr/src/ice/ice_component.c#591 [1] https://searchfox.org/mozilla-central/source/media/mtransport/nricectx.cpp#630 [2] https://searchfox.org/mozilla-central/source/media/mtransport/nr_socket_prsock.cpp#2178 [3] https://searchfox.org/mozilla-central/source/media/mtransport/nr_socket_prsock.cpp#1980 [4]
Flags: needinfo?(docfaraday)
We will definitely try to use NrSocketProxy for ICE TCP if an http proxy is configured. Whether it works is another matter entirely!
Flags: needinfo?(docfaraday)
"works for me" using https://demos.openvidu.io/basic-videoconference/ and nightly build from bug 1505329 comment 7. Firefox release 63 did not.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.