{"issue":{"user":{"id":1240282,"login":"jsamuel","url":"https://api.github.com/users/jsamuel","gravatar_id":"bc1d195cedb959a3946572b08ce9e7c7","avatar_url":"https://secure.gravatar.com/avatar/bc1d195cedb959a3946572b08ce9e7c7?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"title":"\"disable dns prefetch on startup\" doesn't work","milestone":null,"created_at":"2011-12-22T18:57:33Z","labels":[{"name":"extension","url":"https://api.github.com/repos/RequestPolicy/requestpolicy/labels/extension","color":"ededed"}],"state":"closed","updated_at":"2011-12-22T18:57:36Z","id":2640504,"html_url":"https://github.com/RequestPolicy/requestpolicy/issues/171","pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"closed_at":"2011-12-22T18:57:36Z","body":"    imported trac ticket\n    created: 2011-01-31 11:47:05\n    reporter: justin\n\nThe \"disable dns prefetch on startup\" features does not work after the first run of !RequestPolicy. Thanks to Archaeopteryx who reported this bug.\r\n\r\nThe cause may be confusion about a pref which doesn't have a default value at all, `network.dns.disablePrefetch`, being checked only to see if it has a user value without regard to the fact that it may have a user value that is \"false\". So RP does the right thing if dns prefetching was re-enabled by deleting the pref but not if the pref was set to \"false\" (which is what the new RP preference UI in #84 does).\r\n\r\nIt's a bit embarrassing that I didn't notice this when testing the fix for #84, which is likely how Archaeopteryx noticed it.","number":171,"url":"https://api.github.com/repos/RequestPolicy/requestpolicy/issues/171","comments":1,"assignee":null},"action":"closed"}