If you think this add-on violates Mozilla's add-on policies or has security or privacy issues, please report these issues to Mozilla using this form.
Please don't use this form to report bugs or request add-on features; this report will be sent to Mozilla and not to the add-on developer.
Спасибо! Хорошее дополнение к защите вашего браузера и личной информации.
Я рад, что вы чувствовали хорошо.
So you re-invented RefControl?
Could you provide a comparison of your extension with RefControl, so users would know which one is better?
"Disable HTTP Referer at Startup" and "RefControl" is a slightly different flavor.
RefControl is a good extension can control the Send HTTP Referer.
RefControl can be done in a simple and automatic if you want to enable the Send HTTP Referer only a particular site.
However, in my opinion is to fine-grained control is not suitable.
Overview of RefControl:
RefControl can control send HTTP Referer for each site.
When you settings once, thereafter controlled automatically.
But RefControl is to enable or disable the entire site, can not be enabled only a portion of the site.
Defaults for site, can not control send HTTP Referer by standard config 'network.http.sendRefererHeader',
also can not control send HTTP Referer by other extensions or features which changing 'network.http.sendrefererHeader'
On the other hand, Disable HTTP Referer at Startup is very simple extension.
When Firefox startup, force disabled send HTTP Referer, thereafter send HTTP Referer was controled by standard config 'network.http.sendRefererHeader',
Also can control send HTTP Referer by other extensions or features which changing 'network.http.sendrefererHeader'
So if your intended use is "enable or disable the entire site" and "do not control by hand(do not change network.http.sendrefererHeader manually)", it is better to use the RefControl.
Otherwise, it is better to use "Disable HTTP Referer at Startup".