Include and exclude rules: Difference between revisions
m Reverted edits by 178.239.58.133 (Talk) to last revision by 96.255.181.51 |
split out globs into a section, add regular expression section |
||
| Line 12: | Line 12: | ||
* <code><nowiki>http://www.example.com/baz/</nowiki></code>. | * <code><nowiki>http://www.example.com/baz/</nowiki></code>. | ||
== Globs == | |||
Include and exclude rules support the <code>*</code> or [[wikipedia:Glob (programming)|globbing operator]]. | |||
The <code>*</code> serves as a wildcard that matches one or more of any character. | |||
A rule can have several wildcards or none, in which case the rule must match the entire URL exactly. | |||
Exclude rules look the same, and prevent the script from being executed. | |||
For example: | |||
If no include rule is provided, <code>@include *</code> is assumed. That is | <pre class="sample"> | ||
// ==UserScript== | |||
// @include <nowiki>http://www.example.com/foo/*</nowiki> | |||
// @include <nowiki>http://www.example.org/*.bar</nowiki> | |||
// @exclude <nowiki>http://www.example.com/foo/baz</nowiki> | |||
// ==/UserScript== | |||
</pre> | |||
If no include rule is provided, <code>@include *</code> is assumed. | |||
That is: every URL will be matched, within the allowed [[#Greaseable_schemes |Greaseable schemes]]. | |||
== Regular Expressions == | |||
As of [[Version_history#0.9.8|Greasemonkey 0.9.8]], support for full regular expressions in include and exclude rules was added. | |||
If the rule both starts and ends with a forward-slash (<code>/</code>) character, the contents inside those slashes are interpreted as a a regular expression. | |||
For example: | |||
<pre class="sample"> | |||
// ==UserScript== | |||
// @include <nowiki>/https?://www.example.com/*/</nowiki> | |||
// @include <nowiki>/http://www.example.(org|net)/*/</nowiki> | |||
// ==/UserScript== | |||
</pre> | |||
Note: | |||
* The rule is parsed as a standard javascript <code>new RegExp()</code>, so you do not need to escape forward slashes inside the rule. | |||
* The rule is always treated as case insensitive. | |||
== Greaseable schemes == | == Greaseable schemes == | ||
Revision as of 16:11, 1 August 2011
User scripts specify include and exclude rules in the metadata block.
The script will execute if it matches any include rule, as long as it does not match an exclude rule.
The rules are URLs, which can have a "wildcard" asterisk (*), which matches any string including the empty string. For example: http://www.example.com/foo/* will match:
http://www.example.com/foo/barand,http://www.example.com/foo/
but not:
http://www.example.com/baz/.
Globs
Include and exclude rules support the * or globbing operator.
The * serves as a wildcard that matches one or more of any character.
A rule can have several wildcards or none, in which case the rule must match the entire URL exactly.
Exclude rules look the same, and prevent the script from being executed.
For example:
// ==UserScript== // @include http://www.example.com/foo/* // @include http://www.example.org/*.bar // @exclude http://www.example.com/foo/baz // ==/UserScript==
If no include rule is provided, @include * is assumed.
That is: every URL will be matched, within the allowed Greaseable schemes.
Regular Expressions
As of Greasemonkey 0.9.8, support for full regular expressions in include and exclude rules was added.
If the rule both starts and ends with a forward-slash (/) character, the contents inside those slashes are interpreted as a a regular expression.
For example:
// ==UserScript== // @include /https?://www.example.com/*/ // @include /http://www.example.(org|net)/*/ // ==/UserScript==
Note:
- The rule is parsed as a standard javascript
new RegExp(), so you do not need to escape forward slashes inside the rule. - The rule is always treated as case insensitive.
Greaseable schemes
Greasemonkey will run scripts only on documents loaded from particular schemes. By default, those are:
- http
- https
- ftp
- data
(Note: What is officially called a 'scheme' in a URL is also found in Javascript as the .protocol property of any abstract link element such as <a>, <link>, or a DOM object such as document.location.)
Extra schemes
Greasemonkey will also run scripts on:
- file
- Only if
greasemonkey.fileIsGreaseableis set totruein about:config. - about
- Only if
greasemonkey.aboutIsGreaseableis set totruein about:config.
(But about:blank is always allowed.)
In both cases this restriction is intended to prevent security/privacy vulnerabilities.
Magic TLD
The only special syntax besides the wildcard is .tld. An include such as http://www.example.tld/* will match any top level domain, such as www.example.com, www.example.org, www.example.co.uk, and so on. One must be careful with this, to not accidentally leak data to a site that they did not mean to match. This list of TLDs includes a myriad of dual-segment TLDs (such as ca.us, aeroport.fr and kyoto.jp), beside the plain country or category codes (com, jp, se). For a full list see the Magic TLD page.
Data scheme user scripts
Browsers can open windows in which all of the page top content is contained in a data scheme URI. For example, the below URI will display a HTML page that indirectly includes an image from google.com as its sole content:
data:text/html;charset=utf-8,<html><head><title>data: test</title></head><body><img src='http://www.google.com/intl/en_ALL/images/logo.gif'></body></html></pre>
This link points to the above data URI and can be clicked to see it in action.
Firefox ignores unknown semicolon separated parameters in the header of a data URI (and the standards seem to leave this possibility open) which means if one adds say the string MyScript; in the header of the above URI, giving:
data:text/html;MyScript;charset=utf-8,<html><head><title>data: test</title>....
one can then use Include and exclude rules such as
@include data:text/html;MyScript;*
to trigger user scripts to run on a subtype of data URIs.
This ability can be useful if a user script creates one or more data URIs and then opens them. Augmenting the URIs with some extra marking can cause specific user scripts to run in their windows. For example, a user script can create a data URI that contains a HTML table and trigger a user script for it that allows the user sort it.
