Syntax: <Proxy wildcard-url> ...</Proxy>

Directives placed in <Proxy> sections apply only to matching proxied content. Shell-style wildcards are allowed.

<Proxy http://example.com/foo/*>

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 "*.".

Examples: "foobar.com", "*foobar.com", "*.foobar.com", "*foobar.com:99", "https://x.*.y.com:99".

Match pattern syntax

Here's the basic syntax:

<url-pattern> := <scheme>://<host><path>

<scheme> := '*' | 'http' | 'https' | 'file' | 'ftp' | 'chrome-extension'

<host> := '*' | '*.' <any char except '/' and '*'>+

<path> := '/' <any chars>

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:

"http://crosswalk-project.org/"

Or patterns with wild-card characters, such as:

"http://*.org/"

"https://*/"

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

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.

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:

  http://example.com/archive[1996-1999]/vol[1-4]/part{a,b,c}.html

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

-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.

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 "*.".

Examples: "foobar.com", "*foobar.com", "*.foobar.com", "*foobar.com:99", "https://x.*.y.com:99".

Pattern Matches Does not match

".foobar.com" "www.foobar.com" "foobar.com"

"*.foobar.com" "www.foobar.com" "foobar.com"

"foobar.com" "foobar.com" "www.foobar.com"

"*foobar.com" "foobar.com", "www.foobar.com", "foofoobar.com"

[<scheme>://]<ip-literal>[:<port>]

Match URLs that are IP address literals.

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.

Examples: "127.0.1", "[0:0::1]", "[::1]", "http://[::1]:99"

<ip-literal>/<prefix-length-in-bits>

Match any URL containing an IP literal within the given range. The IP range is specified using CIDR notation.

Examples: "192.168.1.1/16", "fefe:13::abc/33"

<local>

Match local addresses. An address is local if the host is "127.0.0.1", "::1", or "localhost".

Example: "<local>"

--proxy-bypass-list=(<trailing_domain>|<ip-address>)[:<port>][;...]

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.

また、サブドメインのワイルドカード (たとえば、https://*.microsoft.com) を含めることはできますが、ドメインのワイルドカード (たとえば、https://*.com や https://*.*) を含めることはできません。

android:host attribute with a domain URI pattern

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.

無効化リクエストには、無効にする 1 つまたは複数のオブジェクトを識別するパスパターンを指定します。/cat.jpg のように特定のパスを指定することも、/pictures/* のようにディレクトリ構造全体を指定することもできます。パスパターンには次の規則が適用されます。

パスパターンは / で始める必要があります。

? 、# は使用できません。

* は、/ に続く最後の文字として使用できますが、それ以外の場所では使用できません。

/* で終わる場合、先行する文字列は接頭辞になり、その接頭辞で始まるオブジェクトはすべて無効になります。

パスパターンは、URL のパス コンポーネント(ホスト名と任意の ? または # の間にあるすべての文字列)と比較されます。

URL にクエリ文字列(例: /images.php?image=fred.png)が含まれている場合、クエリ文字列だけが異なるオブジェクトを無効にすることはできません。 たとえば、2 つの画像(/images.php?image=fred.png と /images.php?image=barney.png)がある場合、fred.png だけを無効にすることはできません。images.php で提供されるすべての画像を無効にするには、パスパターンに /images.php を使用します。

<include> (optional)

A regular expression matching the URLs of pages that the generator is able to summarize.

<exclude> (optional)

A regular expression matching the URLs of pages that the generator is not able to summarize.

In your manifest, you can define your shareURL in this format:

"shareURL": "https://yoursite.com/share?u=%{url}&t=%{title}

Paths can contain * or :placeholders. A :placeholder matches anything except / while a * matches anything.