DescriptionHandle unresolved remote hostname for TCP sockets.
Users of WebRTC reported that certain corporate networks that restrict the DNS resolution
to certain domains. In which case DNS resolve might fail in those conditions.
In that case proxy can resolve the addresses by using CONNECT methods.
Chrome TCP P2P sockets already handles the proxy scenarios, so by just providing the
hostname to TCP sockets should solve these problamatic scenarios.
After socket moves to a connected state, resolved address (peer address) must be reported
back to the renderer process. It's certainly needed for sending packets, but for validation
purposes its required.
BUG=https://code.google.com/p/webrtc/issues/detail?id=3384
R=sergeyu@chromium.org,jiayl@chromium.org
TBR=cevans@chromium.org
CC=juberti@chromium.org
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=281668
Patch Set 1 #Patch Set 2 : #Patch Set 3 : #
Total comments: 10
Patch Set 4 : #Patch Set 5 : #Patch Set 6 : #Patch Set 7 : #Patch Set 8 : #Patch Set 9 : #Messages
Total messages: 8 (0 generated)
|