From 6946683022cf1f333eb628547ad10f7cb6be02d2 Mon Sep 17 00:00:00 2001 From: traky Date: Mon, 23 Dec 2024 17:55:45 +0800 Subject: [PATCH] lint --- docs/en/latest/plugins/response-rewrite.md | 4 ++-- docs/zh/latest/plugins/response-rewrite.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/en/latest/plugins/response-rewrite.md b/docs/en/latest/plugins/response-rewrite.md index 2c536f6caea1..2e22e26a0078 100644 --- a/docs/en/latest/plugins/response-rewrite.md +++ b/docs/en/latest/plugins/response-rewrite.md @@ -126,7 +126,7 @@ X-Server-id: 3 X-Server-status: on X-Server-balancer-addr: 50.237.103.220:80 -{"code":"ok","message":"new json body"} +{"code":"ok","message":"new json body"} ``` ### Rewrite Header With RegEx Filter @@ -297,7 +297,7 @@ You should still receive an `HTTP/1.1 200 OK` response of the same, instead of ` This is because **header_filter** and **body_filter** phase logics of the `response-rewrite` Plugin will continue to run after [`ngx.exit`](https://openresty-reference.readthedocs.io/en/latest/Lua_Nginx_API/#ngxexit) in the **access** or **rewrite** phases from other plugins. -The following table summarizes the impact of `ngx.exit` on execution phases. +The following table summarizes the impact of `ngx.exit` on execution phases. | Phase | rewrite | access | header_filter | body_filter | |---------------|----------|----------|---------------|-------------| diff --git a/docs/zh/latest/plugins/response-rewrite.md b/docs/zh/latest/plugins/response-rewrite.md index 94ce913ad8f6..447ef8bc736a 100644 --- a/docs/zh/latest/plugins/response-rewrite.md +++ b/docs/zh/latest/plugins/response-rewrite.md @@ -126,7 +126,7 @@ X-Server-id: 3 X-Server-status: on X-Server-balancer-addr: 50.237.103.220:80 -{"code":"ok","message":"new json body"} +{"code":"ok","message":"new json body"} ``` ### 使用 RegEx 过滤器重写标头