-
Notifications
You must be signed in to change notification settings - Fork 8
/
tut_match_patterns.html
276 lines (231 loc) · 6.13 KB
/
tut_match_patterns.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
---
layout: default-withsidebar
title: Match patterns
copyright: opera-google-ccby
originalsource: http://developer.chrome.com/trunk/extensions/match_patterns.html
---
<div id="gc-pagecontent">
<h2>Introduction</h2>
<p>
<a href="tut_content_scripts.html">Content scripts</a> operate on
a set of URLs defined by match patterns.
You can put one or more match patterns
in the <code>"matches"</code> part of
a content script's section of the manifest,
as well as in the <code>"exclude_matches"</code> section.
This page describes the match pattern syntax —
the rules you need to follow when you specify
which URLs your content script affects.
</p>
<h2>What match patterns are</h2>
<p>
A match pattern is essentially a URL
that begins with a permitted scheme (<code>http</code>,
<code>https</code>, <code>file</code>, <code>ftp</code>, or
<code>chrome-extension</code>),
and that can contain '<code>*</code>' characters.
The special pattern
<code><all_urls></code> matches any URL
that starts with a permitted scheme.
Each match pattern has 3 parts:</p>
</p>
<ul>
<li> <em>scheme</em> —
for example, <code>http</code> or <code>file</code>
or <code>*</code>
<p class="note">
<b>Note:</b>
Access to <code>file</code> URLs isn't automatic.
The user must visit the extensions management page
and opt in to <code>file</code> access for each extension that requests it.
</p>
</li>
<li> <em>host</em> —
for example, <code>www.google.com</code>
or <code>*.google.com</code>
or <code>*</code>;
if the scheme is <code>file</code>,
there is no <em>host</em> part
</li>
<li> <em>path</em> —
for example, <code>/*</code>, <code>/foo* </code>,
or <code>/foo/bar </code>
</li>
</ul>
<h2>Match pattern syntax</h2>
<p>Here's the basic syntax:</p>
<pre class="prettyprint">
<em><url-pattern></em> := <em><scheme></em>://<em><host></em><em><path></em>
<em><scheme></em> := '*' | 'http' | 'https' | 'file' | 'ftp' | 'chrome-extension'
<em><host></em> := '*' | '*.' <em><any char except '/' and '*'></em>+
<em><path></em> := '/' <em><any chars></em>
</pre>
<p>
The meaning of '<code>*</code>' depends on whether
it's in the <em>scheme</em>, <em>host</em>, or <em>path</em> part.
If the <em>scheme</em> is <code>*</code>,
then it matches either <code>http</code> or <code>https</code>.
If the <em>host</em> is just <code>*</code>,
then it matches any host.
If the <em>host</em> is <code>*.<em>hostname</em></code>,
then it matches the specified host or any of its subdomains.
In the <em>path</em> section,
each '<code>*</code>' matches 0 or more characters.
The following table shows some valid patterns.
</p>
<table class="simple">
<tbody>
<tr>
<th style="margin-left:0; padding-left:0">Pattern</th>
<th style="margin-left:0; padding-left:0">What it does</th>
<th style="margin-left:0; padding-left:0">Examples of matching URLs</th>
</tr>
<tr>
<td>
<code>http://*/*</code>
</td>
<td>Matches any URL that uses the <code>http</code> scheme</td>
<td>
http://www.google.com/<br>
http://example.org/foo/bar.html
</td>
</tr>
<tr>
<td>
<code>http://*/foo*</code>
</td>
<td>
Matches any URL that uses the <code>http</code> scheme, on any host,
as long as the path starts with <code>/foo</code>
</td>
<td>
http://example.com/foo/bar.html<br>
http://www.google.com/foo<b></b>
</td>
</tr>
<tr>
<td>
<code>https://*.google.com/foo*bar </code>
</td>
<td>
Matches any URL that uses the <code>https</code> scheme,
is on a google.com host
(such as www.google.com, docs.google.com, or google.com),
as long as the path starts with <code>/foo</code>
and ends with <code>bar</code>
</td>
<td>
http://www.google.com/foo/baz/bar<br>
http://docs.google.com/foobar
</td>
</tr>
<tr>
<td>
<code>http://example.org/foo/bar.html </code>
</td>
<td>Matches the specified URL</td>
<td>
http://example.org/foo/bar.html
</td>
</tr>
<tr>
<td>
<code>file:///foo*</code>
</td>
<td>Matches any local file whose path starts with <code>/foo</code>
</td>
<td>
file:///foo/bar.html<br>
file:///foo
</td>
</tr>
<tr>
<td>
<code>http://127.0.0.1/*</code>
</td>
<td>
Matches any URL that uses the <code>http</code> scheme
and is on the host 127.0.0.1
</td>
<td>
http://127.0.0.1/<br>
http://127.0.0.1/foo/bar.html
</td>
</tr>
<tr>
<td>
<code>*://mail.google.com/* </code>
</td>
<td>
Matches any URL that starts with
<code>http://mail.google.com</code> or
<code>https://mail.google.com</code>.
</td>
<td>
http://mail.google.com/foo/baz/bar<br>
https://mail.google.com/foobar
</td>
</tr>
<tr>
<td>
<code>chrome-extension://*/* </code>
</td>
<td>
Matches any URL pointing to an extension (the first <code>*</code>
represents a filter for extension IDs, the second for paths).
</td>
<td>
chrome-extension://askla...asdf/options.html
</td>
</tr>
<tr>
<td>
<code><all_urls></code>
</td>
<td>
Matches any URL that uses a permitted scheme.
(See the beginning of this section for the list of permitted
schemes.)
</td>
<td>
http://example.org/foo/bar.html<br>
file:///bar/baz.html
</td>
</tr>
</tbody>
</table>
<p>
Here are some examples of <em>invalid</em> pattern matches:
</p>
<table class="simple">
<tbody>
<tr>
<th style="margin-left:0; padding-left:0">Bad pattern</th>
<th style="margin-left:0; padding-left:0">Why it's bad</th>
</tr>
<tr>
<td><code>http://www.google.com</code></td>
<td>No <em>path</em></td>
</tr>
<tr>
<td><code>http://*foo/bar</code></td>
<td>'*' in the <em>host</em> can be followed only by a '.' or '/'</td>
</tr>
<tr>
<td><code>http://foo.*.bar/baz </code></td>
<td>If '*' is in the <em>host</em>, it must be the first character</td>
</tr>
<tr>
<td><code>http:/bar</code></td>
<td>Missing <em>scheme</em> separator ("/" should be "//")</td>
</tr>
<tr>
<td><code>foo://*</code></td>
<td>Invalid <em>scheme</em></td>
</tr>
</tbody>
</table>
<p>
Some schemes are not supported in all contexts.
</p>
</div>