Closed
Bug 756884
Opened 13 years ago
Closed 13 years ago
myIpAddress return 127.0.0.1
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 304822
People
(Reporter: andi-moz, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:12.0) Gecko/20100101 Firefox/12.0
Build ID: 20120420145725
Steps to reproduce:
My employer has a complicated autoproxy script. With newer firefoxes it causes long stalls. I tracked it down to this
function FindProxyForURL(url,host) {
var me=myIpAddress();
if (me == "127.0.0.1") {return "DIRECT";}
So myIpAddress() returns 127.0.0.1 which returns the incorrect proxy. The host has various other IP addresses so this is clearly not correct. This leads to a long timeout and then eventually it recovers somehow.
Actual results:
Long stalls due to incorrect proxy.
Expected results:
myIpAddress() should not have returned 127.0.0.1
Updated•13 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 2•13 years ago
|
||
duping to a bug that hasn't had any activity since 2006 appears more like a bad joke than a "resolution"
Comment 3•13 years ago
|
||
Andi Kleen: Please understand what "resolution" means in the context of bug reports: "FIXED" is only one potential resolution for a report, "DUPLICATE" another one.
Patches are welcome to get things going, also see https://bugzilla.mozilla.org/page.cgi?id=etiquette.html for the "No obligations" section.
Comment 4•13 years ago
|
||
We get multiple bugs reports for the same issue when the reporter failed to find the original report. In that case people like me dupe the duplicate bug reports to the (in most cases) first report. This happened in this case.
That the original bug report is old (up to 12years) doesn't matter. It only means that nobody provided a patch. That is the result of the limited manpower.
I have my own personal issue with myIPAddress() because it returns the ipv6 link-local instead of the link-global. There is nothing that I can do to get it fixed except to learn c++ and write a patch.
Reporter | ||
Comment 5•13 years ago
|
||
Actually the original bug report *included* a patch. Just for some reason nobody in mozilla land seemed to be interested in merging it.
Comment 6•13 years ago
|
||
The patch is not correct and got a review-
That means that the patch needs an update before it can be merged
You need to log in
before you can comment on or make changes to this bug.
Description
•