For various very long reasons relating to working around CORS and embedding other 3rd party apps/CRMs, we're trying to run Finesse 11.6(1) ES01 at a customer behind a reverse proxy. Everything's set up and forwarding / URL rewriting. However, the call control banner fails to load, because of CORS. The call control banner looks like it attempts to load from the real Finesse server name, rather than the reverse proxy. And while the Finesse API endpoints support sending the needed Access-Control-Allow-Origin header, apparently the Finesse Tomcat instance serving the general /desktop (or /desktop/thirdparty) resources does not. So the call control banner is unable to load its HTML resources, causing a Load Failed message to be displayed.
Any ideas? Would ES04 fix this? Attached is the CORS error from Chrome's dev console.
Yeah, not sure Denise. Interestingly, this customer is running Finesse 10.5 and (seems to be) running successfully. Guess some things in 11.x broke that success.