Mason83 wrote on 25/02/2016 13:16:
On 24/02/2016 00:11, Alexandre Yudenitsch wrote:
EE wrote, on 23 Feb 16 15:16:
Are you blocking referers? If a site will not respond to clicks on
links, that could be the problem. If you are using RefControl, you can
make exceptions to blocking for particular sites.
I don't know what you mean: 'Link Behavior' in SM Preferences doesn't
say anything about blocking 'referrers', and as far as I know I'm not
using "RefControl" (is that an add-on/extension?).
I think EE is referring (see what I did there!) to the
network.http.referer.* and network.http.sendRefererHeader
config settings.
https://blog.mozilla.org/security/2015/01/21/meta-referrer/
http://www.ghacks.net/2015/01/22/improve-online-privacy-by-controlling-referrer-information/
http://kb.mozillazine.org/Network.http.sendRefererHeader
https://bugzilla.mozilla.org/show_bug.cgi?id=55477
https://bugzilla.mozilla.org/show_bug.cgi?id=822869
https://en.wikipedia.org/wiki/HTTP_referer
Regards.
Using $_SERVER['HTTP_REFERER']
The address of the page (if any) which referred the user agent to the
current page. This is set by the user agent. Not all user agents will
set this, and some provide the ability to modify HTTP_REFERER as a
feature. In short, it cannot really be trusted.
But we used it, because our spammer was not clever enough to forge a
correct referer :-)
So we discard any action coming from his site.
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
