TURN access : no CONNECT launched if the DNS resolution can't be done locally

UNCONFIRMED
Unassigned

Status

()

Core
Networking
P3
normal
UNCONFIRMED
2 years ago
3 months ago

People

(Reporter: Xavier De Snoeck, Unassigned)

Tracking

43 Branch
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [necko-backlog])

(Reporter)

Description

2 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36

Steps to reproduce:

On a specific configuration of Desktop environment in a company, I don't have a local DNS resolution.
With a WebRTC test using a TURN server on port 443, the relay is not listed in the local candidates


Actual results:

The DNS resolution cannot be done locally so the HTTP CONNECT is never sent and therefore the relay never added to the local candidates.


Expected results:

Even if the DNS resolution isn't done locally, try to send the HTTP CONNECT request to the proxy (that should do the resolution).
Event if the resolution is added in /etc/hosts locally, send the CONNECT with the FQDN and not the IP address.

Updated

2 years ago
Component: Untriaged → Networking
Product: Firefox → Core
(Reporter)

Comment 1

2 years ago
Someone can help to investigate on this problem to find a fix for future versions of Firefox ?
We are blocked for use of WebRTC inside our enterprise network configuration due to this problem...

Thanks

Xavier
Whiteboard: [necko-backlog]
(Reporter)

Comment 2

2 years ago
The problem is still present on the version 47 and so I am still blocked on using WebRTC inside my company network when I try to make collaboration with external users...

Some can help me ?

Thanks

Xavier
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3
You need to log in before you can comment on or make changes to this bug.