Closed
Bug 1094334
Opened 11 years ago
Closed 10 years ago
Mixed Content Blocking prevents HTTP sites to load
Categories
(Webtools Graveyard :: Pontoon, defect, P5)
Webtools Graveyard
Pontoon
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: mathjazz, Unassigned)
Details
Pontoon is hosted via HTTPS. Modern browsers prevent HTTP content from loading inside iframe. That means websites accessible only through HTTP will not load inside Pontoon, unless user explicitly tells browser to do so.
Quick fix would be to point user to the browser button for disabling blocking. But that's just a partial fix.
What other options do we have? Shall we also allow Pontoon to run on HTTP?
| Reporter | ||
Updated•11 years ago
|
Mentor: m
| Reporter | ||
Updated•10 years ago
|
Priority: -- → P5
>Shall we also allow Pontoon to run on HTTP?
Do you mean pontoon.mozilla.org or Pontoon the source code?
| Reporter | ||
Comment 2•10 years ago
|
||
I mean the page itself (pontoon.mozilla.org). If you want to localize in-page, Pontoon needs to load the website in an iframe. And that's problematic if Pontoon and the website use different protocols (HTTPS vs HTTP).
| Reporter | ||
Updated•10 years ago
|
Mentor: m
| Reporter | ||
Comment 3•10 years ago
|
||
Now that HTTPS is not only a standard at Mozilla but also free and easy to implement in general, I've made it a requirement:
https://developer.mozilla.org/en-US/docs/Mozilla/Implementing_Pontoon_in_a_Mozilla_website#B._Enable_Pontoon_on_your_site
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Comment 4•10 years ago
|
||
I think it's the right decision. I guess it's easier to implement HTTPS by an author of apps than build some workaround that could be potentially unsafe.
Updated•4 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•