Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(32)

Issue 365903007: Handle unresolved remote hostname for TCP sockets. (Closed)

Created:
6 years, 5 months ago by Mallinath (Gone from Chromium)
Modified:
6 years, 4 months ago
Reviewers:
Sergey Ulanov, jiayl
CC:
juberti2, chromium-reviews, darin-cc_chromium.org, jam, miu+watch_chromium.org
Project:
chromium
Visibility:
Public.

Description

Handle 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 : #

Unified diffs Side-by-side diffs Delta from patch set Stats (+11 lines, -4 lines) Patch
M content/browser/renderer_host/p2p/socket_host_tcp.cc View 1 2 3 4 5 6 7 8 1 chunk +11 lines, -4 lines 0 comments Download

Messages

Total messages: 8 (0 generated)
Mallinath (Gone from Chromium)
6 years, 5 months ago (2014-07-02 23:20:40 UTC) #1
Sergey Ulanov
lgtm when my nits are addressed https://codereview.chromium.org/365903007/diff/40001/content/browser/renderer_host/p2p/socket_host_tcp.cc File content/browser/renderer_host/p2p/socket_host_tcp.cc (right): https://codereview.chromium.org/365903007/diff/40001/content/browser/renderer_host/p2p/socket_host_tcp.cc#newcode92 content/browser/renderer_host/p2p/socket_host_tcp.cc:92: remote_address.hostname, remote_address.ip_address.port()); DCHECK ...
6 years, 5 months ago (2014-07-03 03:31:06 UTC) #2
Mallinath (Gone from Chromium)
PTAL https://codereview.chromium.org/365903007/diff/40001/content/browser/renderer_host/p2p/socket_host_tcp.cc File content/browser/renderer_host/p2p/socket_host_tcp.cc (right): https://codereview.chromium.org/365903007/diff/40001/content/browser/renderer_host/p2p/socket_host_tcp.cc#newcode92 content/browser/renderer_host/p2p/socket_host_tcp.cc:92: remote_address.hostname, remote_address.ip_address.port()); On 2014/07/03 03:31:06, Sergey Ulanov wrote: ...
6 years, 5 months ago (2014-07-07 17:56:45 UTC) #3
Sergey Ulanov
still lgtm
6 years, 5 months ago (2014-07-07 18:22:15 UTC) #4
Mallinath (Gone from Chromium)
The CQ bit was checked by mallinath@chromium.org
6 years, 5 months ago (2014-07-07 22:41:53 UTC) #5
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/mallinath@chromium.org/365903007/120001
6 years, 5 months ago (2014-07-07 22:43:06 UTC) #6
commit-bot: I haz the power
FYI, CQ is re-trying this CL (attempt #1). The failing builders are: android_aosp on tryserver.chromium ...
6 years, 5 months ago (2014-07-08 03:24:19 UTC) #7
commit-bot: I haz the power
6 years, 5 months ago (2014-07-08 05:06:32 UTC) #8
Message was sent while issue was closed.
Change committed as 281668

Powered by Google App Engine
This is Rietveld 408576698