Resource Description Framework (RDF) Model and Syntax Specification
3.4. Containers Defined By A URI Patternhttp://www.w3.org/TR/1999/REC-rdf-syntax-19990222/#URIPrefix
[14] Service Modeling Language Interchange Format Version 1.1 ( 版) http://www.w3.org/TR/2009/REC-sml-if-20090512/#URI_prefix_matching
[6]
SML Interchange Format Version 1.0 (2007-03-08 05:32:26 +09:00 版) http://www.w3.org/Submission/2007/SUBM-sml-if-20070321/#URI_prefix_matching
(名無しさん)
[7]
Protocol for Web Description Resources (POWDER): Web Description Resources Datatypes (WDRD) (2007-09-27 06:24:18 +09:00 版) http://www.w3.org/TR/2007/WD-powder-xsd-20070925/
(名無しさん)
[8]
Service Modeling Language Interchange Format Version 1.1 (2007-09-27 00:24:13 +09:00 版) http://www.w3.org/TR/2007/WD-sml-if-20070926/#URI_prefix_matching
(名無しさん)
The meaning of '*' depends on whether it's in the scheme, host, or path part. If the scheme is *, then it matches either http or https. If the host is just *, then it matches any host. If the host is *.hostname, then it matches the specified host or any of its subdomains. In the path section, each '*' matches 0 or more characters. The following table shows some valid patterns.
The field takes an array of URL patterns representing hosts which the application should be able to access. The values can be fully qualified host names, like this:
[38] This morning's work. · w3c/webappsec-csp@d669817
( 版)
https://github.com/w3c/webappsec-csp/commit/d6698170c8eede388bd351773dada7b633988be8
[39] oEmbed
( 版)
http://oembed.com/
The URL scheme may contain one or more wildcards (specified with an asterisk). Wildcards may be present in the domain portion of the URL, or in the path. Within the domain portion, wildcards may only be used for subdomains. Wildcards may not be used in the scheme (to support HTTP and HTTPS, provide two url/endpoint pairs).
Some examples:
http://www.flickr.com/photos/* OK
http://www.flickr.com/photos/*/foo/ OK
http://*.flickr.com/photos/* OK
http://*.com/photos/* NOT OK
*://www.flickr.com/photos/* NOT OK
[41] BEACON link dump format
( 版)
https://gbv.github.io/beaconspec/beacon.html
A URI pattern in this specification is an URI Template, as defined in [RFC6570], with all template expressions being either {ID} for simple string expansion or {+ID} for reserved expansion.
[42] Match Patterns - Google Chrome
( 版)
https://developer.chrome.com/extensions/match_patterns
[44] cURL - How To Use
( ())
https://curl.haxx.se/docs/manpage.html
You can specify multiple URLs or parts of URLs by writing part sets within braces as in:
http://site.{one,two,three}.com
or you can get sequences of alphanumeric series by using [] as in:
ftp://ftp.example.com/file[1-100].txt
ftp://ftp.example.com/file[001-100].txt (with leading zeros)
ftp://ftp.example.com/file[a-z].txt
Nested sequences are not supported, but you can use several ones next to each other:
You can specify any amount of URLs on the command line. They will be fetched in a sequential manner in the specified order.
You can specify a step counter for the ranges to get every Nth number or letter:
http://example.com/file[1-100:10].txt
http://example.com/file[a-z:2].txt
[45] cURL - How To Use
( ())
https://curl.haxx.se/docs/manpage.html#-g
-g, --globoff
This option switches off the "URL globbing parser". When you set this option, you can specify URLs that contain the letters {}[] without having them being interpreted by curl itself. Note that these letters are not normal legal URL contents but they should be encoded according to the URI standard.
[46] Match patterns - Mozilla | MDN
( ())
https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Match_patterns
[47] chrome.proxy - Google Chrome
( ())
https://developer.chrome.com/extensions/proxy
Bypass list
Individual servers may be excluded from being proxied with the bypassList. This list may contain the following entries:
[<scheme>://]<host-pattern>[:<port>]
Match all hostnames that match the pattern <host-pattern>. A leading "." is interpreted as a "*.".
Conceptually this is the similar to the first case, but with special cases to handle IP literal canonicalization. For example, matching on "[0:0:0::1]" is the same as matching on "[::1]" because the IPv6 canonicalization is done internally.
This tells chrome to bypass any specified proxy for the given semi-colon-separated list of hosts. This flag must be used (or rather, only has an effect) in tandem with --proxy-server.
Note that trailing-domain matching doesn't require "." separators so "*google.com" will match "igoogle.com" for example.
[49] Sniffly for ports.
(mikewest著, )
https://github.com/w3c/webappsec-csp/commit/22d08b990290e49f5a666fad08de16d75bb369e7
[50] Part 2.3: What is an intersection of the two source expressions? (#144)
(Sun77789著, )
https://github.com/w3c/webappsec-csp/commit/5da961eb94294f739207e183d21cbe19d3516fa3
The url-filter string format is a strict subset of JavaScript regular expressions, shown in Table 1. Syntactically, everything supported by JavaScript is reserved but only the subset will be accepted by the parser. An unsupported expression results in a parse error.
[82] Editorial: update the standard for the WHATWG move by domenic · Pull Request #193 · whatwg/urlpattern · GitHub, https://github.com/whatwg/urlpattern/pull/193