HTTP URI call

Okay, so not a portal. How do you have it all configured now?

An APM portal is essentially a content rewrite mechanism. You access the portal with a single host name, and the internal applications, their URLs and all references are encoded into the URI (ex. https://myportal.example.com/f5-w-123234329080u0r098ewrduf-0is9dsn...). The rewrite engine rewrites these encoded values incoming and outgoing and is more or less agnostic to the internal HTTP protocol used (80 or 443). Portal mode is definitely an option, but it does incur a per-user connection licensing limitation.

That said, and having established that you're not using portal mode, there are several factors that must be considered to fully understand what's going on in your environment.

Can you first provide a client side capture of the traffic, preferably something like Fiddler, that can show what the client is seeing in the responses and what it's trying to reach. Depending on the complexity of the environment, the solution may require something as simple as a STREAM profile, or as complex as an APM portal.