Closed Bug 194026 Opened 23 years ago Closed 23 years ago

browser waits for connection timeout when attempting to retrieve images from ad servers my firewall blocks.

Categories

(Core :: Graphics: Image Blocking, defect)

x86
Linux
defect
Not set
minor

Tracking

()

VERIFIED DUPLICATE of bug 193967

People

(Reporter: jcooper, Assigned: security-bugs)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030105 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030105 This is a feature request. At this time, the browsers times out when hitting blocked sites (ad servers). It would make browsing much smoother (and faster) if mozilla recognized a "REJECT" from iptables and moved on. FYI, I am using reject, not deny. And I have tried a few --reject-with options without success (well, the ads are blocked, but mozilla still times out, then proceeds with processing the page). Reproducible: Always Steps to Reproduce: 1. Put something like this in your iptables start script: # deny ad(s).doubleclick.net DoubleClick Ad requests iptables -A OUTPUT -d 204.253.104.0/24 -j LOG --log-prefix "FIREWALL:OUTPUT-ads " iptables -A OUTPUT -d 216.73.86.0/24 -j LOG --log-prefix "FIREWALL:OUTPUT-ads " iptables -A OUTPUT -d 204.253.104.0/24 -j REJECT --reject-with $rej iptables -A OUTPUT -d 216.73.86.0/24 -j REJECT --reject-with $rej where rej=icmp-host-prohibited 2. Hit any site using doubleclick ads. 3. Wait a minute or so for mozilla to time out then finish rendering the page. Actual Results: The page took forever to load. Expected Results: Acknowlege the iptables REJECT and continue rendering without the timeout. None applicable.
*** This bug has been marked as a duplicate of 193967 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
v.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.