¿Qué es el proxy de iframe?

What is iframe proxy?

Porthole is a small Javascript library that makes it safe and easy to communicate with cross domain iFrames. Porthole relies on hidden iFrames (later referred to a as proxy) to exchange information. Learn more about Porthole.

Iframes Bring Security Risks. If you create an iframe, your site becomes vulnerable to cross-site attacks. You may get a submittable malicious web form, phishing your users’ personal data. A malicious user can run a plug-in.

IFrames are also used to show pop-under ads and to set cookies on your computer that survive even after you clear cookies from your browser. To prevent misuses of iFrames, you can block them from websites using the security parameters for Internet Explorer or Firefox, and with a plugin for Google Chrome.

If you are using an iframe to get around a properly developed site, then of course it is bad practice. However sometimes an iframe is acceptable. One of the main problems with an iframe has to do with bookmarks and navigation. If you are using it to simply embed a page inside your content, I think that is fine.

The iframe element is supported by all modern desktop and mobile browsers. However, some browsers don’t yet respond consistently to the three new HTML5 attributes for this element.

iFrame Blocking Methods You can protect your site from being iFramed by incorporating the correct HTTP response headers on your website. There are two different response headers that are used to block iFrame loading – X-Frame-Options and Content-Security-Policy.

How to enable iFrames in Internet Explorer?

1. Click on Tools, located on the browser toolbar.
2. Select Internet Options.
3. Select the Security tab.
4. Click on “Custom Level” button.
5. Select the Enable radial located under “Launching programs and files in an IFRAME”
6. Click OK.

iFrames tend to neither help nor hurt your search engine ranking. For this reason, it’s best to refrain from using iFrames on main pages that you want to rank high in search engine results. Instead, fill high-priority pages with useful, unique content and save iFrames for other pages.

Every iframe on a page will increase the memory used as well as other computing resources like your bandwidth. To avoid having your iframes slow down your pages, a good technique is to lazy load them (i.e., loading them only when they are required like when the user scrolls near them).

Use your own HTTPS-to-HTTP reverse proxy. If your use case is about a few, rarely changing URLs to embed into the iframe, you can simply set up a reverse proxy for this on your own server and configure it so that one https URL on your server maps to one http URL on the proxied server.

Note: While this solution may have worked in some browsers when it was written in 2014, it no longer works. Navigating or redirecting to an HTTP URL in an iframe embedded in an HTTPS page is not permitted by modern browsers, even if the frame started out with an HTTPS URL. The best solution I created is to simply use google as the ssl proxy…

Both domains are the same with the same protocol (HTTP) and port (80). For security reasons, the browser’s same origin policy restricts accessing iframe content from the main page and vice versa when the main page and iframe contents are loaded from different domains. All the above cases require access to edit the main page and the iframe page.

This article demonstrates how to override browser same-origin policy and communicate from main page to its iframe loaded with content from external domain using ARR and URL Rewrite.