Closed
Bug 1223785
Opened 9 years ago
Closed 9 years ago
Tracking protection blocks images from https://fotki.yandex.ru/
Categories
(Core :: DOM: Security, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: 08xjcec48, Unassigned)
References
(Blocks 1 open bug, )
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:42.0) Gecko/20100101 Firefox/42.0
Build ID: 20151029151421
Steps to reproduce:
Enable tracking protection and open http://alexhitrov.livejournal.com/392831.html
Actual results:
The pictures from this blog post aren't displayed. They are hosted on a valid image hosting service: https://fotki.yandex.ru/
Expected results:
Firefox shouldn't block pictures from https://fotki.yandex.ru/
Updated•9 years ago
|
Comment 1•9 years ago
|
||
REPRODUCIBLE with SeaMonkey German 2.39 final Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0 from official download area) Gecko/20100101 Firefox/42.0 Build 20151103191810 (Classic Theme) on German WIN7 64bit:
1. With all Tracking protection disabled visit
<http://alexhitrov.livejournal.com/392831.html>
» Background picture <http://img-fotki.yandex.ru/get/5413/124389325.24/0_76fae_8ac78262_XXXL.jpg> will be shown.
2. Enable all Tracking Protection "Block" in 'Edit → Preferences → Privacy'
3. With rightclick from here open <http://alexhitrov.livejournal.com/392831.html>
in a new TAB
» Now picture at the top is missing.
Additional info:
a) <https://www.mywot.com/en/scorecard/img-fotki.yandex.ru?utm_source=addon&utm_content=rw-viewsc> seems to show good reputation for <img-fotki.yandex.ru>,
so I wonder why SM / Mozilla-FF might block that page.
Somebody has fixed this problem without updating this issue.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Comment 3•9 years ago
|
||
(In reply to budaeuforico+mozilla from comment #2)
> Somebody has fixed this problem
For what FF Version?
43.0.3 64-bit on Windows. Are the images still blocked for you?
Comment 5•9 years ago
|
||
For me no longer reproducible with Version from Comment 1, so it seems that something at the Website has changed.
Updated•6 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•