-
Notifications
You must be signed in to change notification settings - Fork 4
/
298.txt
25 lines (19 loc) · 1.14 KB
/
298.txt
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
[FIG(quote)[
[FIGCAPTION[
[1] [CITE[Network Communications - Google Chrome]]
( ([TIME[2016-06-16 19:52:04 +09:00]]))
<https://developer.chrome.com/apps/app_network>
]FIGCAPTION]
> The syntax of socket "host-pattern" entries follows these rules:
> <host-pattern> := <host> | ':' <port> | <host> ':' <port>
> <host> := '*' | '*.' <anychar except '/' and '*'>+
> <port> := '*' | <port number between 1 and 65535>)
]FIG]
[FIG(quote)[
[FIGCAPTION[
[2] [CITE[chrome.webNavigation - Google Chrome]]
( ([TIME[2016-06-18 01:38:52 +09:00]]))
<https://developer.chrome.com/extensions/webNavigation>
]FIGCAPTION]
> Matches if the host name of the URL contains a specified string. To test whether a host name component has a prefix 'foo', use hostContains: '.foo'. This matches 'www.foobar.com' and 'foo.com', because an implicit dot is added at the beginning of the host name. Similarly, hostContains can be used to match against component suffix ('foo.') and to exactly match against components ('.foo.'). Suffix- and exact-matching for the last components need to be done separately using hostSuffix, because no implicit dot is added at the end of the host name.
]FIG]