Without knowing how your appliaction is supposed to work, it's very hard to give you an answer, but it could be that the application needs to be modified so that the address of the VIP instead of the real address of the server is returned on the link to the report.
Anyway, to really see what is going on, I would recommend you to get traffic captures on both sides of the ACE while doing a test connection. Since these captures will be encrypted, you can either use the SSL private key from the ACE and server to decrypt the connections, or, assuming your applciation supports it, disabling the SSL part of the configuration during the test (to get the captures in plain HTTP)
thank you for the answer. I finally got the answer from the programmers yesterday. There really were problems with fixed (not relative) references in the code. Since corrections have been made, everything works fine.
I was not sure, if there are not some obstacles (in ACE) when opening new connection (popup window). Now I see the ACE config was correct.
Here are some commonly asked questions and answers to help with your adoption of Cisco ACI solution. Subscribe to this post to stay up-to-date with the latest Q&A and recommended Ask the Experts (ATXs) sessions to attend.
Join us for this #CiscoChat focused on how you can unlock the power of your hybrid cloud infrastructure. A panel of Cisco and industry experts will discuss Cisco’s hybrid cloud strategy and dive deep into the future-ready infrastructure behind it all.