Skip to main content





Error: unexpected link in application (changes from HTTPS to HTTP or shows an internal server name)

  • Edit
    Collaborate with us
    Edit this page on GitHub
  • Symptoms

    In an application built with the OutSystems Platform, links don't behave consistently. Most links work as expected, and you are able to navigate the application through those.

    However, some of the links in the application misbehave. Some of the possible misbehaviors observed:

    Typically, this type of problem happens in the production environment but not in other (earlier) staging environments (development, test, etc).

    Additionally, in the affected environment(s), the problem will typically not happen if accessing the application in a browser running locally in the server, by accessing with .


    This type of problems typically happens when the environment has a network layer (a load balancer or a reverse proxy) between the end-user and the OutSystems Platform. In this scenario, if these layers are not properly configured, it may be sending wrong information to the platform.

    OutSystems Platform usually generates "relative" links: links to other pages are inserted in the code relative to the current path. Examples:

    • ./NextScreen.aspx

    • ./img/logo.png

    • /MyWidgets/SomeFancyJavascript.js

    In some situations, however, the platform needs to generate absolute URL. In those situations, URL are generated based on the information received in the front-end. Particularly, the following are inferred from the request that arrives at the application server:

    • The protocol (HTTP or HTTPS)

    • The hostname (via the Host header in the HTTP request).

    If a network layer is not properly configured to pass this information correctly to the target server, the misbehaviors indicated under Symptoms may occur.


    Solving this problem is done as indicated below.

    a) HTTPS/HTTP issue

    Either one of the following:

    • doing a full pass-through of protocol (meaning: requests initiated by the end-user as HTTPS need to be delivered to the OutSystems application server as HTTPS; same thing for HTTP)

    • Configuring the platform for properly setting up the HTTPS to HTTP offload.

    b) wrong hostname

    Configure the network layer to pass the original host header all the way through until the application server.


    Applies to OutSystems Platform, all stacks.

    Applies to version 8.0.x.x and above (last reviewed under 9.1.600.0).