Portal Access Application URI - ERR_EMPTY_RESPONSE

What you’re running into isn’t an F5 misconfig; it’s a browser security policy. Portal Access works by rendering the target app inside a frame. The error you saw in DevTools – X-Frame-Options: DENY – instructs the browser not to render the page in a frame. That header is being honoured, so the browser drops the response, and you end up with ERR_EMPTY_RESPONSE.

Unfortunately, Portal Access cannot override this. Even if you try to strip the header in a Portal Access profile, most modern apps also set Content-Security-Policy: frame-ancestors, which will block framing.

• Contact the app owners to update the headers (X-Frame-Options: SAMEORIGIN or allow specific frame-ancestors in CSP to include your F5/Portal domain).
• If you don’t control the site, Portal Access isn’t viable — use Network Access (VPN) or App Tunnel so the app can be reached directly without being framed.