Closed
Bug 877736
Opened 11 years ago
Closed 8 years ago
https://www.samsung.com/ generates errors because of mixed content blocking
Categories
(Web Compatibility :: Site Reports, defect)
Web Compatibility
Site Reports
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: mwobensmith, Unassigned)
References
()
Details
(Whiteboard: [mcb-chrome][mcb-ie])
Mixed content blocking is a feature that prevents insecure elements on secure pages from loading. In Firefox 23, this feature will default to blocking "active" insecure content, which may break some web sites. More information on Firefox's Mixed Content Blocker is below: http://blog.mozilla.org/tanvi/2013/04/10/mixed-content-blocking-enabled-in-firefox-23/ The security feature is currently breaking the HTTPS version of www.samsung.com. It also appears to be causing errors in Chrome 26 and IE10. The home page itself for www.samsung.com appears correct, but may not function correctly, as some active HTTP resources were blocked: Blocked loading mixed active content "http://m.samsung.com/us/api/popular.json" @ https://www.samsung.com/us/scripts/framework-min.js?render=all:1 Blocked loading mixed active content "http://shop.us.samsung.com/store/samsung/DisplayDRCartSummary/Version.2/output.json?callback=jQuery172040041098969851796_1368748780583&jsonp=callbackDRCartSummary&_=1368748780934" @ https://www.samsung.com/us/scripts/jquery-1.7.2.min.js:4 Blocked loading mixed active content "http://platform.twitter.com/widgets.js?_=1368748780965" @ https://www.samsung.com/us/scripts/jquery-1.7.2.min.js:4
Updated•11 years ago
|
Whiteboard: [mcb-chrome][mcb-ie]
Updated•10 years ago
|
Component: English US → Desktop
Comment 1•8 years ago
|
||
Still some mixed content when forcing https on sub pages.
Comment 2•8 years ago
|
||
On http://www.samsung.com/jp/home/ no mcb On http://www.samsung.com/us/ no mcb Closing as WORKSFORME
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
Updated•5 years ago
|
Product: Tech Evangelism → Web Compatibility
You need to log in
before you can comment on or make changes to this bug.
Description
•