287420 - Windows version of Firefox does not respond correctly to REJECT target for iptables.

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Eric Anderson]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1

I have two locations i use firefox from. Home under linux, and work under win2k.
From home i have been annoyed by flash banner ads and added a iptables rule to
reject all traffic bound for ads.nozonedata.com (the ip, not the name). Firefox
under linux loads fine and takes the REJECT as a down site or whatever and loads
the page without errors and stops displaying the "loading" animation as soon as
the primary site images are loaded.

At work i have an IDENTICAL rule in my iptables config to REJECT traffic bound
for this site. Under Win2k (and under a Win2k VMware session from home) i get
the "loading" animation for more than 30 seconds after the page finishes loading.

I obviously prefer the behavior under linux, but consistency would be preferable
between the two versions.

The site in question is www.darkthrone.com, but the banner ads i am blocking
from iptables are all loaded in a frame from http://ads.nozonedata.com/.

Reproducible: Always

Steps to Reproduce:
1. Include iptables filter to REJECT all outbound traffic to
ads.nozonedata.com's ip from fw.
2. Go to and log into www.darkthrone.com
3. From win2k watch the loading animation go on forever, under linux note the
page loads normally and stops within a couple of seconds as expected.




What i am experiencing is probably not common, but i would not need to do this
at all if there were a way to block entire sites as opposed to simply block
images from site.

Comment 1

[Ben Fowler]

Are you expecting the REJECT rule to have the kernel send a TCP reset packet? If
so, does it do so, and does Firefox reset the TCP connection?

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.