HTTP and HTTPS iframe

It is generally bad practice to embed an iframe with content served over HTTPS within a page served over plain HTTP (or mix content). The reason for this is that there’s no good way for the user to check they’re using the HTTPS site they intend (unless the user really wants to check the source of the page).

An attacker could very well replace the content you serve like this:

<iframe src="https://your.legitimate.example/loginframe" />


<iframe src="" />

or even:

<iframe src="" />

This is very hard to detect for the user, and defeats the security measure you’re trying to put in place by enabling login via HTTPS.

Leave a Comment