ROOT_URL_PREFIX

You have successfully configured your Genero application to run via Genero Application Server in your development environment, but then you hit an error when trying to deploy to a customers environment.  OR you have a good configuration in your customers environment and then a change is made in the customers environment such as adding a Reverse Proxy or a Load Balancer and you hit an error.

When you inspect the web pages and various log files, you might see that a file was being requested via http instead of https and via a private server name rather than a public facing URL.  For instance, you might see “http://private-server-name/gas/ua/w/gbc/index.html” was attempted to be accessed when “https://public-server-name/gas/ua/r/app_name” is your public facing URL

When you enter a URL into a Web Browser, the Web Server that processes this request may send this to another server for processing.  The use of a  Reverse Proxy or Load Balancer are the two classic cases where this might occur.  The end-user is unaware that this step occurs, they know they have typed a URL into a browser, but they don’t know and don’t need to know what server is ultimately processing the request.  Similarly this server doing the processing does not necessarily know where the actual request came from, and so if it generates a URL it might generate this URL relative to itself rather than a URL that is suitable for consumption by the public facing web server.