لتجربة الآلاف من الإضافات المتوفرة هنا، نزّل متصفح موزيلا فَيَرفُكس مجانًا. المتصفح الأسرع والأكثر أمانًا في عالم الإنترنت.
Closeمرحبا بك في إضافات فَيَرفُكس.
اختر من بين الآلاف من المميزات والمظاهر الإضافية واجعل فيرفُكس ملكًا لك.
Closeمقيمة بـ 5 من 5 نجوم
It's a pity but version 0.5.25 didn't resolve the conflict with DrWeb link checker: https://github.com/RequestPolicy/requestpolicy/issues/287
I still have to "Temporally allow all redirections" if I want to check a link. For information, I have the latest stable Firefox and DrWeb Link Checker 2.5.8.
مقيمة بـ 5 من 5 نجوم
It is impossible to use <a href="https://addons.mozilla.org/en-US/firefox/addon/drweb-anti-virus-link-checker/?src=ss">Dr.Web LinkChecker</a> simalteniosly with RequestPolicy. I tried to run Dr.Web LinkChecker on sites where all redirections are allowed: the checker opens its pop-up and starts endless "checking". As I understand it tries to connect with Dr.Web's databases but RequestPolicy doesn't allow this. And only when I choose the option "Temporally allow all redirections", the checker gets the chance and finishes its work. I think it is very strange that I have to allow something on sites where everything are already allowed.
I understand that RequestPolicy must block redirections but I would like to ask to make exceptions for Dr.Web Linkchecker. This add-on is a sort of pro-active defence and I think it should be allowed everywhere and every time.
Thanks for the report. I'm tracking this bug here: https://github.com/RequestPolicy/requestpolicy/issues/287 ---- This should be fixed in the next release of RequestPolicy (0.5.25).
لإنشاء مجموعاتك الخاصة، يجب أن تمتلك حسابا على موقع إضافات موزيلا.