Adguard for Mac: version 1.2.0

Now some good news for Mac users – here is an update of Adguard for OS X.

Adguard for Mac 1.2.0

This new version brings a lot of very important changes to Adguard for Mac. Most viable changes are $replace modifier and many security improvements.

New $replace modifier for basic rules

This new rule modifier allows Adguard to change any web response on the fly. Adguard is pretty good at HTML content filtering, and with this new modifier we can change response content of any response disregarding the content type. This is especially important for blocking video ads, for instance when a video player uses the VAST/VPAID protocol. Simple blocking of the web requests will break the video player. So the only way to block such ads is to modify response content, removing the ads from it. #38

UI changes

  • [Added] New localizations: Serbian (Latin), German, Italian, Spanish, Chinese Traditional, Armenian, Turkish, Korean, Indonesian, Hungarian. #50
  • [Added] User warnings in case HTTP proxy mode fails to start. #22
  • [Changed] Assistant requests are now excluded from ‘Filtering log’. #4
  • [Changed] Now clicking on Adguard icon in status bar brings opened Adguard windows to front and makes them active. #33
  • [Fixed] Error previously led to inability to change HTTP proxy port with HTTP proxy mode enabled. #42
  • [Fixed] Lack of explanation text in the ‘Enter email address’ text field. #44

Ad blocking

  • [Added] $genericblock rule modifier. #16
  • [Added] $generichide rule modifier. #15
  • [Added] $replace modifier for basic rules #38
  • [Changed] Now $popup rules modifier is also applied to server redirect responses. #49
  • [Changed] Now status 500 is always returned for blocked requests. #35
  • [Changed] User filter is now loaded last, after all other filters are loaded. #41
  • [Fixed] Error in css-inject rules. #7
  • [Fixed] Error in finding the elements path on a page for HTML filtering rules. #17
  • [Fixed] Error in HTML filtering rules – previously empty elements were never removed. #29
  • [Fixed] Improved processing of rules with $popup modifier. #25
  • [Fixed] Modifiers for the whitelist rules now work while filtering content. #57
  • [Fixed] Now $elemhide rule modifier is applied only to HTML pages. #14
  • [Fixed] Problem with basic rules being treated as rules with $popup modifier. #34
  • [Fixed] Template modifier * in rules now takes into account line break symbols. #40
  • [Fixed] Third-party requests filtering error. #6

Networking

  • [Changed] Adguard automatically stops filtering of the websites with client certificate authorization. #2
  • [Changed] Browser cache is now suppressed for a short period of time after filtering startup. #53
  • [Changed] For all modern browsers SHA1 certificates were deprecated. #46
  • [Changed] Port Adguard accepts connections on. #5
  • [Changed] Updated default list of SSL exceptions. #3
  • [Fixed] Problem when Adguard caused browser to freeze. #37

Browsing Security

  • [Changed] A method of domain check with Browsing Security module. Requests privacy was improved. #8

Compatibility issues

  • [Improved] Compatibility with sites that use the Content-Security-Policy mechanism. #58
  • [Fixed] Blocking of Google Chrome Rapportive extension for Gmail. #30
  • [Fixed] Problem when Adguard extension for Google Chrome couldn’t see triggered $genericblock rules. Integration mode works correctly now. #39
  • [Fixed] Safari inability to connect to some websites with IPv6 network configuration. #10

New version is already available for update. Waiting for your comments :)

Sincerely,
Adguard team

Mr. Adguard

Wow... you got us! We really can't remember who wrote this article... So, here I am - Mr. Adguard tidying up after someone else.

Subscribe to Adguard Blog

Get the latest posts delivered right to your inbox.

or subscribe via RSS with Feedly!