TURNS and HTTP PROXY : IP address in the CONNECT ?

[Skyboth]

Hi all

I am trying to make WebRTC flowing through an enterprise HTTP PROXY. I have setup a rfc5766-turn-server with a signed certificate. It is working fine in a network without HTTP PROXY (by forcing relay).

In the Javascript, I configure the following:

{"url":"turns:some.turn.server:443?transport=tls", "username":"someuser", "credential":"somecredential"}

When behind the HTTP PROXY, Chrome issues a HTTP CONNECT to open the TLS tunnel with the TURN server, but the CONNECT is encoded with the IP address of some.turn.server as Request-URI, and not the hostname.

CONNECT 12.23.34.45:443 HTTP/1.1

Instead of  

CONNECT some.turn.server:443 HTTP/1.1

The HTTP PROXY applies a policy to reject such CONNECT request.

To verify that the TURN server is correctly responding on 443, i just try to connect to https://some.turn.server, and it is working fine (TLS connection is established without no certificate and without proxy traversal issue).

I believe that it is related to the bug https://code.google.com/p/webrtc/issues/detail?can=2&start=0&num=100&q=&colspec=ID%20Pri%20Mstone%20ReleaseBlock%20Area%20Status%20Owner%20Summary&groupby=&sort=&id=3868

This bug seems to have been corrected in M42, but i still have the issue with stable M43, dev 45 and canary.

Has anyone been able to make the proxy traversal work properly with a TURN hostname ?