locked
Forward original GET URL in UAG RRS feed

  • Question

  • Hi,

    My customer has published a web application with UAG. This application needs to know the original URL provided at the client side, the HTTP GET if you will.

    UAG translates this to the internal web server address but the internal web application needs to receive the original GET URL to be able to fulfill its purpose.

    Is there a way in UAG to make this happen?

    Thank you!

    Daniel

    Monday, December 2, 2013 1:04 PM

Answers

  • Hi Daniel,

    Do you use the "Portal Hostname" template to publish your applications or the "Application Specific hostname" ?

    If you are using the "Portal hostname" then you cannot control the host header sent to the backend, however it should be the internal one (so the application should see it correctly, so I am not sure what is the problem).

    If you are using "application specific hostname" template, then if you do not replace the host header, the application will see the external application hostname, but you can overwrite it as per my first answer.

    You can do that for all applications, as this setting is per application and not per trunk...

    Ophir.

    Tuesday, December 3, 2013 8:37 AM

All replies

  • Hi Daniel,

    If you are using the "Application Specific Hostname" template to publish your application, you can overwrite the HOST header sent to the backend using the option "Replace the host header with the following" under the "Web Servers" tab in the application's properties: 

    Replace host header

    Hope this helps,

    Ophir.

    Tuesday, December 3, 2013 6:45 AM
  • Thank you Ophir!

    We have multiple applications on the trunk. Can this method be used with multiple applications on the same trunk and when the trunk has the same public host name?

    Daniel

    Tuesday, December 3, 2013 7:28 AM
  • Hi Daniel,

    Do you use the "Portal Hostname" template to publish your applications or the "Application Specific hostname" ?

    If you are using the "Portal hostname" then you cannot control the host header sent to the backend, however it should be the internal one (so the application should see it correctly, so I am not sure what is the problem).

    If you are using "application specific hostname" template, then if you do not replace the host header, the application will see the external application hostname, but you can overwrite it as per my first answer.

    You can do that for all applications, as this setting is per application and not per trunk...

    Ophir.

    Tuesday, December 3, 2013 8:37 AM
  • Thank you, just as I thought then. We are using the Portal Hostname template because we have multiple applications on the trunk sharing the hostname.

    The application requires the original URL because it stores it in its database. This information is later used by the application to provide links to users and the UAG signed ones wont work.

    We will try a different approach.

    Again, thank you for your help!

    Daniel

    Wednesday, December 4, 2013 3:10 PM