Webrtc needs some API for determining whether its origin was loaded via a web proxy
Categories
(Core :: Networking, enhancement, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox109 | --- | fixed |
People
(Reporter: bwc, Assigned: mleclair)
References
Details
(Whiteboard: [necko-triaged][necko-priority-queue])
Attachments
(1 file)
Right now, we've been trying to use nsIProxiedChannel::GetProxyInfo(), but this just does not work on the content process because that API is not implemented.
In short, webrtc needs this in order to implement the media.peerconnection.ice.proxy_only_if_behind_proxy pref. The intent here is to disable UDP networking, as well as direct p2p TCP connections, when this pref is set and a web-proxy is enabled.
We do not necessarily need a full ProxyInfo, we just need to answer the question "Was my Document loaded via a web proxy?". We are already grabbing the LoadInfo so we can pass it along to the TCP networking code in the socket process, so maybe something simple could be added to the LoadInfo.
|
Reporter | |
Comment 1•2 years ago
•
|
||
I should also point out that since our ICE stack runs in the content process when the socket process is disabled, and delegates the actual network operations to the parent process, we cannot simply get this information after we've made the hop to the socket process.
|
||
Comment 2•2 years ago
•
|
||
Setting priority to P2 because the feature bug for the WebRTC team is P2.
|
||
Updated•2 years ago
|
|
Assignee | |
Comment 3•2 years ago
|
||
|
||
Updated•2 years ago
|
Pushed by mleclair@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/2bb0a039dfbf added proxy attribute to verify if a proxy is used r=necko-reviewers,kershaw
|
|
Reporter | |
Comment 5•2 years ago
|
||
Woohoo! Thanks!
|
||
Comment 6•2 years ago
|
||
| bugherder | ||
Description
•