Closed Bug 202608 Opened 21 years ago Closed 21 years ago

"unblock images from server" should override "Accept images from orig server only"

Categories

(Core :: Graphics: Image Blocking, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: steve, Assigned: security-bugs)

References

()

Details

(Whiteboard: third-party)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030401
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030401

I have "Accept images from the originating server only" set.  Many web sites put
images on "images.domain.com" instead of "www.domain.com".  One example is
www.weather.com; I tried allowing "images.weather.com" by right-clicking on an
image and selecting "unblock images from this server", but it still didn't allow
the image.  I guess this makes sense after thinking about it (after all, the
image *still* isn't from the originating server) but it's not intuitive.

Reproducible: Always

Steps to Reproduce:
1. Set "Accept images from orig server only"
2. View www.weather.com
3. Right-click where an image should be, select "Unblock images from this server"


Actual Results:  
Image still doesn't display

Expected Results:  
Display the image.  Setting "Unblock image..." should override "Accept images
from orig server"
dwitte: you might want to fix this too while looking at whitelisting.
yeah, this sucks. the current whitelisting patch will already fix it.

whitelisting will override any default settings, _except_ for block-from-mailnews.

marking dependent on bug 184059.
Depends on: 184059
*** Bug 141307 has been marked as a duplicate of this bug. ***
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Can't unblock images on a per-site basis → "unblock images from server" should override "Accept images from orig server only"
Whiteboard: third-party
fixed via bug 184059, someone wanna confirm?
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.