Can't turn of DNS Prefetch function
Thu, 06/03/2010 - 19:51 — natri23
Using Firefox 3.6.4 with Foxy Proxy Basic 1.6.1, I failed try to disable the DNS Prefetch function using about:config
After restarted, FoxyProxy automatically deletes the preference network.dns.disablePrefetch I wonder if there is a explanation for this.
It would be better for me to turn this off since it causes DNS overload on my router.
People reading this post who
People reading this post who aren't familiar with DNS prefetching can read about it here: https://developer.mozilla.org/en/Controlling_DNS_prefetching
Coincidentally, I've been working on fixing this for the last few weeks. I've just released FoxyProxy Standard 2.21 and FoxyProxy Basic 1.7, both of which have the fix.
DNS prefetching must be disabled when you want to perform DNS lookups on a proxy server. The logic for determining how to set the network.dns.disablePrefetch preference
network.dns.disablePrefetch is now enabled only if:
1. FoxyProxy is not in disabled mode
AND
2.
a. FoxyProxy is set to "Use Proxy XXXX for All URLs". Proxy XXXX has the checkbox (on the "General" tab) "Perform remote DNS lookups on hostnames loading through this proxy" checked
OR
b. FoxyProxy is set to "Use proxies based on the pre-defined patterns and priorities". One or more of the ENABLED proxies have the checkbox (on the "General" tab) "Perform remote DNS lookups on hostnames loading through this proxy" checked. An enabled proxy is one whose "Enabled" checkbox is checked (this checkbox is also on the General tab)
I hope this explains everything.
Eric
Re: Can't turn of DNS Prefetch function
1.7 basic (same as 1.6.1) overrides (re-enables) the user configured (disabled) network.dns.disablePrefetch in disabled state.
so much for "completely disable foxy proxy"
effing with user settings for no reason is incredibly obnoxious and clearly violates the no surprises amo policy
https://addons.mozilla.org/en-US/developers/docs/policies/reviews#sectio...
1. If you want me to take
1. If you want me to take your claim seriously, you have to provide detailed instructions on how to reproduce the bug you're claiming exists. I've done DAYS of testing on this particular issue. Have you?
2. This is clearly documented in the FAQ under "Why does FoxyProxy enable network.dns.disablePrefetch?"
It's also been
It's also been well-documented in the release notes.
Re: Can't turn of DNS Prefetch function
1. If you want me to take your claim seriously, you have to provide detailed instructions on how to reproduce the bug you're claiming exists. I've done DAYS of testing on this particular issue. Have you?
It should take less than 5 minutes to confirm the problem the OP reported and that it's still present in 1.7. No need for DAYS, or more instructions, but since you're still denying you're changing settings without any legitimate cause, here are your instructions:
1) xp x86 sp3, Fx 3.6.3, new profile
2) set network.dns.disablePrefetch=true, restart
3) disablePrefetch is still there and still true
4) Install FoxyProxy Basic (FPB) 1.7, restart
5) FPB is in the disabled state
6) network.dns.disablePrefetch has been deleted
7) set it again, restart
8) deleted again
your docs talk about disabling prefetching when FP is active and needs to perform dns resolution through the proxy
you should never need to force prefetching on, especially in the disabled state, as described above, but also when active
Well, it appears you are
Well, it appears you are correct. My tests work in development mode, but not in the final XPI. I am investigating and will fix.
As for this:
"you should never need to force prefetching on, especially in the disabled state, as described above, but also when active"
That's not accurate. With prefetching on, DNS lookups do not go through a proxy server, even if you've checked "Perform remote DNS lookups on hostnames through this proxy" on the Proxy Details General tab. This is a limitation of Firefox prefetching at the moment.
Anyway, I'm about to release a minor version of FoxyProxy. It doesn't have this fix. I'm hoping the next one will.
Eric
Re: Can't turn of DNS Prefetch function
As for this:
"you should never need to force prefetching on, especially in the disabled state, as described above, but also when active"
That's not accurate. With prefetching on, DNS lookups do not go through a proxy server, even if you've checked "Perform remote DNS lookups on hostnames through this proxy" on the Proxy Details General tab. This is a limitation of Firefox prefetching at the moment.
You just restated why you may need to turn prefetching OFF. I said you should never need to force it ON. Do you maintain that is not accurate?
OK, firstly... I've
OK, firstly... I've re-tested more thoroughly and FoxyProxy is behaving exactly the way I intend it to. From the FAQ:
Why does FoxyProxy enable network.dns.disablePrefetch?
DNS prefetching is a feature of Firefox which increases page-load performance. You can read about it here. FoxyProxy disables DNS prefetching under certain conditions. It does this because DNS prefetching does not respect proxy rules. In other words, if DNS pretching is enabled but you want DNS lookups to occur through a proxy server, you're out-of-luck. As of FoxyProxy 2.21, DNS prefetching is disabled if:
1. FoxyProxy is not disabled
AND
2a. FoxyProxy is set to "Use Proxy XXXX for All URLs". Proxy XXXX has the checkbox (on the "General" tab) "Perform remote DNS lookups on hostnames loading through this proxy" checked
OR
2b. FoxyProxy is set to "Use proxies based on the pre-defined patterns and priorities". One or more of the ENABLED proxies have the checkbox (on the "General" tab) "Perform remote DNS lookups on hostnames loading through this proxy" checked. An enabled proxy is one whose "Enabled" checkbox is checked (this checkbox is also on the General tab)
Earlier versions of FoxyProxy disabled this preference indiscriminantly.
Concerning this question:
You just restated why you may need to turn prefetching OFF. I said you should never need to force it ON. Do you maintain that is not accurate?
I've done my best to maintain prior settings. In other words, if you had prefetching ON before installing FoxyProxy, or ON before enabling FoxyProxy, then the converse of the above conditions should revert prefetching to ON.
Does that make sense?
Eric
Re: Can't turn of DNS Prefetch function
OK, firstly... I've re-tested more thoroughly and FoxyProxy is behaving exactly the way I intend it to.
Let's review. You're deliberately forcing dns prefetching ON (by deleting the disablePrefetch setting) , even when FP is in the disabled state. There is no legitimate reason for doing that. FP does not need dns prefetching to be ON, whether FP is active or not. The arbitrary (without cause) and willful altering of browser settings is a clear violation of the AMO no surprises policy.
Now that you made it clear you're doing this intentionally, and stand by this decision, there is nothing more to discuss, fortunately there is an alternative to foxy proxy basic.
FoxyProxy forces dns
FoxyProxy forces dns prefetching ON only when you disable FoxyProxy AND if it was ON before FoxyProxy enabled. If you had it OFF, then enable FoxyProxy, then disable FoxyProxy, it should still be OFF.
How is restoring previous settings a violation of "No Surprises"? Are you seeing different behavior?
Eric
Re: Can't turn of DNS Prefetch function
Are you seeing different behavior?
I've already given you the steps to reproduce, which you claimed to have confirmed and which answer this question.
OK, so the bug you're
OK, so the bug you're reporting (confirmed as a bug now) is different than the OP's bug. That's what has been confusing me. I see the problem you're reporting now, have reproduced it, and will fix it shortly... hopefully this week.
Sorry for all the confusion, and thnks for being patient with me.
Eric
Re: Can't turn of DNS Prefetch function
OK, so the bug you're reporting (confirmed as a bug now) is different than the OP's bug.
How is it different?
After restarted, FoxyProxy automatically deletes the preference network.dns.disablePrefetch
The OP reported that you are forcing dns prefetching on by deleting the pref. My directions confirm this.
I mistook this post for
I mistook this post for another one; I didn't read the entire OP's post because I thought he was reporting a bug reported elsewhere in the forums. Anyway, I have a fix. Would you care to beta test it to confirm my tests?
If so, you can write me directly at eric dot jung at yahoo dot com.
Thanks,
Eric
This has been fixed in
This is now fixed in FoxyxProxy Basic 1.7.3 and FoxyProxy Standard 2.21.3.
Sorry for the inconvenience,
Eric