Closed
Bug 1216413
Opened 9 years ago
Closed 9 years ago
WebRTC - HTTP/1.1 407 proxy authentication required - Firefox ESR 38.1.0
Categories
(Core :: WebRTC: Signaling, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1115934
People
(Reporter: remyadas10, Unassigned, NeedInfo)
References
Details
(Keywords: regression)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10) AppleWebKit/600.1.25 (KHTML, like Gecko) Version/8.0 Safari/600.1.25
Steps to reproduce:
The WebRTC call fails when using Firefox ESR 38.1.0 in corporate network.
In the same network conditions Firefox ESR 31.5 is working fine.
Actual results:
When I checked the packet capture using Wireshark I found the issue is happening when trying to connect to TURN server. (I'm using rfc5766-turn-server). Its showing "HTTP/1.1 407 proxy authentication required"
In the Firefox connection log I can see : "(generic/ERR) nr_socket_proxy_tunnel_read unable to connect 407"
Expected results:
Connection should go through and able to establish webRTC call
Updated•9 years ago
|
Comment 1•9 years ago
|
||
Can you run with NSPR_LOG_MODULES=mtransport:4,signaling:4 NSPR_LOG_FILE=some_log_file, and also upload the connection logs? Thanks
Component: WebRTC → WebRTC: Signaling
Comment 2•9 years ago
|
||
The error message "nr_socket_proxy_tunnel_read unable to connect" comes from code which uses the configure HTTP proxy (if one is configured). As this feature landed in 38 it makes sense that the behavior is different with 31.5.
Looks like your proxy requires authentication, which we don't support. See bug 1115934 for that.
If it worked with 31.5 I would recommend to try it without the proxy or put the WebRTC calling service/page on the list of exceptions for your proxy.
See Also: → 1115934
Comment 3•9 years ago
|
||
Flags: needinfo?(remyadas10)
Comment 4•9 years ago
|
||
I'm pretty sure this a duplicate of bug 1115934. If you disagree feel free to re-open this bug or ask further questions in here.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•