Open
Bug 525921
Opened 15 years ago
Updated 2 years ago
Would like a mechanism to disable or purge the DNS cache through JavaScript
Categories
(Core :: Networking, defect, P3)
Core
Networking
Tracking
()
NEW
People
(Reporter: rcampbell, Unassigned)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [necko-backlog])
Currently, developers trying to figure out networking problems on their site have to contend with a full DNS cache. This can present problems when trying to debug some types of networking conditions. Would like to have a means to either clear the cache or a way to turn it off altogether.
Comment 1•14 years ago
|
||
file|work offline clears the cache What do you mean with "have to contend with a full DNS cache"? Also note that DNS cache entries are pretty shortlived.
Reporter | ||
Comment 2•14 years ago
|
||
how short-lived? I think the intent of this bug was to provide a way to set the DNS cache back to a clean state so developers could see what kind of round-trip time they were getting to their pages in a "cold" state. I wasn't aware of the "work offline" trick to clear those. That might be a useful work-around if we don't want to provide an explicit option to dump those caches.
Comment 3•14 years ago
|
||
3 minutes by default (used to be 1 until we implemented DNS prefetching) Is this just asking for exposing DNS cache clearing through XPCOM, or for actually exposing this to content script?
Reporter | ||
Comment 4•14 years ago
|
||
(In reply to comment #3) > 3 minutes by default (used to be 1 until we implemented DNS prefetching) good to know, thanks. > Is this just asking for exposing DNS cache clearing through XPCOM, or for > actually exposing this to content script? Just XPCOM so we could implement a control somewhere in the UI or in the console to forcibly purge the cache. Not a content thing.
Updated•8 years ago
|
Whiteboard: [necko-backlog]
Comment 5•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
Comment 6•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•