Closed Bug 69515 Opened 24 years ago Closed 23 years ago

file:// doesn't support Image blocking from other-sites not working

Categories

(Core :: Graphics: Image Blocking, defect)

Product:
Core
Component:
Graphics: Image Blocking
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 51266
Milestone:
Future

People

(Reporter: tarmoj, Assigned: morse)

References

(
URL
)

Details

Even with the test file below, option "Accect images that come from the originating server only" won't work. ---test.html--- <HTML> <HEAD> <TITLE>Test page</TITLE> </HEAD> <BODY> <H1>Title</H1> Image 1 (originating server): <IMG src="./test.jpg"> <P> Image 2 (non-originating server): <IMG src="http://www.mozilla.org/images/mozilla-banner.gif"> </BODY> </HTML> ---test.html--- Reproducible: Always Steps to Reproduce: 1. Copy test.html (above) to some directory. 2. Copy random image as test.jpg to the same directory. 3. Open test.html with mozilla. Both images are loaded when "Accect images that come from the originating server only" is selected. Expected Results: Image from mozilla.org shouldn't be loaded.
I see this on today's linux CVS build.
Status: UNCONFIRMED → NEW
Component: Browser-General → Networking
Ever confirmed: true
Keywords: regression
Um.. it actually only happens to me when I use a file:// url to fetch test.html. For http:// urls everything seems to be OK.
Image blocking currently only works on HTTP requests. I belief that this is a dup of bug 64068.
bug 64068 is, as morse says, a imagelib bug. This one would be a cookie bug... tarmoj@iobox.com, are you seeing the problem using the http:// protocol to view your page? Or just using file://?
No problems with http:// , only with file:// . But if IFRAME is used instead of IMG, image will be downloaded even with http://.
i'm sure this is intentional and i suggest wontfix
Assignee: asa → dougt
Component: Networking → Networking: FTP
Keywords: regression
QA Contact: doronr → tever
Summary: Image blocking from other-sites not working → file:// doesn't support Image blocking from other-sites not working
Whiteboard: WONTFIX?
Target Milestone: --- → Future
is this actually a dupe of bug 51266? either way, this definitely should not be wontfix - blocking an image shouldn't be dependent on the location calling that image.
I think that most users select "Accept images that come from the originating server only" in order to get rid of advertisements etc. However, this selection seems to have no effect currently, since IFRAME is so widely used. I wish there could be a way to prevent downloading all "non-originating server images", whether their are defined by IMG, IFRAME, or any else HTML element. Best regards, Jukka.
img blocking is steve, right?
Assignee: dougt → morse
QA Contact: tever → benc
-> file (oops to ftp...) Should eventually go to image blocking (how do you determin the "server"?. file: URLs currently do not validate the host field (e.g. file://host/path/file) (see bug 70871).
Component: Networking: FTP → Networking: File
->Image blocking (via browser general). Can someone send this to the right place?
Assignee: morse → asa
Component: Networking: File → Browser-General
QA Contact: benc → doronr
->morse code
Assignee: asa → morse
Component: Browser-General → Cookies
QA Contact: doronr → tever
Status: NEW → ASSIGNED
Dupe of bug 51266?
*** This bug has been marked as a duplicate of 51266 ***
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Component: Cookies → Image Blocking
QA Contact: tever → nobody
Whiteboard: WONTFIX?
You need to log in before you can comment on or make changes to this bug.