Using the Proxy action in the SPEED tab you can reverse-proxy to any IP and Port, locally or on an external server.
Reverse-proxy is now achievable for applications that use NodeJS Server or Docker that are not yet supported by ClusterCS.
In order to enable the SPEED Proxy rule, head over to the SPEED section.
You can use the example below to create your new rule:
Additional conditions can be added to redirect only certain pages from the site.
path begin_with /example
After you add the rules and temper the values as needed, proceed to Add Rule & Apply Configuration.
The rule will automatically become Enabled and it will shortly take effect on your server.
Destination IP: The IP of the local or external server on which the reverse-proxy happens.
Destination Port: The Port of the local or external server on which the reverse-proxy happens.
MaxConn: This parameter specifies the maximal number of concurrent connections that will be sent to this server.
MaxQueue: This parameter specifies the maximal number of connections which will wait in the queue for this server.
Send Proxy: Whether or not to enable proxy protocol HAproxy will send the data through the PROXY protocol without needing additional headers for real user IP data.