diff options
| author | mallinath@chromium.org <mallinath@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-06-21 21:07:55 +0000 |
|---|---|---|
| committer | mallinath@chromium.org <mallinath@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-06-21 21:07:55 +0000 |
| commit | f25eb36e3344223ffcabcf96d54cf000862d6088 (patch) | |
| tree | 5b3517da2e3cf47cf72c307334c0b14daa150e61 /net/tools/fetch | |
| parent | f6dfbfd60af638964d15dc5b752cecd3504dc2d1 (diff) | |
| download | chromium_src-f25eb36e3344223ffcabcf96d54cf000862d6088.zip chromium_src-f25eb36e3344223ffcabcf96d54cf000862d6088.tar.gz chromium_src-f25eb36e3344223ffcabcf96d54cf000862d6088.tar.bz2 | |
Proxy detection is important feature for the P2P sockets, as
it provides additional security for enterprise use cases.
Communication between webrtc endpoints happens through UDP/TCP/STUN
with or without the help of TURN server.
In case of firewall restrictions like outgoing UDP block and allowing
only secure ports, direct communication between two endbecomes impossible
without the help of TURN.
In the presence of proxies, direct communication even to TURN server also
becomes impossible without first esablishing connection with the proxy.
This CL is trying to address the last problem.
If proxies are configured(HTTP/S/SOCKS) send data(stun+media) through it.
jingle_glue::ProxyResolvingClientSocket solves the problem of proxy detection and establishing the connection and also it's a type of net::StreamSocket, this class can be directly used in P2PSocketHostTcpBase.
R=sergeyu@chromium.org,juberti@chromium.org,thakis@chromium.org
Review URL: https://chromiumcodereview.appspot.com/17132012
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@207919 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'net/tools/fetch')
0 files changed, 0 insertions, 0 deletions