locked
UAG translation of published application URL RRS feed

  • Question

  • Please ,  help me with published web application on UAG trunk.
    I installed UAG service on domain y.z.
    Next I configured one trunk 'uagportal'. On this trunk I published the web application which is deployed on other domain  x.c.
    The aplication's real URL is  http://t2a.x.c:9080/csuadmin and its public URL is http://csu.y.z/csuadmin
    So the UAG has to translate not only URL's hostname but also the port. If URLs to the web aplication parts are included in the response body, the translation works correctly.
    The problem appears when application sends the http redirection response to the client.
    The redirection mechanism use http response code 302 and sets new URL in the location header.
    The location header in the browser  contains mixed-up URL http://csu.x.c:9080/csuadmin . Hostname is translated ok, but not the port.
    So the browser redirects to uag trunk on bad port and it naturally crashes.
    I'm using Internet Explorer 6 and 8 as browsers. In both cases the result is the same.  
    It seems the UAG has problem with URL translation in some http headers.
    What could be the problem? Is there something I miss in UAG's URL translation configuration ?

    Wednesday, September 22, 2010 3:05 PM

Answers

  • Applications that span multiple servers and ports are common, Jarda. What you need to do is edit the properties of your application (I assume you used the "other web app (Portal hostname)", right?) and in the Web Servers tab, add all internal servers that are relevant to the list of servers, and all the relevant ports to the HTTP or HTTPS ports (depending on how the internal app is configured), seperated by commas. Then, activate the configuration, and all should work fine.

     


    Ben Ari
    Microsoft CSS UAG/IAG Support
    Sammamish, WA
    • Marked as answer by Erez Benari Wednesday, September 22, 2010 7:14 PM
    Wednesday, September 22, 2010 7:14 PM

All replies

  • Applications that span multiple servers and ports are common, Jarda. What you need to do is edit the properties of your application (I assume you used the "other web app (Portal hostname)", right?) and in the Web Servers tab, add all internal servers that are relevant to the list of servers, and all the relevant ports to the HTTP or HTTPS ports (depending on how the internal app is configured), seperated by commas. Then, activate the configuration, and all should work fine.

     


    Ben Ari
    Microsoft CSS UAG/IAG Support
    Sammamish, WA
    • Marked as answer by Erez Benari Wednesday, September 22, 2010 7:14 PM
    Wednesday, September 22, 2010 7:14 PM
  • Thank you for your answer but problem is a little different.
    Application Internal server has only one url with one port- http://t2a.x.c:9080/csuadmin .
    Its published name should be http://csu.y.z/csuadmin   because I configured the trunk on port 80.
    But the browser gets the responses with URLs http://csu.y.z/csuadmin (in the html body) and sometimes http://csu.y.z:9080/csuadmin (in the location header) from the UAG.
    How can i add multiple ports to application public url ? Is there some possibility to set the trunk listening on multiple ports ?
    Thursday, September 23, 2010 11:11 AM
  • Hi Amigo. For UAG to rewrite the URLs it looks inside text content type (html, text, javascript..) searching for tags that implies a "link". It seems that the HAT is not finding the string http://csu.y.z:9080 and though it is not being rewritten. Try to identify with an HTTP debugger in the client's station where the broken links are being sent (I recommend Fiddler. It´s free).

    Regards


    // Raúl - I love this game
    Thursday, September 23, 2010 11:51 AM
  • My web application generates internaly server-relative urls like this /csuadmin/* in the responses or absolute urls http://t2b.x.c:9080/csuadmin/*  .
    HAT has to translate this to http://csu.y.z/csuadmin/ * . Usually it works ok.
    The problem is only when my application include url in location http header (it is allowed in url redirecting in the http protocol)
    Why UAG translates adds another port instead of its listener port ?

    When i go directly to my application(without UAG), redirecting response headers are:
    HTTP/1.1 302 Found
    Location: http://t2b.x.c:9080/csuadmin/layout.html
    Content-Language: sk-SK
    Content-Length: 0
    Set-Cookie: JSESSIONID=0000BuxcKnkCifFCbQZY-_dpVu4:-1; Path=/
    Date: Thu, 23 Sep 2010 12:57:31 GMT
    Server: WebSphere Application Server/6.1
    Expires: Thu, 01 Dec 1994 16:00:00 GMT
    Cache-Control: no-cache="set-cookie, set-cookie2"

    If i go to my app. via UAG, here are response headers i get in browser:
    HTTP/1.1 302 Found
    Cache-Control: no-cache="set-cookie, set-cookie2"
    Content-Length: 0
    Content-Language: sk-SK
    Expires: Thu, 01 Dec 1994 16:00:00 GMT
    Location: http://csu.y.z:9080/csuadmin/layout.html
    Server: Microsoft-IIS/7.5
    Set-Cookie: JSESSIONID=0000l5R74KaKCrps0qhLOCMzVfn:-1; Path=/
    Server: Microsoft-IIS/6.0
    Set-cookie: NLSessionCuagportal=Ld5VnG6Q72ZVopCyNtmpIJni4FunmDNIc9Z9uX/y3dxjrduVrQRCUIVNvtyJSXWh07kDErk/cbPpMKow/AICVsDNk3NFwwMNTTppP+DhC+dbdlP4ZqX81rRJJ4AjUhpk;path=/;domain=.vszp.test
    X-Powered-By: ASP.NET
    Date: Thu, 23 Sep 2010 13:03:11 GMT

     

    Thursday, September 23, 2010 1:07 PM
  • Could by the problem caused by non-standard port I am using on internal application url.
    I found this feature in http://technet.microsoft.com/en-us/library/dd772157.aspx#BKMKClient :
      "When creating trunks and publishing applications, using non-standard ports is not supported; servers must listen on port 80 for HTTP, and port 443 for HTTPS."

    Or is this match only for public app. url ?

     

     

    Monday, September 27, 2010 2:09 PM