![]() It will not result in GlimmerBlocker sending back a redirect response to Safari. returns hostname for client ip address using reverse dns lookupĬhanging any of the gb.request attributes in a request-modification script makes GlimmerBlocker use the new values when getting the content from the server. returns client ip address as dotted decimal in a Javascript string. If you set an attribute to null or an empty string, the attribute will be deleted. it will still set the attribute "User-Agent". The attribute name is the proper mixed-case name of the header (e.g. returns a Javascript object which contains all the request headers. Var s = gb.request.baseContentType // Content-type without any semicolon-options. S = "application/x-www-form-urlencoded" // Typically null. Var s = gb.ntentType // The full content-type of the *request*, not the response. Var s = gb.thod // Changing the method easily breaks everything. Var s = gb.request.urlQuery // only the query path of the URL, excl. the host and port, separated by colon. Var s = gb.request.url // the full URL of the request keyword rules: defined, but read-only as the request is never forwarded to a web-server.transformation rules: defined, but read-only as the request already has been executed.request-modification rules: defined and modifiable.OBS: the result includes single quotes. jsEncode("Hello, D'Angleterre") -> "'Hello, D\x27Angleterre'" encode a string to be a Javascript string token: gb.urlDecode("Hello%2C%20D%27Angleterre") -> "Hello, D'Angleterre" decodes a string with %-escapes: opposite of gb.urlEncode() Var html = gb.htmlEncode("Paul & Allan says '1 "Hello%2C%20D%27Angleterre" converts the object into a JSON-like string using same format as %o in gb.log() flags which tells the state of the proxy server debug checkboxes. compares the version to v, and returns -1, 0 or 1. contains the current GlimmerBlocker version, Read-only. The parameters will still be evaluated, so this is only for simple logging. same parameters as gb.log(), but logs only when the proxy server debug logging %f: floating point (no formatting yet) %o: dump the object in JSON-like format (no escape of keywords, supports NaN). The first parameter is a format string just like console.log() in Firebug: Logging to the console (use the "Open Log" button on the developer tab). Improved IPv6 connectivity test class and logging.Gb.log("I had %d birds and a %s dog", 42, "black").Fix host header used for proxy requests as some client software doesn't use the wanted hostname in the host-header but only in the full URL.Smart quotes are now disabled in filter code editing.Workaround for servers which sends space before colon in HTTP headers.Use ISO-8859-1 when sending HTTP headers to browser.If this version prompts you to install a java runtime, please tell me at Detect application/smil as XML. ![]() Port number is now included in forwarded host header.Digits in top-level domains are now allowed.Fixed bugs which made WebDav publishing dialog (and others) likely to hang or crash.Complete new updater which will dramatically reduce the amount of data to download (for following updates).This made GlimmerBlocker unable to block ads when you reactivated GlimmerBlocker. Fixed problem with network settings not being activated when activating GlimmerBlocker.See the included filters for examples, e.g., adding a download link. If you can program in JavaScript you'll be able to add your own modifications to pages. So I hope you're happy with the tradeoff. But you win a lot in stability, and GlimmerBlocker provides much easier methods for adding your own modifications to pages by adding CSS rules, pieces of JavaScript or by transforming the HTML before Safari receives it. Because GlimmerBlocker doesn't hack Safari, there is a few things it isn't able to do: adding a block by right-clicking an image, stopping pop-unders, and filtering cookies from 3rd party sites. This makes it much easier to use the beta versions of Safari and especially the nightly builds of WebKit. You'll always be able to upgrade Safari without breaking GlimmerBlocker (or waiting for a new release) and you'll be able to upgrade GlimmerBlocker without upgrading Safari. It is even compatible with all other browsers. GlimmerBlocker is implemented as an HTTP proxy, so the stability of Safari isn't compromised because it doesn't use any hacks. This compromises the stability of Safari and very often creates problems when Apple releases a new version. The problem with other ad blockers for Safari is that they are implemented as awful hacks: as an InputManager and/or ApplicationEnhancer. GlimmerBlocker is a different kind of ad blocker.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |