Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

enforce SSL for frame/iframe #103

Open
GoogleCodeExporter opened this issue Mar 21, 2015 · 3 comments
Open

enforce SSL for frame/iframe #103

GoogleCodeExporter opened this issue Mar 21, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

(Sorry, my english is not very good...)

What steps will reproduce the problem?
1. Open an SSL page containing a non SSL iframe.
2. The iframe is not loaded because it's insecure content (really), even if the 
concerned domaine is in the enforced list.

What is the expected output? What do you see instead?
The expected output should be to load the iframe with https, by rewriting the 
source url in the frame/iframe tag

What version of the product are you using? On what operating system?
KB SSL Enforcer 2.0.3 / Chromium 30.0.1599.101 / Mac OS-X 10.6.8

Please provide any additional information below.
I've made a simple exemple here : 
https://assistance-multimedia.fr/cyril/divers/iframe_http.php
I now parsing all the pages is not good for performances, but maybe you can ad 
an option to enable this.

Original issue reported on code.google.com by [email protected] on 6 Jan 2014 at 1:03

@GoogleCodeExporter
Copy link
Author

Without having dived too much in to it yet, it might be that Chrome is blocking 
the "insecure content", before the extension is able to get a hold of the 
request and "saving" the content from being loaded insecurely.

If that is true, there's not much hope for redirecting that iframe, unless it's 
either coming from an insecure page allowed to make those insecure requests we 
can change. Or if we scrape the page and look for iframes with insecure content 
that could be redirected. The last option is probably not a good idea though.

Original comment by [email protected] on 18 Feb 2014 at 9:17

@GoogleCodeExporter
Copy link
Author

This problem seems to have been reported in issue chromium:122548.

Original comment by [email protected] on 25 Feb 2014 at 8:15

  • Changed state: AwaitingUpstreamBug

@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 30 Jul 2014 at 7:49

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant