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

Allowed HTTP URL assets getting blocked and/or not redirected. #14

Open
karlwilbur opened this issue Mar 12, 2014 · 1 comment
Open

Comments

@karlwilbur
Copy link

I have allowed "*.local:80/" for development. Works as expected. However, the assets (images, external JS, and external CSS) are not being redirected to HTTPS endpoints.

Link, script, and img elements (more specifically their href/src attributes) have no protocol defined ( i.e. "//example.com" vs "http://example.com") so they should be fetched using the same protocol as the parent window, in this case HTTP. I would expect that the extension detects those request and auto-redirects (Auto-Redirect is selected in preferences). However, in the Firebug Net tab, I see asset requests that never complete ...even to the allowed domain.

http://netdna.bootstrapcdn.com/bootstrap/3.1.0/css/bootstrap.min.css
http://cdnjs.cloudflare.com/ajax/libs/handlebars.js/1.3.0/handlebars.min.js
http://my.devapp.local/css/style.css

@karlwilbur
Copy link
Author

After re-reading the README, I see that I need to add "*" to the path to serve local assets. That part is working now.

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

No branches or pull requests

1 participant