Hi,
I have a large corporate client that uses an outbound proxy, they did some packet sniffing and noticed that our jwplayer that uses rtmp is not respecting the proxy settings in the browser, and therefore is not working. Is this a bug? Is there something I can do to configure it?
The plain RTMP protocol uses port 1935, so the proxy should be setup to handle that traffic.
There are various other fallback ports, check the RTMP protocol specs. for them.
You can also use RTMPT which uses port 80.
Simply specify rtmpt instead of rtmp:bc.. 'streamer': '*rtmpt*://www.domain.com/application/instance',
The problem lies in the player which does not communicate with the proxy at all.
We have WPAD proxy configuration in our company and everything besides internal traffic is directed through proxy. JW player tries to connect to the server directly and the connection gets dropped on the firewall.
After switching to manual proxy setting (everything through proxy), the player still tries to connect directly...
This is a huge problem, because our policy orders not to allow traffic from the client bypassing the proxy server.
@Fedor -
There’s no way for the player to route plain RTMP traffic through the proxy. By default, RTMP traffic is sent through port 1935, but browser proxies don’t re-route non-HTTP traffic. This is the reason for the RTMPT variant – the traffic is routed over HTTP, and so the browser has the opportunity to route it through a proxy.
In summary:
RTMP – traffic is routed over port 1935, bypassing any HTTP proxies the browser might have in place
RTMPT – traffic is routed over port 80, which is handled by the browser’s proxy settings.
Additional info from Adobe about RTMP traffic and proxy servers:
http://www.adobe.com/devnet/flashcom/articles/firewalls_proxy03.html
PabloS
You say RTMPT - traffic is routed over port 80, which is handled by the browser's proxy settings. Does this then mean that if your browser is configured to use a proxy port, it will use the configured port and not port 80
