I have a desktop app running on macOS that outputs an HTML file that can be launched and viewed by the default browser. Inside this HTML file is an iFrame that holds a link to a URL. When that URL is plain (no port number) it works fine e.g. http://click.bulkemailapp.com
In the case of http://click.bulkemailapp.com:4000, the WebApp should run a ShowURL of an error page due to the lack of parameters, and runs fine outside the iFrame, but fails inside the iFrame.
Any clues on why a port number should block an iFrame from displaying?
Browser security settings, cross-site scripting protection.
I’m not sure if there’s something you can do with the HTML to change X-Frame-Options or if that’s a browser setting.
(Google might know, though.)
Thanks Tim. You’ve given a place to start looking.
Even if I set the URL to an entirely different server outside my intranet (but with a port number) it doesn’t display, so I don’t think it’s a ‘same PC’ style issue.