(In reply to Christoph Kerschbaumer [:ckerschb] from comment #1) > Hey Alexandru, thanks for filing. FWIW, Firefox is not going to do auto upgrading which would fix broken websites that are `not using` https subresources in https contexts (hence `Bug 1703847: Disable Mixed Content Auto-upgrading in Nightly (and in general)`. > > In this particular case the Page CSP blocked the load: > `Content Security Policy: Blocking insecure request ‘http://articles-images.sftcdn.net/wp-content/uploads/sites/2/2014/10/firefox-android-header-664x374.png’.` > > The best way to fix the website is to update the image-request from `http:` to `https:`. Please note that Chrome is shipping mixed-content-auto upgrading and therefore this works in Chrome. However, it's a website problem, not a browser problem. Hello and thank you for the explanation, Christoph. I think it's good to close this as Invalid then based on the above.
Bug 1750195 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Christoph Kerschbaumer [:ckerschb] from comment #1) > Hey Alexandru, thanks for filing. FWIW, Firefox is not going to do auto upgrading which would fix broken websites that are `not using` https subresources in https contexts (hence `Bug 1703847: Disable Mixed Content Auto-upgrading in Nightly (and in general)`. > > In this particular case the Page CSP blocked the load: > `Content Security Policy: Blocking insecure request ‘http://articles-images.sftcdn.net/wp-content/uploads/sites/2/2014/10/firefox-android-header-664x374.png’.` > > The best way to fix the website is to update the image-request from `http:` to `https:`. Please note that Chrome is shipping mixed-content-auto upgrading and therefore this works in Chrome. However, it's a website problem, not a browser problem. Hello and thank you for the explanation, Christoph. I think it's good to close this as Invalid based on the above.