1000TurquoisePogs

I suggest that the URL used in the browser has a different host:port combination than the first entry of zowe.externalDomains + zowe.externalPort That's what is used here https://github.com/zowe/api-layer/blob/v3.x.x/api-catalog-package/src/main/resources/plugin/pluginDefinition.json#L8C19-L8C74 And if...

@Martin-Zeithaml it looks like the problem occurs as a result of 2 things 1) the above discussion about how the desktop chooses which URL to reach given what the pluginDefinition...

and a third thing... if I access app-server from hostname:port, it tries to access api-catalog from hostname:port/ui/v1/api-catalog That actually seems like the right behavior! ... and then APIML responds with...

I have isolated the cause to a catalog behavior change that can be fixed by changing its pluginDefinition.json here https://github.com/zowe/api-layer/pull/4007