Closed
Bug 73392
Opened 23 years ago
Closed 23 years ago
Ad-blocking hosts file prevents page load (DNS serialized issue?)
Categories
(Core :: Networking: HTTP, defect, P3)
Tracking
()
VERIFIED
FIXED
mozilla0.9.2
People
(Reporter: motrei, Assigned: darin.moz)
References
()
Details
(Keywords: dataloss, Whiteboard: r=gagan, sr=dougt, a=asa)
Attachments
(2 files)
344.30 KB,
text/plain
|
Details | |
651 bytes,
patch
|
Details | Diff | Splinter Review |
If one uses an ad-blocking hosts file such as is obtained from www.smartin-designs.com/hosts_info.htm, any site that has ads that are blocked by the hosts file doesnt load. I believe this may be because of DNS lookups that occur serially with content lookup, as is mentioned in bug 70213. The sites that fail with mozilla do not fail with other browsers such as internet explorer or konqueror. I request that this bug be fixed and not viewed as a future enhancement as seems to be indicated in bug 70213. In general, any blocked/slow-responding hosts will cause mozilla to look really bad. It is especially galling that IE 5.5sp1 running on top of Win4lin 2.0 on linux loads pages with ads blocked faster than does mozilla running natively on linux on the same box. I am running on Mandrake Linux 7.2 (close to RedHat 6.x) with glibc 2.1.3 and linux kernel version 2.2.17-21mdk on a Pentium 3 933Mhz with 256Meg of RAM, accessing the internet through DSL. I have also seen this problem at work (which is also a Mandrake Linux box) with a much faster connection. I am using mozilla nightly build id 2001032409. One can see the bug using any site that has URLs whose entries are set to 0.0.0.0 in the hosts file; I have included an example URL above. To get the hosts file I am using, just get the hosts file from smartin-designs.com that has entries of the form 0.0.0.0 for various blocked URLs. I'm including a few lines below. 0.0.0.0 pc11.DAL.247media.com 0.0.0.0 pc11.LA.247media.com 0.0.0.0 pc11.SF.247media.com 0.0.0.0 pc12.CHI.247media.com 0.0.0.0 pc12.DAL.247media.com 0.0.0.0 pc12.LA.247media.com 0.0.0.0 pc12.SF.247media.com 0.0.0.0 pc13.CHI.247media.com 0.0.0.0 pc13.DAL.247media.com
Comment 2•23 years ago
|
||
doesn't seem to be a dup of 70213 -- that bug should just cause timeout alerts for content that cannot be fetched, but the page should still get rendered. Marking dependency, though.
Depends on: 70213
Comment 3•23 years ago
|
||
Marking NEW.
Assignee | ||
Updated•23 years ago
|
Target Milestone: mozilla0.9.1 → mozilla0.9.2
Assignee | ||
Comment 4•23 years ago
|
||
Assignee | ||
Comment 5•23 years ago
|
||
70213 is unrelated... that only applies to lookups that actually hit a domain name server. removing dependency.
Status: NEW → ASSIGNED
No longer depends on: 70213
Assignee | ||
Updated•23 years ago
|
Priority: -- → P2
Assignee | ||
Updated•23 years ago
|
Priority: P2 → P3
This bug is FIXED! I can confirm that with the 2-line patch in the attachment provided by darin's comment above and using a ad-blocking host file, pages that previously would not display correctly now do display correctly. Further, I tried this without the hosts file above and everything still displayed correctly, so accepting this checkin should not break anybody who doesnt use ad-blocking hosts files in the style mentioned above. Further, I emptied my cache (in case the pages were being served from cache) and, with the ad-blocking hosts file, was still successfully able to access various sites. Thanks a lot for fixing this bug!
Comment 8•23 years ago
|
||
sr
Comment 9•23 years ago
|
||
a= asa@mozilla.org for checkin to the trunk. (on behalf of drivers)
Assignee | ||
Updated•23 years ago
|
Whiteboard: r=gagan, sr=dougt, a=asa
Assignee | ||
Updated•23 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 10•23 years ago
|
||
fix checked in
You need to log in
before you can comment on or make changes to this bug.
Description
•