Skip to main content

How to add custom proxy settings per Web Page using the Advanced Player Directives

Updated this week

There are cases where custom proxy settings are required to access a specific web page, such as a dashboard. The rest of the player connections will not use the proxy.

Consider the following example:

Your dashboard on dashboard.example.com can only be accessed through the following HTTP proxy:

  • Proxy: myproxy.example.com

  • Port: 3128

  • Username: user

  • Password: pass

You can configure this under the Advanced Player Directives (Screen configuration→ Advanced → Customization → Advanced Player Directives) using the following directive:

custom_proxy_settings={ "dashboard.example.com" : { "username" : "user" , "password" : "pass" , "proxy" : "myproxy.example.com" , "no_proxy" : "static.example.com" }}

Make sure your directive is a single line of text when pasting it to the Advanced Player Directives field.

Note

In the example above, we added an exception using the no_proxy key. This allows some web page resources to skip loading through the proxy. In these cases, any resources under static.example.com will not use the proxy.

Did this answer your question?