This is an automated email from the ASF dual-hosted git repository.
Baoyuantop pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/apisix.git
The following commit(s) were added to refs/heads/master by this push:
new bc5a74f7b docs: update attach-consumer-label plugin documentation
(#13301)
bc5a74f7b is described below
commit bc5a74f7b8d880d63ef0d6f4978829e7dbb15d0c
Author: Yilia Lin <[email protected]>
AuthorDate: Wed May 6 09:58:27 2026 +0800
docs: update attach-consumer-label plugin documentation (#13301)
---
docs/en/latest/plugins/attach-consumer-label.md | 60 ++++++++++------------
docs/en/latest/plugins/response-rewrite.md | 8 +--
docs/zh/latest/plugins/attach-consumer-label.md | 68 ++++++++++++-------------
docs/zh/latest/plugins/response-rewrite.md | 26 +++++-----
4 files changed, 77 insertions(+), 85 deletions(-)
diff --git a/docs/en/latest/plugins/attach-consumer-label.md
b/docs/en/latest/plugins/attach-consumer-label.md
index ab0d8437a..2f5557d8e 100644
--- a/docs/en/latest/plugins/attach-consumer-label.md
+++ b/docs/en/latest/plugins/attach-consumer-label.md
@@ -3,8 +3,10 @@ title: attach-consumer-label
keywords:
- Apache APISIX
- API Gateway
- - API Consumer
-description: This article describes the Apache APISIX attach-consumer-label
plugin, which you can use to pass custom consumer labels to upstream services.
+ - Plugin
+ - attach-consumer-label
+ - Consumer
+description: The attach-consumer-label Plugin attaches custom Consumer labels
to authenticated requests, for Upstream services to implement additional
business logic.
---
<!--
@@ -26,19 +28,23 @@ description: This article describes the Apache APISIX
attach-consumer-label plug
#
-->
+<head>
+ <link rel="canonical" href="https://docs.api7.ai/hub/attach-consumer-label";
/>
+</head>
+
## Description
-The `attach-consumer-label` plugin attaches custom consumer-related labels, in
addition to `X-Consumer-Username` and `X-Credential-Indentifier`, to
authenticated requests, for upstream services to differentiate between
consumers and implement additional logics.
+The `attach-consumer-label` Plugin attaches custom consumer-related labels, in
addition to `X-Consumer-Username` and `X-Credential-Identifier`, to
authenticated requests, for Upstream services to differentiate between
consumers and implement additional logic.
## Attributes
| Name | Type | Required | Default | Valid values | Description
|
|----------|--------|----------|---------|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| headers | object | True | | | Key-value pairs of
consumer labels to be attached to request headers, where key is the request
header name, such as `X-Consumer-Role`, and the value is a reference to the
custom label key, such as `$role`. Note that the value should always start with
a dollar sign (`$`). If a referenced consumer value is not configured on the
consumer, the corresponding header will not be attached to the request. |
+| headers | object | True | | | Key-value pairs of
Consumer labels to be attached to request headers, where key is the request
header name, such as `X-Consumer-Role`, and the value is a reference to the
custom label key, such as `$role`. Note that the value should always start with
a dollar sign (`$`). If a referenced Consumer label value is not configured on
the Consumer, the corresponding header will not be attached to the request. |
-## Enable Plugin
+## Examples
-The following example demonstrates how you can attach custom labels to request
headers before authenticated requests are forwarded to upstream services. If
the request is rejected, you should not see any consumer labels attached to
request headers. If a certain label value is not configured on the consumer but
referenced in the `attach-consumer-label` plugin, the corresponding header will
also not be attached.
+The following example demonstrates how you can attach custom labels to request
headers before authenticated requests are forwarded to Upstream services. If
the request is rejected, you should not see any Consumer labels attached to
request headers. If a certain label value is not configured on the Consumer but
referenced in the `attach-consumer-label` Plugin, the corresponding header will
also not be attached.
:::note
@@ -50,11 +56,13 @@ admin_key=$(yq '.deployment.admin.admin_key[0].key'
conf/config.yaml | sed 's/"/
:::
-Create a consumer `john` with custom labels:
+### Attach Consumer Labels
+
+Create a Consumer `john` with custom labels:
```shell
curl "http://127.0.0.1:9180/apisix/admin/consumers"; -X PUT \
- -H "X-API-KEY: ${ADMIN_API_KEY}" \
+ -H "X-API-KEY: ${admin_key}" \
-d '{
"username": "john",
"labels": {
@@ -64,11 +72,11 @@ curl "http://127.0.0.1:9180/apisix/admin/consumers"; -X PUT \
}'
```
-Configure the `key-auth` credential for the consumer `john`:
+Configure the `key-auth` Credential for the Consumer `john`:
```shell
curl "http://127.0.0.1:9180/apisix/admin/consumers/john/credentials"; -X PUT \
- -H "X-API-KEY: ${ADMIN_API_KEY}" \
+ -H "X-API-KEY: ${admin_key}" \
-d '{
"id": "cred-john-key-auth",
"plugins": {
@@ -79,11 +87,11 @@ curl
"http://127.0.0.1:9180/apisix/admin/consumers/john/credentials"; -X PUT \
}'
```
-Create a route enabling the `key-auth` and `attach-consumer-label` plugins:
+Create a Route enabling the `key-auth` and `attach-consumer-label` Plugins:
```shell
curl "http://127.0.0.1:9180/apisix/admin/routes"; -X PUT \
- -H "X-API-KEY: ${ADMIN_API_KEY}" \
+ -H "X-API-KEY: ${admin_key}" \
-d '{
"id": "attach-consumer-label-route",
"uri": "/get",
@@ -106,13 +114,17 @@ curl "http://127.0.0.1:9180/apisix/admin/routes"; -X PUT \
}'
```
+- `X-Consumer-Department`: attaches the `department` Consumer label value.
+- `X-Consumer-Company`: attaches the `company` Consumer label value.
+- `X-Consumer-Role`: attaches the `role` Consumer label value. As the `role`
label is not configured on the Consumer, it is expected that the header will
not appear in the request forwarded to the Upstream service.
+
:::tip
-The consumer label references must be prefixed by a dollar sign (`$`).
+Consumer label references must be prefixed by a dollar sign (`$`).
:::
-To verify, send a request to the route with the valid credential:
+To verify, send a request to the Route with the valid Credential:
```shell
curl -i "http://127.0.0.1:9080/get"; -H 'apikey: john-key'
@@ -128,7 +140,7 @@ You should see an `HTTP/1.1 200 OK` response similar to the
following:
"Apikey": "john-key",
"Host": "127.0.0.1",
"X-Consumer-Username": "john",
- "X-Credential-Indentifier": "cred-john-key-auth",
+ "X-Credential-Identifier": "cred-john-key-auth",
"X-Consumer-Company": "api7",
"X-Consumer-Department": "devops",
"User-Agent": "curl/8.6.0",
@@ -140,20 +152,4 @@ You should see an `HTTP/1.1 200 OK` response similar to
the following:
}
```
-## Delete plugin
-
-To remove the Plugin, you can delete the corresponding JSON configuration from
the Plugin configuration. APISIX will automatically reload and you do not have
to restart for this to take effect.
-
-```shell
-curl "http://127.0.0.1:9180/apisix/admin/routes/attach-consumer-label-route";
-X PUT \
- -H "X-API-KEY: ${ADMIN_API_KEY}" \
- -d '{
- "uri": "/get",
- "upstream": {
- "type": "roundrobin",
- "nodes": {
- "httpbin.org:80": 1
- }
- }
- }'
-```
+Note that `X-Consumer-Role` is not present in the response because the `role`
label was not configured on the Consumer.
diff --git a/docs/en/latest/plugins/response-rewrite.md
b/docs/en/latest/plugins/response-rewrite.md
index f7292bfc4..ec3bd8a7a 100644
--- a/docs/en/latest/plugins/response-rewrite.md
+++ b/docs/en/latest/plugins/response-rewrite.md
@@ -54,11 +54,11 @@ You can also use the [redirect](./redirect.md) Plugin to
set up redirects.
| status_code | integer | False | | [200, 598]
| New HTTP status code in the response. If unset, falls back to the original
status code.
|
| body | string | False | |
| New response body. The `Content-Length` header would also be reset. Should
not be configured with `filters`.
|
| body_base64 | boolean | False | false |
| If true, decode the response body configured in `body` before sending to
client, which is useful for image and protobuf decoding. Note that this
configuration cannot be used to decode Upstream response.
|
-| headers | object | False | |
| Actions to be executed in the order of `add`, `remove`, and `set`.
|
+| headers | object | False | |
| Actions to be executed in the order of `add`, `remove`, and `set`.
|
| headers.add | array[string] | False | |
| Headers to append to requests. If a header already present in the
request, the header value will be appended. Header value could be set to a
constant, or one or more [Nginx
variables](https://nginx.org/en/docs/http/ngx_http_core_module.html).
[...]
-| headers.set | object | False | |
|Headers to set to requests. If a header already present in the request, the
header value will be overwritten. Header value could be set to a constant, or
one or more[Nginx
variables](https://nginx.org/en/docs/http/ngx_http_core_module.html). |
+| headers.set | object | False | |
| Headers to set to requests. If a header already present in the request, the
header value will be overwritten. Header value could be set to a constant, or
one or more [Nginx
variables](https://nginx.org/en/docs/http/ngx_http_core_module.html). |
| headers.remove | array[string] | False | |
| Headers to remove from requests. |
-| vars | array[array] | False | | | An array of one or
more matching conditions in the form of
[lua-resty-expr](https://github.com/api7/lua-resty-expr#operator-list).
|
+| vars | array[array] | False | | | An array of one or
more matching conditions in the form of
[lua-resty-expr](https://github.com/api7/lua-resty-expr#operator-list) to
conditionally execute the Plugin. |
| filters | array[object] | False | |
| List of filters that modify the response body by replacing one
specified string with another. Should not be configured with `body`.
|
| filters.regex | string | True | |
| RegEx pattern to match on the response body. |
| filters.scope | string | False | "once" | ["once","global"]
| Scope of substitution. `once` substitutes the first matched instance and
`global` substitutes globally.
|
@@ -228,7 +228,7 @@ Hello World
### Rewrite Response and Its Connection with Execution Phases
-The following example demonstrates the connection between the
`response-rewrite` Plugin and [execution
phases](/apisix/key-concepts/plugins#plugins-execution-lifecycle) by
configuring the Plugin with the `key-auth` Plugin, and see how the response is
still rewritten to `200 OK` in the case of an unauthenticated request.
+The following example demonstrates the connection between the
`response-rewrite` Plugin and [execution
phases](../terminology/plugin.md#plugins-execution-lifecycle) by configuring
the Plugin with the `key-auth` Plugin, and see how the response is still
rewritten to `200 OK` in the case of an unauthenticated request.
Create a Consumer `jack`:
diff --git a/docs/zh/latest/plugins/attach-consumer-label.md
b/docs/zh/latest/plugins/attach-consumer-label.md
index 57c611685..5981cc737 100644
--- a/docs/zh/latest/plugins/attach-consumer-label.md
+++ b/docs/zh/latest/plugins/attach-consumer-label.md
@@ -3,8 +3,10 @@ title: attach-consumer-label
keywords:
- Apache APISIX
- API 网关
- - API Consumer
-description: 本文介绍了 Apache APISIX attach-consumer-label
插件的相关操作，你可以使用此插件向上游服务传递自定义的 Consumer labels。
+ - 插件
+ - attach-consumer-label
+ - Consumer
+description: attach-consumer-label 插件将自定义消费者标签附加到经过身份验证的请求，以便上游服务实现额外的业务逻辑。
---
<!--
@@ -26,23 +28,27 @@ description: 本文介绍了 Apache APISIX attach-consumer-label 插件的相关
#
-->
+<head>
+ <link rel="canonical" href="https://docs.api7.ai/hub/attach-consumer-label";
/>
+</head>
+
## 描述
-`attach-consumer-label` 插件在 X-Consumer-Username 和 X-Credential-Indentifier
之外，还将自定义的消费者相关标签附加到经过身份验证的请求，以便上游服务区分消费者并实现额外的逻辑。
+`attach-consumer-label` 插件在 `X-Consumer-Username` 和 `X-Credential-Identifier`
之外，还将自定义的消费者相关标签附加到经过身份验证的请求，以便上游服务区分消费者并实现额外的业务逻辑。
## 属性
-| 名称 | 类型 | 必选项 | 默认值 | 有效值 | 描述
|
-|----------|--------|--------|----------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------|
-| headers | object | 是 | | | 要附加到请求标头的 Consumer
标签的键值对，其中键是请求标头名称，例如 "X-Consumer-Role"，值是对客户标签键的引用，例如 "$role"。请注意，该值应始终以美元符号
(`$`) 开头。如果 Consumer 上没有配置引用的值，则相应的标头将不会附加到请求中。 |
+| 名称 | 类型 | 必选项 | 默认值 | 有效值 | 描述
|
+|----------|--------|--------|--------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------|
+| headers | object | 是 | | |
要附加到请求标头的消费者标签键值对，其中键是请求标头名称（例如 `X-Consumer-Role`），值是对消费者标签键的引用（例如
`$role`）。注意，值必须以美元符号（`$`）开头。如果消费者上未配置被引用的标签，则对应的请求标头将不会被附加。 |
-## 启用插件
+## 示例
-下面的示例演示了如何在通过身份验证的请求转发到上游服务之前，将自定义标签附加到请求标头。如果请求被拒绝，就不会在请求标头上附加任何消费者标签。如果某个标签值未在消费者上配置，但在“attach-consumer-label”插件中被引用，相应的标头也不会被附加。
+下面的示例演示了如何在经过身份验证的请求转发到上游服务之前，将自定义标签附加到请求标头。如果请求被拒绝，则不会在请求标头中附加任何消费者标签。如果某个标签值未在消费者上配置但在
`attach-consumer-label` 插件中被引用，对应的请求标头也不会被附加。
:::note
-您可以这样从 `config.yaml` 中获取 `admin_key` 并存入环境变量：
+你可以这样从 `config.yaml` 中获取 `admin_key` 并存入环境变量：
```bash
admin_key=$(yq '.deployment.admin.admin_key[0].key' conf/config.yaml | sed
's/"//g')
@@ -50,11 +56,13 @@ admin_key=$(yq '.deployment.admin.admin_key[0].key'
conf/config.yaml | sed 's/"/
:::
-创建一个有自定义标签的 Consumer `john`:
+### 附加消费者标签
+
+创建一个带有自定义标签的消费者 `john`：
```shell
curl "http://127.0.0.1:9180/apisix/admin/consumers"; -X PUT \
- -H "X-API-KEY: ${ADMIN_API_KEY}" \
+ -H "X-API-KEY: ${admin_key}" \
-d '{
"username": "john",
"labels": {
@@ -64,11 +72,11 @@ curl "http://127.0.0.1:9180/apisix/admin/consumers"; -X PUT \
}'
```
-为 Consumer `john` 配置 `key-auth`:
+为消费者 `john` 配置 `key-auth` 凭据：
```shell
curl "http://127.0.0.1:9180/apisix/admin/consumers/john/credentials"; -X PUT \
- -H "X-API-KEY: ${ADMIN_API_KEY}" \
+ -H "X-API-KEY: ${admin_key}" \
-d '{
"id": "cred-john-key-auth",
"plugins": {
@@ -83,7 +91,7 @@ curl
"http://127.0.0.1:9180/apisix/admin/consumers/john/credentials"; -X PUT \
```shell
curl "http://127.0.0.1:9180/apisix/admin/routes"; -X PUT \
- -H "X-API-KEY: ${ADMIN_API_KEY}" \
+ -H "X-API-KEY: ${admin_key}" \
-d '{
"id": "attach-consumer-label-route",
"uri": "/get",
@@ -106,21 +114,25 @@ curl "http://127.0.0.1:9180/apisix/admin/routes"; -X PUT \
}'
```
+- `X-Consumer-Department`：附加消费者的 `department` 标签值。
+- `X-Consumer-Company`：附加消费者的 `company` 标签值。
+- `X-Consumer-Role`：附加消费者的 `role` 标签值。由于消费者上未配置 `role`
标签，预期该标头不会出现在转发到上游服务的请求中。
+
:::tip
-引用标签的值必须以 `$` 符号开头。
+引用消费者标签的值必须以 `$` 符号开头。
:::
-使用正确的 apikey 请求该路由，验证插件：
+向路由发送带有正确凭据的请求，进行验证：
```shell
curl -i "http://127.0.0.1:9080/get"; -H 'apikey: john-key'
```
-可以看到类似的 `HTTP/1.1 200 OK` 响应：
+你应该看到类似如下的 `HTTP/1.1 200 OK` 响应：
-```text
+```json
{
"args": {},
"headers": {
@@ -128,7 +140,7 @@ curl -i "http://127.0.0.1:9080/get"; -H 'apikey: john-key'
"Apikey": "john-key",
"Host": "127.0.0.1",
"X-Consumer-Username": "john",
- "X-Credential-Indentifier": "cred-john-key-auth",
+ "X-Credential-Identifier": "cred-john-key-auth",
"X-Consumer-Company": "api7",
"X-Consumer-Department": "devops",
"User-Agent": "curl/8.6.0",
@@ -140,20 +152,4 @@ curl -i "http://127.0.0.1:9080/get"; -H 'apikey: john-key'
}
```
-## 删除插件
-
-当你需要禁用该插件时，可以通过以下命令删除相应的 JSON 配置，APISIX 将会自动重新加载相关配置，无需重启服务：
-
-```shell
-curl "http://127.0.0.1:9180/apisix/admin/routes/attach-consumer-label-route";
-X PUT \
- -H "X-API-KEY: ${ADMIN_API_KEY}" \
- -d '{
- "uri": "/get",
- "upstream": {
- "type": "roundrobin",
- "nodes": {
- "httpbin.org:80": 1
- }
- }
- }'
-```
+注意，由于消费者上未配置 `role` 标签，响应中不包含 `X-Consumer-Role` 标头。
diff --git a/docs/zh/latest/plugins/response-rewrite.md
b/docs/zh/latest/plugins/response-rewrite.md
index 3e0a08dd6..0be097f85 100644
--- a/docs/zh/latest/plugins/response-rewrite.md
+++ b/docs/zh/latest/plugins/response-rewrite.md
@@ -6,7 +6,7 @@ keywords:
- Plugin
- Response Rewrite
- response-rewrite
-description: response-rewrite 插件提供了重写 APISIX 及其上游服务返回给客户端的响应的选项。使用该插件，您可以修改
HTTP 状态代码、请求标头、响应正文等。
+description: response-rewrite 插件提供了重写 APISIX 及其上游服务返回给客户端的响应的选项。使用该插件，你可以修改
HTTP 状态代码、请求标头、响应正文等。
---
<!--
@@ -34,9 +34,9 @@ description: response-rewrite 插件提供了重写 APISIX 及其上游服务返
## 描述
-`response-rewrite` 插件提供了重写 APISIX 及其上游服务返回给客户端的响应的选项。使用此插件，您可以修改 HTTP
状态代码、请求标头、响应正文等。
+`response-rewrite` 插件提供了重写 APISIX 及其上游服务返回给客户端的响应的选项。使用此插件，你可以修改 HTTP
状态代码、请求标头、响应正文等。
-例如，您可以使用此插件来：
+例如，你可以使用此插件来：
- 通过设置 `Access-Control-Allow-*` 标头来支持
[CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS)。
- 通过设置 HTTP 状态代码和 `Location` 标头来指示重定向。
@@ -56,14 +56,14 @@ description: response-rewrite 插件提供了重写 APISIX 及其上游服务返
| body_base64 | boolean | 否 | false | | 如果为
true，则在发送到客户端之前解码`body` 中配置的响应主体，这对于图像和 protobuf 解码很有用。请注意，此配置不能用于解码上游响应。
|
| headers | object | 否 | | | 按照 `add`、`remove` 和 `set` 的顺序执行的操作。 |
| headers.add | array[string] | 否 | | |
要附加到请求的标头。如果请求中已经存在标头，则会附加标头值。标头值可以设置为常量，也可以设置为一个或多个 [Nginx
变量](https://nginx.org/en/docs/http/ngx_http_core_module.html)。 |
-| headers.set | object | 否 | |
|要设置到请求的标头。如果请求中已经存在标头，则会覆盖标头值。标头值可以设置为常量，也可以设置为一个或多个[Nginx
变量](https://nginx.org/en/docs/http/ngx_http_core_module.html)。 |
+| headers.set | object | 否 | | |
要设置到请求的标头。如果请求中已经存在标头，则会覆盖标头值。标头值可以设置为常量，也可以设置为一个或多个 [Nginx
变量](https://nginx.org/en/docs/http/ngx_http_core_module.html)。 |
| headers.remove | array[string] | 否 | | | 要从请求中删除的标头。 |
-| vars | array[array] | 否 | | | 以
[lua-resty-expr](https://github.com/api7/lua-resty-expr#operator-list)
的形式包含一个或多个匹配条件的数组。 |
+| vars | array[array] | 否 | | | 以
[lua-resty-expr](https://github.com/api7/lua-resty-expr#operator-list)
的形式包含一个或多个匹配条件的数组，用于有条件地执行插件。 |
| filters | array[object] | 否 | | | 通过将一个指定字符串替换为另一个指定字符串来修改响应主体的过滤器列表。不应与
`body` 一起配置。 |
| filters.regex | string | True | | | 用于匹配响应主体的 RegEx 模式。 |
| filters.scope | string | 否 | "once" | ["once","global"] | 替换范围。`once`
替换第一个匹配的实例，`global` 全局替换。 |
| filters.replace | string | True | | | 要替换的内容。 |
-| filters.options | string | 否 | "jo" | | 用于控制如何执行匹配操作的 RegEx 选项。请参阅[Lua NGINX
模块](https://github.com/openresty/lua-nginx-module#ngxrematch)以了解可用选项。|
+| filters.options | string | 否 | "jo" | | 用于控制如何执行匹配操作的 RegEx 选项。请参阅 [Lua
NGINX 模块](https://github.com/openresty/lua-nginx-module#ngxrematch)以了解可用选项。|
## 示例
@@ -71,7 +71,7 @@ description: response-rewrite 插件提供了重写 APISIX 及其上游服务返
:::note
-您可以这样从 `config.yaml` 中获取 `admin_key` 并存入环境变量：
+你可以这样从 `config.yaml` 中获取 `admin_key` 并存入环境变量：
```bash
admin_key=$(yq '.deployment.admin.admin_key[0].key' conf/config.yaml | sed
's/"//g')
@@ -122,7 +122,7 @@ curl "http://127.0.0.1:9180/apisix/admin/routes"; -X PUT \
curl -i "http://127.0.0.1:9080/headers";
```
-您应该收到类似于以下内容的 `HTTP/1.1 200 OK` 响应：
+你应该收到类似于以下内容的 `HTTP/1.1 200 OK` 响应：
```text
...
@@ -172,7 +172,7 @@ curl "http://127.0.0.1:9180/apisix/admin/routes"; -X PUT \
curl -i "http://127.0.0.1:9080/headers";
```
-您应该会看到类似以下内容的响应：
+你应该会看到类似以下内容的响应：
```text
{
@@ -220,7 +220,7 @@ curl "http://127.0.0.1:9180/apisix/admin/routes"; -X PUT \
curl "http://127.0.0.1:9080/get";
```
-您应该看到以下响应：
+你应该看到以下响应：
```text
Hello World
@@ -228,7 +228,7 @@ Hello World
### 重写响应及其与执行阶段的联系
-以下示例通过使用 `key-auth` 插件配置插件，演示了 `response-rewrite` 插件与
[执行阶段](/apisix/key-concepts/plugins#plugins-execution-lifecycle)
之间的联系，并查看在未经身份验证的请求的情况下，响应仍如何重写为 `200 OK`。
+以下示例通过使用 `key-auth` 插件配置插件，演示了 `response-rewrite`
插件与[执行阶段](../terminology/plugin.md#plugins-execution-lifecycle)之间的联系，并查看在未经身份验证的请求的情况下，响应仍如何重写为
`200 OK`。
创建消费者 `jack`：
@@ -285,7 +285,7 @@ curl "http://127.0.0.1:9180/apisix/admin/routes"; -X PUT \
curl -i "http://127.0.0.1:9080/get"; -H 'apikey: jack-key'
```
-您应该收到以下 `HTTP/1.1 200 OK` 响应：
+你应该收到以下 `HTTP/1.1 200 OK` 响应：
```text
{"code": 200, "msg": "success"}
@@ -297,7 +297,7 @@ curl -i "http://127.0.0.1:9080/get"; -H 'apikey: jack-key'
curl -i "http://127.0.0.1:9080/get";
```
-您仍应收到相同的 `HTTP/1.1 200 OK` 响应，而不是来自 `key-auth` 插件的 `HTTP/1.1 401
Unauthorized`。这表明 `response-rewrite` 插件仍在重写响应。
+你仍应收到相同的 `HTTP/1.1 200 OK` 响应，而不是来自 `key-auth` 插件的 `HTTP/1.1 401
Unauthorized`。这表明 `response-rewrite` 插件仍在重写响应。
这是因为 `response-rewrite` 插件的 **header_filter** 和 **body_filter** 阶段逻辑将在
[`ngx.exit`](https://openresty-reference.readthedocs.io/en/latest/Lua_Nginx_API/#ngxexit)
之后在其他插件的 **access** 或 **rewrite** 阶段继续运行。
