Their response was "chances of these rules actually matching anything are very low". Old versions of Adblock Plus didn't support comments, and when they introduced comments, the old Adblock Plus read the comment lines as URLs to block. There is no consideration for upgrade path.Even the writing filters document doesn't fully document the format. The file format is very badly documented. There are several problems with supporting Adblock Plus filters: This will improve GlimmerBlocker for everybody, including those that doesn't like the shotgun approach to blocking that the Adblock Plus rules use. Please send me the URL of sites which has ads that the current included filters doesn't block. The files in /Library/GlimmerBlocker can only be changed when the user has authenticated. The reason GlimmerBlocker stores its settings in /Library/GlimmerBlocker instead of /Library/Preferences/GlimmerBlocker is that /Library/Preferences is writeable by users who is allowed to administer the mac, even when they have not authenticated. Why are settings in /Library/GlimmerBlocker? This will come as soon as I get the time. I did start installing a Django based board, but was then completely drowned in work. Even if GlimmerBlocker tried to work as a middleman and decoded/encoded the content, it would have no means of telling Safari to trust it, nor to tell Safari if the websites certificate is valid, so Safari would think you have visited a dubious website.įortunately, most ad-providers are not going to switch to https as serving pages using https are much slower and would have a huge processing overhead on the ad-providers servers. The disadvantage is, that GlimmerBlocker can't modify the content. The advantage is that any intermediate proxies can't modify or read the contents of the page, nor the URL. When Safari fetches an https page using a proxy, it doesn't really use the http protocol, but makes a tunneled tcp connection so Safari receives the encrypted bytes. The only solution is to petition Apple to include proper keyword search in Safari. That keywords work at all is because Safari sends the invalid URL-hostnames to GlimmerBlocker (spaces is not an allowed character in hostnames), but when the hostname contain a quote, Safari gives this message before even contacting GlimmerBlocker. Keywords searches with special characters fail You can fix the proxy settings by opening the GlimmerBlocker System Preferences Panel, choosing the "Network" tab, and click "Update Now" in the "Network proxy settings" section. 3G wireless) the proxy settings then GlimmerBlocker can't automatically update the network settings as it runs with reduced permissions to enhance security. When you install GlimmerBlocker it sets the proxy configuration for the network interfaces. The request flow is then: Safari → GB → Authoxy → CompanyProxy → Website. In GlimmerBlocker's network tab, set the proxy to Authoxy's port number. However, there is a Safari extension which provides the same functionality: KeySearch by Matt Swain. Asked questions Safari keyword expansions don't work anymoreĪpple has upgraded Safari in Mac OS X 10.8.2 so it performs Google searches using SSL (https) and this makes it impossible for GlimmerBlocker to intercept the searches and perform keyword expansions.
0 Comments
Leave a Reply. |