192127 - Moz doesn't realize when the ip address of a host is changing

Status: VERIFIED DUPLICATE of bug 168566

(Core :: Networking, defect)

Description

[Michael Kremser]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030202
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030202

Just visit the page above, wait one day (then the ip address should be changed
by my ISP) and click "Refresh" --> Moz contacts the ip address resolved one day
before (checked with netstat).

Reproducible: Sometimes

Steps to Reproduce:
1. Visit a webpage hosted on a server with dynamic ip address
2. Wait until the ip address is changed
3. Click "Refresh" and Moz tells you that it can't access the server



Expected Results:  
If it can't contact the website, it should try to resolve the ip address for the
host name again.

Comment 1

[Boris Zbarsky [:bzbarsky]]

See bug 162871

Comment 2

[benc]

Michael: Please verify if this bug would make the browser do what you want.

*** This bug has been marked as a duplicate of 168566 ***

Comment 3

[Michael Kremser]

@ benc: What do you exactly mean by that? The issue is that Mozilla caches
resolved DNS entries and there should be a way of turning this "feature" on and off.

Bug 168566 describes the same problem.

Bug 162871 has also to do with that issue, people talked a lot about it; I think
there should be found a solution quickly, otherwise too many people will move
away from Mozilla (the issue makes the browser definitely unusable) and we don't
want that, right? ;-)

Comment 4

[benc]

Michael: if you agree that bug 168566 is the same problem, then change the
status to VERIFIED...

As for fixing this, the problem is that the current behavior is blocks a serious
security exploit from working. We cannot turn this behavior off, so we need to
improve the overall design.

Comment 5

[Michael Kremser]

Alright... changed to VERIFIED. But please let me say again that this is an
*URGENT* problem that makes Mozilla unusable and the "feature" that should avoid
security problems, makes just a new one and the current behaviour of Mozilla IS
wrong and annoying (I can't tell my web page visitors that they should use
Mozilla as long as they can't).