This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/apisix-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new aae53d8 Deploy to GitHub pages
aae53d8 is described below
commit aae53d84b17c056e9adb028765f443cb6a0e72ce
Author: github-actions[bot]
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Fri Dec 11 09:04:42 2020 +0000
Deploy to GitHub pages
---
apisix/admin-api.html | 11 ++++++-----
apisix/admin-api/index.html | 11 ++++++-----
apisix/aws.html | 2 +-
apisix/aws/index.html | 2 +-
apisix/plugins/kafka-logger.html | 2 +-
apisix/plugins/kafka-logger/index.html | 2 +-
apisix/plugins/response-rewrite.html | 2 +-
apisix/plugins/response-rewrite/index.html | 2 +-
apisix/plugins/sls-logger.html | 2 +-
apisix/plugins/sls-logger/index.html | 2 +-
apisix/plugins/tcp-logger.html | 2 +-
apisix/plugins/tcp-logger/index.html | 2 +-
apisix/plugins/udp-logger.html | 2 +-
apisix/plugins/udp-logger/index.html | 2 +-
apisix/zh-cn/admin-api.html | 6 +++---
apisix/zh-cn/admin-api/index.html | 6 +++---
16 files changed, 30 insertions(+), 28 deletions(-)
diff --git a/apisix/admin-api.html b/apisix/admin-api.html
index d874438..4b60b5b 100644
--- a/apisix/admin-api.html
+++ b/apisix/admin-api.html
@@ -71,11 +71,12 @@
<tbody>
<tr><td>name</td><td>False</td><td>Auxiliary</td><td>Identifies route
names.</td><td>customer-xxxx</td></tr>
<tr><td>desc</td><td>False</td><td>Auxiliary</td><td>route description, usage
scenarios, and more.</td><td>customer xxxx</td></tr>
-<tr><td>uri</td><td>True</td><td>Match Rules</td><td>In addition to full
matching such as <code>/foo/bar</code>、<code>/foo/gloo</code>, using different
<a href="/apisix/architecture-design#router">Router</a> allows more advanced
matching, see <a href="/apisix/architecture-design#router">Router</a> for
more.</td><td>"/hello"</td></tr>
-<tr><td>host</td><td>False</td><td>Match Rules</td><td>Currently requesting a
domain name, such as <code>foo.com</code>; pan-domain names such as
<code>*.foo.com</code> are also supported.</td><td>"foo.com"</td></tr>
-<tr><td>hosts</td><td>False</td><td>Match Rules</td><td>The <code>host</code>
in the form of a list means that multiple different hosts are allowed, and
match any one of them.</td><td>{"foo.com",
"*.bar.com"}</td></tr>
-<tr><td>remote_addr</td><td>False</td><td>Match Rules</td><td>The client
requests an IP address: <code>192.168.1.101</code>, <code>192.168.1.102</code>,
and CIDR format support <code>192.168.1.0/24</code>. In particular, APISIX also
fully supports IPv6 address matching: <code>::1</code>, <code>fe80::1</code>,
<code>fe80::1/64</code>, etc.</td><td>"192.168.1.0/24"</td></tr>
-<tr><td>remote_addrs</td><td>False</td><td>Match Rules</td><td>The
<code>remote_addr</code> in the form of a list indicates that multiple
different IP addresses are allowed, and match any one of
them.</td><td>{"127.0.0.1", "192.0.0.0/8",
"::1"}</td></tr>
+<tr><td>uri</td><td>True, can't be used with <code>uris</code></td><td>Match
Rules</td><td>In addition to full matching such as
<code>/foo/bar</code>、<code>/foo/gloo</code>, using different <a
href="/apisix/architecture-design#router">Router</a> allows more advanced
matching, see <a href="/apisix/architecture-design#router">Router</a> for
more.</td><td>"/hello"</td></tr>
+<tr><td>uris</td><td>True, can't be used with <code>uri</code></td><td>Match
Rules</td><td>The <code>uri</code> in the form of a non-empty list means that
multiple different uris are allowed, and match any one of
them.</td><td>["/hello", "/word"]</td></tr>
+<tr><td>host</td><td>False, can't be used with
<code>hosts</code></td><td>Match Rules</td><td>Currently requesting a domain
name, such as <code>foo.com</code>; PAN domain names such as
<code>*.foo.com</code> are also supported.</td><td>"foo.com"</td></tr>
+<tr><td>hosts</td><td>False, can't be used with
<code>host</code></td><td>Match Rules</td><td>The <code>host</code> in the form
of a non-empty list means that multiple different hosts are allowed, and match
any one of them.</td><td>{"foo.com", "*.bar.com"}</td></tr>
+<tr><td>remote_addr</td><td>False, can't be used with
<code>remote_addrs</code></td><td>Match Rules</td><td>The client requests an IP
address: <code>192.168.1.101</code>, <code>192.168.1.102</code>, and CIDR
format support <code>192.168.1.0/24</code>. In particular, APISIX also fully
supports IPv6 address matching: <code>::1</code>, <code>fe80::1</code>,
<code>fe80::1/64</code>, etc.</td><td>"192.168.1.0/24"</td></tr>
+<tr><td>remote_addrs</td><td>False, can't be used with
<code>remote_addr</code></td><td>Match Rules</td><td>The
<code>remote_addr</code> in the form of a non-empty list indicates that
multiple different IP addresses are allowed, and match any one of
them.</td><td>{"127.0.0.1", "192.0.0.0/8",
"::1"}</td></tr>
<tr><td>methods</td><td>False</td><td>Match Rules</td><td>If empty or without
this option, there are no <code>method</code> restrictions, and it can be a
combination of one or more:
<code>GET</code>,<code>POST</code>,<code>PUT</code>,<code>DELETE</code>,<code>PATCH</code>,
<code>HEAD</code>,<code>OPTIONS</code>,<code>CONNECT</code>,<code>TRACE</code>.</td><td>{"GET",
"POST"}</td></tr>
<tr><td>priority</td><td>False</td><td>Match Rules</td><td>If different routes
contain the same <code>uri</code>, determine which route is matched first based
on the attribute<code>priority</code>. Larger value means higher priority. The
default value is 0.</td><td>priority = 10</td></tr>
<tr><td>vars</td><td>False</td><td>Match Rules</td><td>A list of one or more
<code>{var, operator, val}</code> elements, like this: <code>{{var, operator,
val}, {var, operator, val}, ...}}</code>. For example:
<code>{"arg_name", "==", "json"}</code> means
that the current request parameter <code>name</code> is <code>json</code>. The
<code>var</code> here is consistent with the internal variable name of Nginx,
so you can also use <code>request_uri</code>, <co [...]
diff --git a/apisix/admin-api/index.html b/apisix/admin-api/index.html
index d874438..4b60b5b 100644
--- a/apisix/admin-api/index.html
+++ b/apisix/admin-api/index.html
@@ -71,11 +71,12 @@
<tbody>
<tr><td>name</td><td>False</td><td>Auxiliary</td><td>Identifies route
names.</td><td>customer-xxxx</td></tr>
<tr><td>desc</td><td>False</td><td>Auxiliary</td><td>route description, usage
scenarios, and more.</td><td>customer xxxx</td></tr>
-<tr><td>uri</td><td>True</td><td>Match Rules</td><td>In addition to full
matching such as <code>/foo/bar</code>、<code>/foo/gloo</code>, using different
<a href="/apisix/architecture-design#router">Router</a> allows more advanced
matching, see <a href="/apisix/architecture-design#router">Router</a> for
more.</td><td>"/hello"</td></tr>
-<tr><td>host</td><td>False</td><td>Match Rules</td><td>Currently requesting a
domain name, such as <code>foo.com</code>; pan-domain names such as
<code>*.foo.com</code> are also supported.</td><td>"foo.com"</td></tr>
-<tr><td>hosts</td><td>False</td><td>Match Rules</td><td>The <code>host</code>
in the form of a list means that multiple different hosts are allowed, and
match any one of them.</td><td>{"foo.com",
"*.bar.com"}</td></tr>
-<tr><td>remote_addr</td><td>False</td><td>Match Rules</td><td>The client
requests an IP address: <code>192.168.1.101</code>, <code>192.168.1.102</code>,
and CIDR format support <code>192.168.1.0/24</code>. In particular, APISIX also
fully supports IPv6 address matching: <code>::1</code>, <code>fe80::1</code>,
<code>fe80::1/64</code>, etc.</td><td>"192.168.1.0/24"</td></tr>
-<tr><td>remote_addrs</td><td>False</td><td>Match Rules</td><td>The
<code>remote_addr</code> in the form of a list indicates that multiple
different IP addresses are allowed, and match any one of
them.</td><td>{"127.0.0.1", "192.0.0.0/8",
"::1"}</td></tr>
+<tr><td>uri</td><td>True, can't be used with <code>uris</code></td><td>Match
Rules</td><td>In addition to full matching such as
<code>/foo/bar</code>、<code>/foo/gloo</code>, using different <a
href="/apisix/architecture-design#router">Router</a> allows more advanced
matching, see <a href="/apisix/architecture-design#router">Router</a> for
more.</td><td>"/hello"</td></tr>
+<tr><td>uris</td><td>True, can't be used with <code>uri</code></td><td>Match
Rules</td><td>The <code>uri</code> in the form of a non-empty list means that
multiple different uris are allowed, and match any one of
them.</td><td>["/hello", "/word"]</td></tr>
+<tr><td>host</td><td>False, can't be used with
<code>hosts</code></td><td>Match Rules</td><td>Currently requesting a domain
name, such as <code>foo.com</code>; PAN domain names such as
<code>*.foo.com</code> are also supported.</td><td>"foo.com"</td></tr>
+<tr><td>hosts</td><td>False, can't be used with
<code>host</code></td><td>Match Rules</td><td>The <code>host</code> in the form
of a non-empty list means that multiple different hosts are allowed, and match
any one of them.</td><td>{"foo.com", "*.bar.com"}</td></tr>
+<tr><td>remote_addr</td><td>False, can't be used with
<code>remote_addrs</code></td><td>Match Rules</td><td>The client requests an IP
address: <code>192.168.1.101</code>, <code>192.168.1.102</code>, and CIDR
format support <code>192.168.1.0/24</code>. In particular, APISIX also fully
supports IPv6 address matching: <code>::1</code>, <code>fe80::1</code>,
<code>fe80::1/64</code>, etc.</td><td>"192.168.1.0/24"</td></tr>
+<tr><td>remote_addrs</td><td>False, can't be used with
<code>remote_addr</code></td><td>Match Rules</td><td>The
<code>remote_addr</code> in the form of a non-empty list indicates that
multiple different IP addresses are allowed, and match any one of
them.</td><td>{"127.0.0.1", "192.0.0.0/8",
"::1"}</td></tr>
<tr><td>methods</td><td>False</td><td>Match Rules</td><td>If empty or without
this option, there are no <code>method</code> restrictions, and it can be a
combination of one or more:
<code>GET</code>,<code>POST</code>,<code>PUT</code>,<code>DELETE</code>,<code>PATCH</code>,
<code>HEAD</code>,<code>OPTIONS</code>,<code>CONNECT</code>,<code>TRACE</code>.</td><td>{"GET",
"POST"}</td></tr>
<tr><td>priority</td><td>False</td><td>Match Rules</td><td>If different routes
contain the same <code>uri</code>, determine which route is matched first based
on the attribute<code>priority</code>. Larger value means higher priority. The
default value is 0.</td><td>priority = 10</td></tr>
<tr><td>vars</td><td>False</td><td>Match Rules</td><td>A list of one or more
<code>{var, operator, val}</code> elements, like this: <code>{{var, operator,
val}, {var, operator, val}, ...}}</code>. For example:
<code>{"arg_name", "==", "json"}</code> means
that the current request parameter <code>name</code> is <code>json</code>. The
<code>var</code> here is consistent with the internal variable name of Nginx,
so you can also use <code>request_uri</code>, <co [...]
diff --git a/apisix/aws.html b/apisix/aws.html
index 8e245d8..46413e0 100644
--- a/apisix/aws.html
+++ b/apisix/aws.html
@@ -223,7 +223,7 @@ apiSix.ApiSixServiceServiceURLF6EC7872 =
http://apiSi-ApiSi-123HOROQKWZKA-126832
<p>Open the <code>apiSix.ApiSixDashboardURL</code> URL and log in to configure
your <strong>APISIX</strong> in AWS China region.</p>
<p><em>TBD</em></p>
<h2><a class="anchor" aria-hidden="true"
id="decouple-apisix-and-etcd3-on-aws"></a><a
href="#decouple-apisix-and-etcd3-on-aws" aria-hidden="true"
class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16"
version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4
9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2
3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4
9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13. [...]
-<p>For high availability and state consistency consideration, you might be
interested to decouple the <strong>etcd3</strong> as a seperate cluster from
<strong>APISIX</strong> not only for performance but also high availability and
faught tolerance yet with highly reliable state consistency.</p>
+<p>For high availability and state consistency consideration, you might be
interested to decouple the <strong>etcd3</strong> as a separate cluster from
<strong>APISIX</strong> not only for performance but also high availability and
fault tolerance yet with highly reliable state consistency.</p>
<p><em>TBD</em></p>
</span></div></article></div><div class="docs-prevnext"></div></div></div><nav
class="onPageNav"><ul class="toc-headings"><li><a
href="#architecture">Architecture</a></li><li><a
href="#generate-an-aws-cdk-project-with-projen">Generate an AWS CDK project
with <code>projen</code></a></li><li><a href="#update-srcmaints">update
<code>src/main.ts</code></a></li><li><a
href="#deploy-the-apisix-stack-with-aws-cdk">Deploy the APISIX Stack with AWS
CDK</a><ul class="toc-headings"><li><a href="#co [...]
document.addEventListener('keyup', function(e) {
diff --git a/apisix/aws/index.html b/apisix/aws/index.html
index 8e245d8..46413e0 100644
--- a/apisix/aws/index.html
+++ b/apisix/aws/index.html
@@ -223,7 +223,7 @@ apiSix.ApiSixServiceServiceURLF6EC7872 =
http://apiSi-ApiSi-123HOROQKWZKA-126832
<p>Open the <code>apiSix.ApiSixDashboardURL</code> URL and log in to configure
your <strong>APISIX</strong> in AWS China region.</p>
<p><em>TBD</em></p>
<h2><a class="anchor" aria-hidden="true"
id="decouple-apisix-and-etcd3-on-aws"></a><a
href="#decouple-apisix-and-etcd3-on-aws" aria-hidden="true"
class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16"
version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4
9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2
3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4
9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13. [...]
-<p>For high availability and state consistency consideration, you might be
interested to decouple the <strong>etcd3</strong> as a seperate cluster from
<strong>APISIX</strong> not only for performance but also high availability and
faught tolerance yet with highly reliable state consistency.</p>
+<p>For high availability and state consistency consideration, you might be
interested to decouple the <strong>etcd3</strong> as a separate cluster from
<strong>APISIX</strong> not only for performance but also high availability and
fault tolerance yet with highly reliable state consistency.</p>
<p><em>TBD</em></p>
</span></div></article></div><div class="docs-prevnext"></div></div></div><nav
class="onPageNav"><ul class="toc-headings"><li><a
href="#architecture">Architecture</a></li><li><a
href="#generate-an-aws-cdk-project-with-projen">Generate an AWS CDK project
with <code>projen</code></a></li><li><a href="#update-srcmaints">update
<code>src/main.ts</code></a></li><li><a
href="#deploy-the-apisix-stack-with-aws-cdk">Deploy the APISIX Stack with AWS
CDK</a><ul class="toc-headings"><li><a href="#co [...]
document.addEventListener('keyup', function(e) {
diff --git a/apisix/plugins/kafka-logger.html b/apisix/plugins/kafka-logger.html
index 4875993..29de3e2 100644
--- a/apisix/plugins/kafka-logger.html
+++ b/apisix/plugins/kafka-logger.html
@@ -37,7 +37,7 @@
<h2><a class="anchor" aria-hidden="true" id="name"></a><a href="#name"
aria-hidden="true" class="hash-link"><svg class="hash-link-icon"
aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16"
width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4
3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10
5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2
2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p><code>kafka-logger</code> is a plugin which works as a Kafka client driver
for the ngx_lua nginx module.</p>
<p>This will provide the ability to send Log data requests as JSON objects to
external Kafka clusters.</p>
-<p>This plugin provides the ability to push Log data as a batch to you're
external Kafka topics. In case if you did not recieve the log data don't worry
give it some time it will automatically send the logs after the timer function
expires in our Batch Processor.</p>
+<p>This plugin provides the ability to push Log data as a batch to you're
external Kafka topics. In case if you did not receive the log data don't worry
give it some time it will automatically send the logs after the timer function
expires in our Batch Processor.</p>
<p>For more info on Batch-Processor in Apache APISIX please refer.
<a href="/apisix/batch-processor">Batch-Processor</a></p>
<h2><a class="anchor" aria-hidden="true" id="attributes"></a><a
href="#attributes" aria-hidden="true" class="hash-link"><svg
class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0
0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5
0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2
3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4
9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1
[...]
diff --git a/apisix/plugins/kafka-logger/index.html
b/apisix/plugins/kafka-logger/index.html
index 4875993..29de3e2 100644
--- a/apisix/plugins/kafka-logger/index.html
+++ b/apisix/plugins/kafka-logger/index.html
@@ -37,7 +37,7 @@
<h2><a class="anchor" aria-hidden="true" id="name"></a><a href="#name"
aria-hidden="true" class="hash-link"><svg class="hash-link-icon"
aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16"
width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4
3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10
5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2
2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p><code>kafka-logger</code> is a plugin which works as a Kafka client driver
for the ngx_lua nginx module.</p>
<p>This will provide the ability to send Log data requests as JSON objects to
external Kafka clusters.</p>
-<p>This plugin provides the ability to push Log data as a batch to you're
external Kafka topics. In case if you did not recieve the log data don't worry
give it some time it will automatically send the logs after the timer function
expires in our Batch Processor.</p>
+<p>This plugin provides the ability to push Log data as a batch to you're
external Kafka topics. In case if you did not receive the log data don't worry
give it some time it will automatically send the logs after the timer function
expires in our Batch Processor.</p>
<p>For more info on Batch-Processor in Apache APISIX please refer.
<a href="/apisix/batch-processor">Batch-Processor</a></p>
<h2><a class="anchor" aria-hidden="true" id="attributes"></a><a
href="#attributes" aria-hidden="true" class="hash-link"><svg
class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0
0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5
0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2
3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4
9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1
[...]
diff --git a/apisix/plugins/response-rewrite.html
b/apisix/plugins/response-rewrite.html
index e7ad6f6..129f2f7 100644
--- a/apisix/plugins/response-rewrite.html
+++ b/apisix/plugins/response-rewrite.html
@@ -39,7 +39,7 @@
<p><strong>senario</strong>:</p>
<ol>
<li>can set <code>Access-Control-Allow-*</code> series field to support
CORS(Cross-origin Resource Sharing).</li>
-<li>we can set customized <code>status_code</code> and <code>Location</code>
field in header to achieve redirect, you can alse use <a
href="/apisix/plugins/redirect">redirect</a> plugin if you just want a
redirection.</li>
+<li>we can set customized <code>status_code</code> and <code>Location</code>
field in header to achieve redirect, you can also use <a
href="/apisix/plugins/redirect">redirect</a> plugin if you just want a
redirection.</li>
</ol>
<h2><a class="anchor" aria-hidden="true" id="attributes"></a><a
href="#attributes" aria-hidden="true" class="hash-link"><svg
class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0
0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5
0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2
3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4
9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1
[...]
<table>
diff --git a/apisix/plugins/response-rewrite/index.html
b/apisix/plugins/response-rewrite/index.html
index e7ad6f6..129f2f7 100644
--- a/apisix/plugins/response-rewrite/index.html
+++ b/apisix/plugins/response-rewrite/index.html
@@ -39,7 +39,7 @@
<p><strong>senario</strong>:</p>
<ol>
<li>can set <code>Access-Control-Allow-*</code> series field to support
CORS(Cross-origin Resource Sharing).</li>
-<li>we can set customized <code>status_code</code> and <code>Location</code>
field in header to achieve redirect, you can alse use <a
href="/apisix/plugins/redirect">redirect</a> plugin if you just want a
redirection.</li>
+<li>we can set customized <code>status_code</code> and <code>Location</code>
field in header to achieve redirect, you can also use <a
href="/apisix/plugins/redirect">redirect</a> plugin if you just want a
redirection.</li>
</ol>
<h2><a class="anchor" aria-hidden="true" id="attributes"></a><a
href="#attributes" aria-hidden="true" class="hash-link"><svg
class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0
0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5
0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2
3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4
9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1
[...]
<table>
diff --git a/apisix/plugins/sls-logger.html b/apisix/plugins/sls-logger.html
index dff3d32..c930de9 100644
--- a/apisix/plugins/sls-logger.html
+++ b/apisix/plugins/sls-logger.html
@@ -35,7 +35,7 @@
</ul>
<h2><a class="anchor" aria-hidden="true" id="name"></a><a href="#name"
aria-hidden="true" class="hash-link"><svg class="hash-link-icon"
aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16"
width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4
3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10
5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2
2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p><code>sls-logger</code> is a plugin which push Log data requests to ali
cloud <a
href="https://help.aliyun.com/document_detail/112903.html?spm=a2c4g.11186623.6.763.21321b47wcwt1u";>Log
Server</a> with <a href="https://tools.ietf.org/html/rfc5424";>RF5424</a>.</p>
-<p>This plugin provides the ability to push Log data as a batch to ali cloud
log service. In case if you did not recieve the log data don't worry give it
some time it will automatically send the logs after the timer function expires
in our Batch Processor.</p>
+<p>This plugin provides the ability to push Log data as a batch to ali cloud
log service. In case if you did not receive the log data don't worry give it
some time it will automatically send the logs after the timer function expires
in our Batch Processor.</p>
<p>For more info on Batch-Processor in Apache APISIX please refer
<a href="/apisix/batch-processor">Batch-Processor</a></p>
<h2><a class="anchor" aria-hidden="true" id="attributes"></a><a
href="#attributes" aria-hidden="true" class="hash-link"><svg
class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0
0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5
0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2
3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4
9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1
[...]
diff --git a/apisix/plugins/sls-logger/index.html
b/apisix/plugins/sls-logger/index.html
index dff3d32..c930de9 100644
--- a/apisix/plugins/sls-logger/index.html
+++ b/apisix/plugins/sls-logger/index.html
@@ -35,7 +35,7 @@
</ul>
<h2><a class="anchor" aria-hidden="true" id="name"></a><a href="#name"
aria-hidden="true" class="hash-link"><svg class="hash-link-icon"
aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16"
width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4
3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10
5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2
2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p><code>sls-logger</code> is a plugin which push Log data requests to ali
cloud <a
href="https://help.aliyun.com/document_detail/112903.html?spm=a2c4g.11186623.6.763.21321b47wcwt1u";>Log
Server</a> with <a href="https://tools.ietf.org/html/rfc5424";>RF5424</a>.</p>
-<p>This plugin provides the ability to push Log data as a batch to ali cloud
log service. In case if you did not recieve the log data don't worry give it
some time it will automatically send the logs after the timer function expires
in our Batch Processor.</p>
+<p>This plugin provides the ability to push Log data as a batch to ali cloud
log service. In case if you did not receive the log data don't worry give it
some time it will automatically send the logs after the timer function expires
in our Batch Processor.</p>
<p>For more info on Batch-Processor in Apache APISIX please refer
<a href="/apisix/batch-processor">Batch-Processor</a></p>
<h2><a class="anchor" aria-hidden="true" id="attributes"></a><a
href="#attributes" aria-hidden="true" class="hash-link"><svg
class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0
0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5
0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2
3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4
9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1
[...]
diff --git a/apisix/plugins/tcp-logger.html b/apisix/plugins/tcp-logger.html
index 4a1316e..12ea567 100644
--- a/apisix/plugins/tcp-logger.html
+++ b/apisix/plugins/tcp-logger.html
@@ -36,7 +36,7 @@
<h2><a class="anchor" aria-hidden="true" id="name"></a><a href="#name"
aria-hidden="true" class="hash-link"><svg class="hash-link-icon"
aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16"
width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4
3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10
5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2
2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p><code>tcp-logger</code> is a plugin which push Log data requests to TCP
servers.</p>
<p>This will provide the ability to send Log data requests as JSON objects to
Monitoring tools and other TCP servers.</p>
-<p>This plugin provides the ability to push Log data as a batch to you're
external TCP servers. In case if you did not recieve the log data don't worry
give it some time it will automatically send the logs after the timer function
expires in our Batch Processor.</p>
+<p>This plugin provides the ability to push Log data as a batch to you're
external TCP servers. In case if you did not receive the log data don't worry
give it some time it will automatically send the logs after the timer function
expires in our Batch Processor.</p>
<p>For more info on Batch-Processor in Apache APISIX please refer.
<a href="/apisix/batch-processor">Batch-Processor</a></p>
<h2><a class="anchor" aria-hidden="true" id="attributes"></a><a
href="#attributes" aria-hidden="true" class="hash-link"><svg
class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0
0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5
0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2
3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4
9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1
[...]
diff --git a/apisix/plugins/tcp-logger/index.html
b/apisix/plugins/tcp-logger/index.html
index 4a1316e..12ea567 100644
--- a/apisix/plugins/tcp-logger/index.html
+++ b/apisix/plugins/tcp-logger/index.html
@@ -36,7 +36,7 @@
<h2><a class="anchor" aria-hidden="true" id="name"></a><a href="#name"
aria-hidden="true" class="hash-link"><svg class="hash-link-icon"
aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16"
width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4
3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10
5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2
2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p><code>tcp-logger</code> is a plugin which push Log data requests to TCP
servers.</p>
<p>This will provide the ability to send Log data requests as JSON objects to
Monitoring tools and other TCP servers.</p>
-<p>This plugin provides the ability to push Log data as a batch to you're
external TCP servers. In case if you did not recieve the log data don't worry
give it some time it will automatically send the logs after the timer function
expires in our Batch Processor.</p>
+<p>This plugin provides the ability to push Log data as a batch to you're
external TCP servers. In case if you did not receive the log data don't worry
give it some time it will automatically send the logs after the timer function
expires in our Batch Processor.</p>
<p>For more info on Batch-Processor in Apache APISIX please refer.
<a href="/apisix/batch-processor">Batch-Processor</a></p>
<h2><a class="anchor" aria-hidden="true" id="attributes"></a><a
href="#attributes" aria-hidden="true" class="hash-link"><svg
class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0
0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5
0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2
3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4
9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1
[...]
diff --git a/apisix/plugins/udp-logger.html b/apisix/plugins/udp-logger.html
index 3af604c..e9a1ce6 100644
--- a/apisix/plugins/udp-logger.html
+++ b/apisix/plugins/udp-logger.html
@@ -36,7 +36,7 @@
<h2><a class="anchor" aria-hidden="true" id="name"></a><a href="#name"
aria-hidden="true" class="hash-link"><svg class="hash-link-icon"
aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16"
width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4
3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10
5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2
2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p><code>udp-logger</code> is a plugin which push Log data requests to UDP
servers.</p>
<p>This will provide the ability to send Log data requests as JSON objects to
Monitoring tools and other UDP servers.</p>
-<p>This plugin provides the ability to push Log data as a batch to you're
external UDP servers. In case if you did not recieve the log data don't worry
give it some time it will automatically send the logs after the timer function
expires in our Batch Processor.</p>
+<p>This plugin provides the ability to push Log data as a batch to you're
external UDP servers. In case if you did not receive the log data don't worry
give it some time it will automatically send the logs after the timer function
expires in our Batch Processor.</p>
<p>For more info on Batch-Processor in Apache APISIX please refer.
<a href="/apisix/batch-processor">Batch-Processor</a></p>
<h2><a class="anchor" aria-hidden="true" id="attributes"></a><a
href="#attributes" aria-hidden="true" class="hash-link"><svg
class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0
0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5
0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2
3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4
9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1
[...]
diff --git a/apisix/plugins/udp-logger/index.html
b/apisix/plugins/udp-logger/index.html
index 3af604c..e9a1ce6 100644
--- a/apisix/plugins/udp-logger/index.html
+++ b/apisix/plugins/udp-logger/index.html
@@ -36,7 +36,7 @@
<h2><a class="anchor" aria-hidden="true" id="name"></a><a href="#name"
aria-hidden="true" class="hash-link"><svg class="hash-link-icon"
aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16"
width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4
3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10
5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2
2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p><code>udp-logger</code> is a plugin which push Log data requests to UDP
servers.</p>
<p>This will provide the ability to send Log data requests as JSON objects to
Monitoring tools and other UDP servers.</p>
-<p>This plugin provides the ability to push Log data as a batch to you're
external UDP servers. In case if you did not recieve the log data don't worry
give it some time it will automatically send the logs after the timer function
expires in our Batch Processor.</p>
+<p>This plugin provides the ability to push Log data as a batch to you're
external UDP servers. In case if you did not receive the log data don't worry
give it some time it will automatically send the logs after the timer function
expires in our Batch Processor.</p>
<p>For more info on Batch-Processor in Apache APISIX please refer.
<a href="/apisix/batch-processor">Batch-Processor</a></p>
<h2><a class="anchor" aria-hidden="true" id="attributes"></a><a
href="#attributes" aria-hidden="true" class="hash-link"><svg
class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0
0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5
0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2
3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4
9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1
[...]
diff --git a/apisix/zh-cn/admin-api.html b/apisix/zh-cn/admin-api.html
index fca8e5d..81f45e9 100644
--- a/apisix/zh-cn/admin-api.html
+++ b/apisix/zh-cn/admin-api.html
@@ -71,7 +71,7 @@
</thead>
<tbody>
<tr><td>uri</td><td>与 <code>uris</code> 二选一</td><td>匹配规则</td><td>除了如
<code>/foo/bar</code>、<code>/foo/gloo</code> 这种全量匹配外，使用不同 <a
href="/apisix/zh-cn/architecture-design#router">Router</a> 还允许更高级匹配，更多见 <a
href="/apisix/zh-cn/architecture-design#router">Router</a>。</td><td>"/hello"</td></tr>
-<tr><td>uris</td><td>与 <code>uri</code> 二选一</td><td>匹配规则</td><td>数组形式，可以匹配多个
<code>uri</code></td><td>["/hello", "/world"]</td></tr>
+<tr><td>uris</td><td>与 <code>uri</code> 二选一</td><td>匹配规则</td><td>非空数组形式，可以匹配多个
<code>uri</code></td><td>["/hello", "/world"]</td></tr>
<tr><td>plugins</td><td><code>plugins</code>、<code>script</code>、<code>upstream</code>/<code>upstream_id</code>、<code>service_id</code>至少选择一个</td><td>Plugin</td><td>详见
<a
href="/apisix/zh-cn/architecture-design#plugin">Plugin</a></td><td></td></tr>
<tr><td>script</td><td><code>plugins</code>、<code>script</code>、<code>upstream</code>/<code>upstream_id</code>、<code>service_id</code>至少选择一个</td><td>Script</td><td>详见
<a
href="/apisix/zh-cn/architecture-design#script">Script</a></td><td></td></tr>
<tr><td>upstream</td><td><code>plugins</code>、<code>script</code>、<code>upstream</code>/<code>upstream_id</code>、<code>service_id</code>至少选择一个</td><td>Upstream</td><td>启用的
Upstream 配置，详见 <a
href="/apisix/zh-cn/architecture-design#upstream">Upstream</a></td><td></td></tr>
@@ -81,9 +81,9 @@
<tr><td>name</td><td>可选</td><td>辅助</td><td>标识路由名称</td><td>route-xxxx</td></tr>
<tr><td>desc</td><td>可选</td><td>辅助</td><td>标识描述、使用场景等。</td><td>客户
xxxx</td></tr>
<tr><td>host</td><td>可选</td><td>匹配规则</td><td>当前请求域名，比如
<code>foo.com</code>；也支持泛域名，比如
<code>*.foo.com</code>。</td><td>"foo.com"</td></tr>
-<tr><td>hosts</td><td>可选</td><td>匹配规则</td><td>列表形态的
<code>host</code>，表示允许有多个不同
<code>host</code>，匹配其中任意一个即可。</td><td>{"foo.com",
"*.bar.com"}</td></tr>
+<tr><td>hosts</td><td>可选</td><td>匹配规则</td><td>非空列表形态的
<code>host</code>，表示允许有多个不同
<code>host</code>，匹配其中任意一个即可。</td><td>{"foo.com",
"*.bar.com"}</td></tr>
<tr><td>remote_addr</td><td>可选</td><td>匹配规则</td><td>客户端请求 IP 地址:
<code>192.168.1.101</code>、<code>192.168.1.102</code> 以及 CIDR 格式的支持
<code>192.168.1.0/24</code>。特别的，APISIX 也完整支持 IPv6
地址匹配：<code>::1</code>，<code>fe80::1</code>, <code>fe80::1/64</code>
等。</td><td>"192.168.1.0/24"</td></tr>
-<tr><td>remote_addrs</td><td>可选</td><td>匹配规则</td><td>列表形态的
<code>remote_addr</code>，表示允许有多个不同 IP
地址，符合其中任意一个即可。</td><td>{"127.0.0.1", "192.0.0.0/8",
"::1"}</td></tr>
+<tr><td>remote_addrs</td><td>可选</td><td>匹配规则</td><td>非空列表形态的
<code>remote_addr</code>，表示允许有多个不同 IP
地址，符合其中任意一个即可。</td><td>{"127.0.0.1", "192.0.0.0/8",
"::1"}</td></tr>
<tr><td>methods</td><td>可选</td><td>匹配规则</td><td>如果为空或没有该选项，代表没有任何
<code>method</code> 限制，也可以是一个或多个的组合：<code>GET</code>, <code>POST</code>,
<code>PUT</code>, <code>DELETE</code>, <code>PATCH</code>, <code>HEAD</code>,
<code>OPTIONS</code>，<code>CONNECT</code>，<code>TRACE</code>。</td><td>{"GET",
"POST"}</td></tr>
<tr><td>priority</td><td>可选</td><td>匹配规则</td><td>如果不同路由包含相同
<code>uri</code>，根据属性 <code>priority</code> 确定哪个 <code>route</code>
被优先匹配，值越大优先级越高，默认值为 0。</td><td>priority = 10</td></tr>
<tr><td>vars</td><td>可选</td><td>匹配规则</td><td>由一个或多个<code>{var, operator,
val}</code>元素组成的列表，类似这样：<code>{{var, operator, val}, {var, operator, val},
...}}</code>。例如：<code>{"arg_name", "==",
"json"}</code>，表示当前请求参数 <code>name</code> 是 <code>json</code>。这里的
<code>var</code> 与 Nginx 内部自身变量命名是保持一致，所以也可以使用
<code>request_uri</code>、<code>host</code> 等；对于 <code>operator</code>
部分，目前已支持的运算符有
<code>==</code>、<code>~=</code>、<code>></code>、<code><</code> 和 <code>
[...]
diff --git a/apisix/zh-cn/admin-api/index.html
b/apisix/zh-cn/admin-api/index.html
index fca8e5d..81f45e9 100644
--- a/apisix/zh-cn/admin-api/index.html
+++ b/apisix/zh-cn/admin-api/index.html
@@ -71,7 +71,7 @@
</thead>
<tbody>
<tr><td>uri</td><td>与 <code>uris</code> 二选一</td><td>匹配规则</td><td>除了如
<code>/foo/bar</code>、<code>/foo/gloo</code> 这种全量匹配外，使用不同 <a
href="/apisix/zh-cn/architecture-design#router">Router</a> 还允许更高级匹配，更多见 <a
href="/apisix/zh-cn/architecture-design#router">Router</a>。</td><td>"/hello"</td></tr>
-<tr><td>uris</td><td>与 <code>uri</code> 二选一</td><td>匹配规则</td><td>数组形式，可以匹配多个
<code>uri</code></td><td>["/hello", "/world"]</td></tr>
+<tr><td>uris</td><td>与 <code>uri</code> 二选一</td><td>匹配规则</td><td>非空数组形式，可以匹配多个
<code>uri</code></td><td>["/hello", "/world"]</td></tr>
<tr><td>plugins</td><td><code>plugins</code>、<code>script</code>、<code>upstream</code>/<code>upstream_id</code>、<code>service_id</code>至少选择一个</td><td>Plugin</td><td>详见
<a
href="/apisix/zh-cn/architecture-design#plugin">Plugin</a></td><td></td></tr>
<tr><td>script</td><td><code>plugins</code>、<code>script</code>、<code>upstream</code>/<code>upstream_id</code>、<code>service_id</code>至少选择一个</td><td>Script</td><td>详见
<a
href="/apisix/zh-cn/architecture-design#script">Script</a></td><td></td></tr>
<tr><td>upstream</td><td><code>plugins</code>、<code>script</code>、<code>upstream</code>/<code>upstream_id</code>、<code>service_id</code>至少选择一个</td><td>Upstream</td><td>启用的
Upstream 配置，详见 <a
href="/apisix/zh-cn/architecture-design#upstream">Upstream</a></td><td></td></tr>
@@ -81,9 +81,9 @@
<tr><td>name</td><td>可选</td><td>辅助</td><td>标识路由名称</td><td>route-xxxx</td></tr>
<tr><td>desc</td><td>可选</td><td>辅助</td><td>标识描述、使用场景等。</td><td>客户
xxxx</td></tr>
<tr><td>host</td><td>可选</td><td>匹配规则</td><td>当前请求域名，比如
<code>foo.com</code>；也支持泛域名，比如
<code>*.foo.com</code>。</td><td>"foo.com"</td></tr>
-<tr><td>hosts</td><td>可选</td><td>匹配规则</td><td>列表形态的
<code>host</code>，表示允许有多个不同
<code>host</code>，匹配其中任意一个即可。</td><td>{"foo.com",
"*.bar.com"}</td></tr>
+<tr><td>hosts</td><td>可选</td><td>匹配规则</td><td>非空列表形态的
<code>host</code>，表示允许有多个不同
<code>host</code>，匹配其中任意一个即可。</td><td>{"foo.com",
"*.bar.com"}</td></tr>
<tr><td>remote_addr</td><td>可选</td><td>匹配规则</td><td>客户端请求 IP 地址:
<code>192.168.1.101</code>、<code>192.168.1.102</code> 以及 CIDR 格式的支持
<code>192.168.1.0/24</code>。特别的，APISIX 也完整支持 IPv6
地址匹配：<code>::1</code>，<code>fe80::1</code>, <code>fe80::1/64</code>
等。</td><td>"192.168.1.0/24"</td></tr>
-<tr><td>remote_addrs</td><td>可选</td><td>匹配规则</td><td>列表形态的
<code>remote_addr</code>，表示允许有多个不同 IP
地址，符合其中任意一个即可。</td><td>{"127.0.0.1", "192.0.0.0/8",
"::1"}</td></tr>
+<tr><td>remote_addrs</td><td>可选</td><td>匹配规则</td><td>非空列表形态的
<code>remote_addr</code>，表示允许有多个不同 IP
地址，符合其中任意一个即可。</td><td>{"127.0.0.1", "192.0.0.0/8",
"::1"}</td></tr>
<tr><td>methods</td><td>可选</td><td>匹配规则</td><td>如果为空或没有该选项，代表没有任何
<code>method</code> 限制，也可以是一个或多个的组合：<code>GET</code>, <code>POST</code>,
<code>PUT</code>, <code>DELETE</code>, <code>PATCH</code>, <code>HEAD</code>,
<code>OPTIONS</code>，<code>CONNECT</code>，<code>TRACE</code>。</td><td>{"GET",
"POST"}</td></tr>
<tr><td>priority</td><td>可选</td><td>匹配规则</td><td>如果不同路由包含相同
<code>uri</code>，根据属性 <code>priority</code> 确定哪个 <code>route</code>
被优先匹配，值越大优先级越高，默认值为 0。</td><td>priority = 10</td></tr>
<tr><td>vars</td><td>可选</td><td>匹配规则</td><td>由一个或多个<code>{var, operator,
val}</code>元素组成的列表，类似这样：<code>{{var, operator, val}, {var, operator, val},
...}}</code>。例如：<code>{"arg_name", "==",
"json"}</code>，表示当前请求参数 <code>name</code> 是 <code>json</code>。这里的
<code>var</code> 与 Nginx 内部自身变量命名是保持一致，所以也可以使用
<code>request_uri</code>、<code>host</code> 等；对于 <code>operator</code>
部分，目前已支持的运算符有
<code>==</code>、<code>~=</code>、<code>></code>、<code><</code> 和 <code>
[...]
