Closed
Bug 267699
Opened 20 years ago
Closed 19 years ago
PAC: myIpAddress() returns ::1
Categories
(Core :: Networking, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: vasiliy_gagin, Assigned: darin.moz)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20040913 Firefox/0.10 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041026 Firefox/1.0RC1 In PAC configuration file myIpAddress() returns "::1". It looks same as "resolved" BUG 238341. Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: ::1
Comment 1•20 years ago
|
||
Maybe it is a dupe, i can't figure out exactly (that bug was resolved, reopened and resolved again without a patch; but the 1.7 branch was created before the reopening on which Firefox depends more or less). Reporter: Can you download the latest Mozilla release from http://ftp.mozilla.org/pub/mozilla.org/mozilla/releases/mozilla1.8a4/ and test if that bug still occours there?
| Reporter | ||
Comment 2•20 years ago
|
||
Installed mozilla-win32-1.8a4-installer.exe Same problem
Comment 3•20 years ago
|
||
This does look like bug 191715 which is in fact supposed to be fixed on trunk... Darin, what's up here?
Assignee: general → darin
Component: Browser-General → Networking
QA Contact: general → benc
So if you use: http://www.mozilla.org/quality/networking/testing/PAC/myIpAddress.pac for your pac file, do you see that in the javascript console? WFM on Mac OS X, 1.7.5. Do you have IPv6 loaded on the system? Maybe a Windows + IPv6-only problem? I recall another problem like this, but can't find the bug.
Comment 5•19 years ago
|
||
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 6•19 years ago
|
||
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•