Browsermob Proxy and Selenium Grid

Browsermob Proxy is an open source proxy that can be used with our Gridlastic Connect tunnel client to tunnel traffic to test your internal behind firewall web servers. Browsermob proxy should be used when there is a specific need like for performance testing as it has built in support for producing performance data. Otherwise our recommendation for tunneling via a proxy is to use the open source proxy Squid.


To tunnel your selenium grid nodes through your own Browsermob Proxy, follow the setup below.

Click chart to enlarge.

Sample Gridlastic Connect Config file:
    remote_port: 9001
      tcp: 9091
    remote_port: 9002
      tcp: 9092
    remote_port: 9003
      tcp: 9093
Start the tunnel client like
./gridc -username=USERNAME --password=PASSWORD -config=config.cfg start BMP-PROXY-1 BMP-PROXY-2 BMP-PROXY-3
the output would be:


Tunnel Status                 online
Version (client/server)       1.3/1.2
Forwarding                    tcp:// ->
Forwarding                    tcp:// ->
Forwarding                    tcp:// ->

Of course you need to create the equivalent browsermob proxies on ports 9091, 9092 and 9093 see (browsermob proxy example for instructions how to do this) but your tunnel client and its mapping is independent from this and you can start tunnels to non yet created Browsermob proxies. This enables you to configure Browsermob proxies whenever you want and route one or many selenium tests through one proxy or many proxies.

Each Browsermob proxy can create a HAR file with performance data that you can use in your test suite to include performance testing at the same time you run functional testing.

The above endpoints like "" are accessible only by your Gridlastic selenium grid nodes. Use these endpoints in your selenium test suite as selenium proxies, see the Squid example for reference.