Skip to end of metadata
Go to start of metadata

Port mapping

If the Servoy Application Server is installed behind a firewall and Servoy Clients need to access the Servoy Application Server through the firewall, some configuration is required.

It can be that the ports over which the Servoy Application Server communicates are blocked by the firewall. By default, the Servoy Application Server uses port 8080 for HTTP traffic and port 1099 for RMI traffic. Both ports need to be opened on the firewall and forwarded to the Servoy Application Server.

Opening the correct ports on the firewall and/or setting up the forwarding needs to be done by the the person administrating the firewall.

Its also possible to configure the Servoy Application Server to run on different ports and/or to tunnel the RMI traffic over the HTTP port.

For detailed information on configuring the different ports on the Servoy Application Server, see Network Related Settings.

Forwarding of Request headers

In some situations, Servoy needs to generate URLs that are referring to its own external location, as used by the client browser. When a firewall is not set-up correctly, Application Server does not know how generate the correct URL. This is mainly a problem with the Servoy Webclient.

The problem may occur when the firewall is creating a new internal request to the Application server for each external request and in the internal request some headers are missing.

If the firewall has an option to set the 'Pass Host Header', this should be turned on.

If this is not possible, Servoy will inspect requests for headers X-Forwarded-Host, X-Forwarded-Proto, X-Forwarded-Scheme and Forwarded.

Check your firewall configuration manual to enable these headers.

 

 

  • No labels