User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0a1) Gecko/20111108 Firefox/10.0a1 Build ID: 20111108031146 Steps to reproduce: I sometimes connect to a network that redirects all network traffic to an authentication page. After you authenticate, you can browse normally. However, links that were redirected to the authentication page continue to be redirected to a cached authentication page at the cached IP address for the redirect. Switching networks to one without the authentication page results in still being sent to a cached authentication page, even though I'm no longer on the network for which the private page IP is even valid. Actual results: 1) Connect to network with auth page. 2) Click on toolbar shortcut to any page (say, google) 3) Request is redirected to private IP space at 10.50.0.2. 4) Either authenticate and connect to the same network, or switch to a different network in which the private IP space doesn't exist. 5) Click on the shortcut to google. 6) The auth page at 10.50.0.2 is displayed, even though the redirect is no longer occurring, or the computer is no longer on the network with that page. 7) Problem continues unless the browser cache is cleared. Expected results: Browser obtains the correct IP and goes to the correct page.

Definitely not an installer bug. You should move this bug over to core -> netorking: cache

Weird. I thought it was submitted to General. I've switched it to Core, but there doesn't seem to be a menu option for networking or cache in there...

Are you talking about a fake DNS result that is being cached (1) or a HTTP-redirect that is cached (2) ? (1) see http://kb.mozillazine.org/Network.dnsCacheExpiration how to disable the dns-cache. It's currently 3 minutes btw. (2) Recent browsers started to respect caching directives for redirects in a better way, especially the 301 redirect. Can you provide an example of the redirect request (a Wireshark capture for instance), please ?

Just tried to get a wireshark capture, but this is turning out to be difficult. As it turns out, once you register your MAC address, you don't get the registration page again, and attempting to connect to the registration server seems to fail. So I'll do my best to describe it. I connect to the network. I click on a bookmark to google. The DNS reply appears to be a 10.50.0.x number. Note - it's not just Firefox that's affected. None of my programs can connect to anything on the outside network until I register the MAC address of the machine. They just get redirected to the 10.50.0.x IP - regardless of protocol. I register. I can connect. But the bookmark still sends me to the 10.50.0.x IP. If I switch to my own network, clicking on the bookmark also sends me to it. The page appears to load from cache, since it's not accessible. In the url bar, I see the 10.50.0.x IP with the cached page's name, rather than the bookmark (google). Clearing the browser cache (not the DNS cache) resolves this problem. The first time I had this happen, I tried restarting the browser. That did NOT resolve the problem, as I recall. Only clearing the cache did.

Workaround: I have found that shift-reload usually fixes this.

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258