281000 - Hostperm.1 incorrectly blocking subdomains

Status: RESOLVED FIXED

(Camino Graveyard :: General, defect)

Description

[Oakland Raiders]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b) Gecko/20050202 Camino/0.8+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b) Gecko/20050202 Camino/0.8+

I have the following in my hostperm.1 file:

host    image   2   advance.net

However the ads at oregonlive.com which are images from subdomains of
advance.net are still being downloaded.  For example:
http://ads6.udc.advance.net/RealMedia/ads/Creatives/OREGONLIVE/OR_HSSPORTS_07/hs_basketball.gif

still downloads and displays.

Reproducible: Always

Steps to Reproduce:
See Details



Expected Results:  
Images from advance.net or any subdomains should not be downloaded and displayed.

If I have something such as "doubleclick.net" in the hostperm.1 file I will
still get images such as 1x1 images from ads.doubleclick.net

Comment 1

[Mike Pinkerton (not reading bugmail)]

does this work in firefox?

Comment 2

[Oakland Raiders]

Yes. This works correctly in Firefox.  However, it is difficult to test (at
least as far as I have been able to think of - maybe access to my own website
would enable developing a better test case).

The URL previously given is simply the URL of a .gif that should not be loaded
WHEN LINKED TO FROM ANOTHER PAGE.  If you go to the URL directly, it will load
no matter what is in the hostperm.1 file.  (Maybe loading the image directly
bypasses the rules to follow in the hostperm.1 file).

But if you go to this URL:
http://www.oregonlive.com/news/oregonian/mike_francis/index.ssf?/base/news/1107522376244970.xml

About 75% of the time the ads that show up on the right side are hosted from a
subdomain of advance.net (sometimes ads.advance.net, ads1.advance.net or as the
previously posted URL shows even deeper, ads6.udc.advance.net).

In Firefox, if I have "advance.net" in the hostperm.1 file with an "image 2"
setting, it will not show any of the images from any of the subdomains of
advance.net

In Camino, using the 2/3 build now, I have to have the FULL server including
subdomains to block the images.  So if I have "advance.net" and
"ads.advance.net" in my hostperm.1 file it will still show images from
"ads6.udc.advance.net" or "ads1.advance.net".

Thank you.

Comment 3

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Attachment: Testcase (?)

I *think* this is a workable testcase for this bug.  The attached page has two
images, one from data.georgetown.edu and one from www.georgetown.edu.  

However, neither Cm 20050401 nor Fx (both 1.0.2 and a semi-recent nightly) seem
to be blocking images when I test this as a local file using
host	image	2	georgetown.edu

Comment 4

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

The results are the same when viewing the page online here at bugzilla; no one's
blocking anything.  Either my testcase is bad, the syntax is bad, or hostperm.1
is not blocking subdomains at all.  I'm not familiar with the feature at all, so
pointers appreciated.

Comment 5

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

No, it's not the testcase or the syntax.  It's trunk bug 288412, because
host	image	2	georgetown.edu
blocks both images on the testcase in Camino 0.8.3 and a Mar 27 Camino nightly.

This was perhaps the problem when you reported the bug in Feb, too.

Note that there are several bugs open against Core: Image Blocking dealing with
sneaky ways (javascript, redirect, etc.) that get around image blocking, so
check them, too, if the problem reappears on certain sites after bug 288412 is
fixed.

*** This bug has been marked as a duplicate of 288412 ***

Comment 6

[Oakland Raiders]

Attachment: Screenshot of my blocked servers

Here is a screenshot of my CEP blocked servers pane, showing advance.net is
indeed in there.

Comment 7

[Oakland Raiders]

Attachment: my hostperm.1 file

Here is my full hostperm.1 file.  You will see that "advance.net" is in there.

Comment 8

[Oakland Raiders]

I am not sure this is a duplicate.

I have added a couple attachments, my hostperm.1 file and a screenshot.  This bug still exists for me in 
the 4/7 optimized builds, and the 4/8 official build.

At http://www.oregonlive.com I still get images hosted from subdomains of advance.net

such as 
http://ads6.udc.advance.net/RealMedia/ads/Creatives/OREGONLIVE/PAYBYTOUCH01OR08/
nochecks_banner.gif

Thanks again for Camino.  Camino rocks!

Comment 9

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Indeed, something fishy is going on.

The Apr 8 build does not block anything when
host	image	2	georgetown.edu
is in hostperm.1

The Mar 27 build (before the regression in bug 288412) blocks both images with
host	image	2	georgetown.edu

*However*, the Mar 27 build also--incorrectly--blocks both images when I change
the line to
host	image	2	www.georgetown.edu
Camino 0.8.3 does this, too.
The Apr 08 nightly incorrectly fails to block the image from www.georgetown.edu

So actually there are two bugs: 
1) Recent Camino nightlies are not blocking anything at all
2) Camino 0.8.x and nightlies prior to 3-29(? at least through 3-27) are
incorrectly blocking multiple subdomains when given a specific subdomain entry,
e.g. www.domain_name.tld

Either Camino is not picking something up properly from the Core feature, or the
Core feature is not sending something that Camino needs.

Reopening and confirming.

Comment 10

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Torben notes in the MZ forums (there have been several threads on these problems
since 0.9a1 came out) that this might be related to bug 240070. 

It's also possible the fix for bug 288412 didn't include changes needed to fix
Camino, because some blocking *was working* in a nightly from before the
regression that bug fixed.

Point 1 in my comment 9 is a regression from 0.8.x; point 2 is an additional
problem common to CaminoTrunk and Branch.

Can someone who knows/understands more than me do a little investigation?

Comment 11

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Attachment: Updated testcase

data.georgetown.edu was retired since I last checked this bug; I've replaced
that image with one from ccas.georgetown.edu.  Wherever you saw data...
earlier, see ccas... now :-)

Comment 12

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

See also bug 299356.

Comment 13

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

OK, reorienting this bug now that bug 299356 is fixed.  Fixing bug 299356 fixed
hostperm.1 *not* blocking images from domains or subdomains.
host	image	2	georgetown.edu
blocks both images from the "Updated testcase" above.

The problem that remains, though, is point 2 from comment 9, i.e., that if I put
host	image	2	www.georgetown.edu
in my hostperm.1, *both* images in the "Updated testcase" are blocked rather
than just the image from www.georgetown.edu.  Deer Park Alpha 2 correctly blocks
only the image from www.georgetown.edu in that case.

This remaining bit is not a regression from 0.8, so removing the regression
keyword and the ? flag and targeting for 1.0 for now.

Comment 14

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Well, this is working now (comment 13); not sure what was up the other day.

Marking FIXED because I think bug 299356 fixed this, momentary glitch in comment
13 aside.  It certainly fixed the original scope of the bug.