ICE/TURN/TCP via an HTTP-Proxy which require Authentication
Balwant Bisht
10373: SOCKET
Start Time: 2016-02-29 16:23:38.973
t=53060 [st= 0] +SOCKET_ALIVE [dt=11]
--> source_dependency = 10372 (CONNECT_JOB)
t=53060 [st= 0] +TCP_CONNECT [dt=3]
--> address_list = ["192.168.0.112:3128"]
t=53060 [st= 0] TCP_CONNECT_ATTEMPT [dt=3]
--> address = "192.168.0.112:3128"
t=53063 [st= 3] -TCP_CONNECT
--> source_address = "192.168.0.114:54682"
t=53063 [st= 3] +SOCKET_IN_USE [dt=8]
--> source_dependency = 10371 (PROXY_CLIENT_SOCKET_WRAPPER)
t=53063 [st= 3] +HTTP_TRANSACTION_TUNNEL_SEND_REQUEST [dt=0]
t=53063 [st= 3] HTTP_TRANSACTION_SEND_TUNNEL_HEADERS
--> CONNECT trnltva01.bbcollab.com:443 HTTP/1.1
Host: trnltva01.bbcollab.com:443
Proxy-Connection: keep-alive
t=53063 [st= 3] HTTP_TRANSACTION_SEND_REQUEST_HEADERS
--> CONNECT trnltva01.bbcollab.com:443 HTTP/1.1
Host: trnltva01.bbcollab.com:443
Proxy-Connection: keep-alive
t=53063 [st= 3] SOCKET_BYTES_SENT
--> byte_count = 111
t=53063 [st= 3] -HTTP_TRANSACTION_TUNNEL_SEND_REQUEST
t=53064 [st= 4] +HTTP_TRANSACTION_TUNNEL_READ_HEADERS [dt=6]
t=53064 [st= 4] +HTTP_STREAM_PARSER_READ_HEADERS [dt=6]
t=53070 [st=10] SOCKET_BYTES_RECEIVED
--> byte_count = 2896
t=53070 [st=10] -HTTP_STREAM_PARSER_READ_HEADERS
t=53070 [st=10] HTTP_TRANSACTION_READ_TUNNEL_RESPONSE_HEADERS
--> HTTP/1.1 407 Proxy Authentication Required
Server: squid/3.5.15-20160223-r13996
Mime-Version: 1.0
Date: Mon, 29 Feb 2016 10:53:39 GMT
Content-Type: text/html;charset=utf-8
Content-Length: 3441
X-Squid-Error: ERR_CACHE_ACCESS_DENIED 0
Vary: Accept-Language
Content-Language: en
Proxy-Authenticate: Basic realm="Squid proxy-caching web server"
X-Cache: MISS from ADMIN
Via: 1.1 ADMIN (squid/3.5.15-20160223-r13996)
Connection: keep-alive
t=53070 [st=10] -HTTP_TRANSACTION_TUNNEL_READ_HEADERS
--> net_error = -127 (ERR_PROXY_AUTH_REQUESTED)
t=53071 [st=11] -SOCKET_IN_USE
t=53071 [st=11] -SOCKET_ALIVE
Philipp Hancke
--
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/61507754-bc9f-46d5-b293-f9ac36cf2da4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Silvia Pfeiffer
Oh man, here I thought this was fixed a long time ago.
Connections getting killed at the web proxy rather than the firewall is the main reason we encounter issues in corporate networks.
Is this the reason apprtc filters out tcp ice candidates?
How can we move the fixing of this bug up in priority? If everyone star-s it, that might be a start...
Best Regards,
Silvia.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CADxkKi%2BNZsBkozsP05xApCGxj89N%2B%2BbhbjzPVzrwRbKuhig73Q%40mail.gmail.com.
Justin Uberti
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CAHp8n2%3DK06sNZZTb9xOLxS2SXzvskhsc23dnyYPoWE%2BZXCc%3DOg%40mail.gmail.com.
Warren McDonald
In Health environments the proxy is always in place and we have to get firewall exemptions for direct egress to TURN to be able to make a call in a lot of cases.