AdGuard 5.10 release

Status
Not open for further replies.

avatar

Administrator
Staff member
Administrator
Dear friends!

It's time for release of a new Adguard version. Version 5.10 is the latest of the 5-series, the next is going to be Adguard 6.0.
However, it brings a lot of changes, improvements and bug fixes.

A complete list of changes can be found in our blog.

Many thanks to all who participated in the beta testing of Adguard 5.10.
Thanks to you, we have fixed hundreds of defects!

Sincerely,
Adguard team.
 

clarke

Beta Tester
Downloaded the Adguard 5.10 version,happy to see that now more filter subscriptions to be added,is now light on the resources..GUI is more responsive.......:)
 

Rian

Beta Tester
Congrats on the release ................. working great :) The Beta testing was soo good :) looking forward for the next Beta :) :cool:
 

avatar

Administrator
Staff member
Administrator
We've just released patch for Adguard 5.10.
Version 5.10.1164.5985

Changelog:
Improved HTTP and HTML filtering, fixed some minor bugs in it.
Fixed issue with some keep-alive connections (issue with theverge images)
Fixed some issues with Adguard userscripts (Assistant and WOT)
Fixed bug with domain restrictions in CSS rules
Decreased filters update period
 
Last edited by a moderator:

Venky

Beta Tester
Here is a look of Adguard 5.10 in the latest Windows 10. Working without any problems so far.



 

avatar

Administrator
Staff member
Administrator
It is a beta version with some minor fixes.

Changelog:
* Fixed some localization issues
* Changed the way we block requests. We now return "500 Request Blocked" for most of the blocked requests.
 

Boo Berry

Moderator + Beta Tester
Moderator
Same as the beta log posted above by avatar.

Changelog:
* Fixed some localization issues
* Changed the way we block requests. We now return "500 Request Blocked" for most of the blocked requests.
 

avatar

Administrator
Staff member
Administrator
We have not yet enabled auto-update for this version.
I'll post release notes on monday.
 

GunGunGun

New Member
Hi avatar, can you explain me why you return 500 instead 402 ?
" * Changed the way we block requests. We now return "500 Request Blocked" for most of the blocked requests. "

Thanks.

And just my suggestion, in my oppinion, use our own AdBlock list always much much better than AdBlock Plus Easylist which is slow and big, make a list that is optimized, short and easy to maintain.
 
Last edited by a moderator:

avatar

Administrator
Staff member
Administrator
Hi avatar, can you explain me why you return 500 instead 402 ?
" * Changed the way we block requests. We now return "500 Request Blocked" for most of the blocked requests. "
You mean instead of 204?

When our extension blocks request it looks like error for the code that makes this request (either javascript or flash).
Would be better if the app and extension will be similar in this.

And just my suggestion, in my oppinion, use our own AdBlock list always much much better than AdBlock Plus Easylist which is slow and big, make a list that is optimized, short and easy to maintain.
Our English filter is an Easylist fork so it's not that simple:)

Talking about EasyList size and speed, we are working on it:
http://forum.adguard.com/showthread.php?2899-resolved-Video-is-blocked-at-http-bleacherreport-com&p=35895&viewfull=1#post35895
 

GunGunGun

New Member
You mean instead of 204?

When our extension blocks request it looks like error for the code that makes this request (either javascript or flash).
Would be better if the app and extension will be similar in this.



Our English filter is an Easylist fork so it's not that simple:)

Talking about EasyList size and speed, we are working on it:
http://forum.adguard.com/showthread.php?2899-resolved-Video-is-blocked-at-http-bleacherreport-com&p=35895&viewfull=1#post35895
Ah thanks!
From the start I just think maybe return 500 can prevent some javascript Anti AdBlock detection.
 
Status
Not open for further replies.
Top