Private Proxies

The Private Proxy App lets you forward all Session traffix through a private proxy server, giving you control over the IP address used for requests. Both HTTPS and SOCKS5 proxies are supported.

Private Proxies are useful for a variety of Use Cases, including:

• Compliance – Ensure compliance with data protection regulations by routing traffic through a specific geographic location.
• Access control – Restrict access to your application by allowing traffic only from specific IP addresses.
• Bypass restrictions – Access content that is restricted based on geographic location or requires a residential IP address.
• Security – Protect your identity and location by routing your traffic through a private proxy server.
• Anonymity – Hide your IP address and location from the websites you visit.
• Performance – Improve performance by using a proxy server that is closer to the target website.
• Testing – Test your application from different geographic locations or IP addresses.

Private proxies are configured as a JSON array. Each proxy is represented as a string in the following format:

<protocol>://<username>:<password>@<host>:<port>

Example

["socks5://username1:password1@host1:port1", "socks5://username2:password2@host2:port2"]

When multiple proxies are provided, Webfuse uses a round-robin algorithm to assign sessions across the proxies. This means each session will be handled by a different proxy, but all requests within a session will use the same proxy.

You can enforce all traffic to go through private proxies by enabling the Enforce private proxies toggle in the Private Proxies App.

Note

If you add both a residential proxy and a private proxy, the private proxy will always take precedence.

Getting Started

🎁Webfuse App

Enable the Private Proxies App in the Session Editor to make requests to the origin server using your own proxy servers.