Open Bug 461221 Opened 17 years ago Updated 3 years ago

Should we clear the DNS cache when leaving the private browsing mode?

Categories

(Firefox :: Private Browsing, defect, P4)

defect

Tracking

()

Future

People

(Reporter: ehsan.akhgari, Unassigned)

References

Details

(Whiteboard: [PB-P3])

See shaver's comments on <https://wiki.mozilla.org/Talk:Firefox3.1/PrivateBrowsing/FunctionalSpec>. Actually I think this would be another good thing to handle in the private browsing mode, though I'm not sure if this can be taken in the Firefox 3.1 timeframe, so I'm filing a bug in order to centralize the discussion over this here.
Any thoughts on this?
Clearing the system DNS cache, on Windows at least, requires admin privileges. It's box wide and not specific to a user, afaik. It's also trival to view without those privs.. ipconfig /displaydns that's probably a OS oversight. Firefox's internal DNS cache is a different story. There are no tools available as far as I know at the moment to view it, but it's not outside the realm of possibility. Some reports on the web say that "cache" in Clear Private Data clears the internal DNS cache, is this true?
Mass moving of all Firefox::General private browsing bugs to Firefox::Private Browsing.
Component: General → Private Browsing
QA Contact: general → private.browsing
Whiteboard: [PB-P3]
Hard, not a huge priority right now.
Priority: -- → P4
Target Milestone: --- → Future
We should ship our own resolver, would make solving this (and a ton of other stuff) a lot easier!
(In reply to comment #6) > We should ship our own resolver, would make solving this (and a ton of other > stuff) a lot easier! Is there any bug on file for that?
(In reply to comment #6) > We should ship our own resolver, would make solving this (and a ton of other > stuff) a lot easier! I second that, the way private browsing currently handles the cache (by not handling it) clearly misleads users. You could extend this remark to Flash's Shared Objects as pointed at http://www.lifehacker.com.au/2009/11/how-to-really-browse-without-leaving-a-trace/ but it's probably not Firefox's responsibilty.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.