Comment 33 for bug 207456

(In reply to comment #21)
> Seems resonable to have cache disabled for anything that gets translated into
> 127.0.0.1. After all it's almost like loading a file from disk anyway.

I don't agree. If web developers want to test their cache headers on localhost server the behavior will be different from what is expected normally when address of the same configured server is not localhost.

(In reply to comment #22)
> Just a thought, but maybe there could be something like:
> browser.cache.offline.disable_on='localhost, 127.0.0.1'
> and/or
> browser.offline.never_offline_on='localhost, 127.0.0.1'
>
> (similar to network.proxy.no_proxies_on)

To fix this bug is not that simple and have option like this as well. When necko gets to offline mode DNS and socket service get shutdown. It means we cannot resolve localhost to 127.0.0.1 (ipv4) or ::1 (ipv6) and even we could we cannot run any connections to it. This would mean complex rebuild of the necko infrastructure. There is workaround for this described in comment 6.