This is an automated email from the ASF dual-hosted git repository.
kayx23 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 91de1cad4c docs(forward-auth): keepalive does not change the
Connection header (#14187)
91de1cad4c is described below
commit 91de1cad4c0509dfb7be1119b3842d9d0e173d4b
Author: AlinsRan <[email protected]>
AuthorDate: Thu Nov 12 17:03:37 2026 +0800
docs(forward-auth): keepalive does not change the Connection header (#14187)
keepalive decides whether the connection to the auth service is pooled
or closed after the response. ngx_http_ffi_client sends
"Connection: keep-alive" in both cases.
---
docs/en/latest/plugins/forward-auth.md | 2 +-
docs/zh/latest/plugins/forward-auth.md | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/en/latest/plugins/forward-auth.md
b/docs/en/latest/plugins/forward-auth.md
index 4376cb15fc..de6b125f33 100644
--- a/docs/en/latest/plugins/forward-auth.md
+++ b/docs/en/latest/plugins/forward-auth.md
@@ -97,7 +97,7 @@ plugin_attr:
- `ngx_http_ffi_client` (default): the C client. It requires an APISIX runtime
built with the module, which the runtime pinned in `.requirements` is. On a
runtime without it, the auth request fails and returns `status_on_error`, and
the error log names the missing module; the Plugin never silently switches
clients.
- `lua-resty-http`: the Lua client, on every runtime.
-The two clients frame the auth request slightly differently:
`ngx_http_ffi_client` sends `Connection: keep-alive` (or `close` when
`keepalive` is `false`), sends `Content-Length: 0` on a `GET`, and sends no
default `User-Agent`. Its `timeout` bounds the whole response read, where
`lua-resty-http` applies it to each receive.
+The two clients frame the auth request slightly differently:
`ngx_http_ffi_client` sends `Connection: keep-alive`, sends `Content-Length: 0`
on a `GET`, and sends no default `User-Agent`. Its `timeout` bounds the whole
response read, where `lua-resty-http` applies it to each receive. With either
client, `keepalive` only decides whether the connection is returned to the pool
or closed after the response; it does not change the `Connection` header.
## Examples
diff --git a/docs/zh/latest/plugins/forward-auth.md
b/docs/zh/latest/plugins/forward-auth.md
index 2705ba4211..e14ea1183c 100644
--- a/docs/zh/latest/plugins/forward-auth.md
+++ b/docs/zh/latest/plugins/forward-auth.md
@@ -96,7 +96,7 @@ plugin_attr:
- `ngx_http_ffi_client`（默认）：C 客户端，要求 APISIX runtime 编译了该模块，`.requirements`
中固定的 runtime 已包含。在不含该模块的 runtime 上，鉴权请求会失败并返回
`status_on_error`，错误日志会指出缺失的模块；插件不会静默切换客户端。
- `lua-resty-http`：Lua 客户端，适用于所有 runtime。
-两种客户端发出的鉴权请求略有不同：`ngx_http_ffi_client` 会发送 `Connection:
keep-alive`（`keepalive` 为 `false` 时为 `close`），`GET` 请求会带 `Content-Length:
0`，且不发送默认的 `User-Agent`。它的 `timeout` 限制读取整个响应的总时长，而 `lua-resty-http` 对每次接收分别计时。
+两种客户端发出的鉴权请求略有不同：`ngx_http_ffi_client` 会发送 `Connection: keep-alive`，`GET` 请求会带
`Content-Length: 0`，且不发送默认的 `User-Agent`。它的 `timeout` 限制读取整个响应的总时长，而
`lua-resty-http` 对每次接收分别计时。无论使用哪种客户端，`keepalive` 只决定响应后连接放回连接池还是关闭，不影响
`Connection` 请求头。
## 使用示例
