Search Engine: Elastic

Article ID: 127674, created on Dec 2, 2015, last review on Dec 2, 2015

  • Applies to:
  • Operations Automation


APS Custom UI hangs. In Firebug or Web Console, we can see that failed request uses internal IP of UI node.


Application UI accesses a resource via link, for example:


APS Controller replies as follows:

  HTTP/1.1 302 Found

  Location: /aps/2/resources/4bdd9c09-0e10-48b6-802f-6980d67568a4

It returns relative path, but UI proxy inserts an internal IP of UI node, for example:

  HTTP/1.1 302 Found


Browser is trying this url and hangs.


Bug will be fixed in OA 6.0.7 for new brands.

For existing brands, add this rule in .branding_htaccess on the branding node:

  Header edit Location "(^http[s]?://)([a-zA-Z0-9\.\-]+)" ""

.branding_htaccess config can be found at the branding node by the following path:

/var/www/vhosts/2/{brand webspace id}/webspace/httpsdocs/.branding_htaccess


/var/www/vhosts/2/{brand webspace id}/webspace/httpsdocs/{hostname}/.branding_htaccess

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF