Closed Bug 238806 Opened 20 years ago Closed 20 years ago

Firewall reports repeatedly: "Mozilla tried to receive data from the internet (127.0.0.1) ...", although Mozilla is not fetching anything from the internet.

Categories

(SeaMonkey :: General, defect)

x86
Windows XP
defect
Not set
minor

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 100154

People

(Reporter: andyreif, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7a) Gecko/20040219
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7a) Gecko/20040219

After engaging Internet Lock using ZoneAlarm firewall, firewall repeatedly
reports that Mozilla tries to receive data from Internet(127.0.0.1), although
Mozilla is inactive (not downloading anything, not connected to email server).
Even after closing all the windows, this behavio(u)r only stops after disabling
QuickLaunch. 

I don't know whether this behavior is caused by Browser-General, Networking or
perhaps some other component.

Reproducible: Always
Steps to Reproduce:
1. Install ZoneAlarm (version:4.5.538.001), select "Alerts & Logs"->"Alert
Events Shown"->"on"
2. Activate "Internet Lock"
3. Start Mozilla
Actual Results:  
ZoneAlarm repeatedly reports:
ZoneAlarm reports repeatedly (every couple of seconds, and this is really annoying):
 ZoneAlarm Alert
 Internet Lock
  Mozilla tried to receive data from the Internet(127.0.0.1),
  but was denied access by the Internet Lock.

Expected Results:  
Mozilla shouldn't try to access 127.0.0.1 before typing in a URL or after the
download of a given URL is complete.
This is probably dupe of bug 100154.


btw: 127.x.y.z is the computer-internal "network" not the Internet. 
yup dupe
Reporter: You can allow that connection safely

*** This bug has been marked as a duplicate of 100154 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
v
Zonealarm is wrong because 127.0.0.1 is localhost and not the internet
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.