This is an automated email from the ASF dual-hosted git repository.
shreemaanabhishek 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 2caa9d88a docs: remove misleading information (#10973)
2caa9d88a is described below
commit 2caa9d88abec2e482c6e7f4da4845bbe7f4278ef
Author: Abhishek Choudhary <[email protected]>
AuthorDate: Fri Mar 1 08:29:08 2024 +0545
docs: remove misleading information (#10973)
---
docs/en/latest/plugin-develop.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/en/latest/plugin-develop.md b/docs/en/latest/plugin-develop.md
index 1b674303e..014939a51 100644
--- a/docs/en/latest/plugin-develop.md
+++ b/docs/en/latest/plugin-develop.md
@@ -341,7 +341,7 @@ If none of the keys in `keyring` can decrypt the data, the
original data is used
Determine which phase to run, generally access or rewrite. If you don't know
the [OpenResty
lifecycle](https://github.com/openresty/lua-nginx-module/blob/master/README.markdown#directives),
it's
recommended to know it in advance. For example key-auth is an authentication
plugin, thus the authentication should be completed
before forwarding the request to any upstream service. Therefore, the plugin
must be executed in the rewrite phases.
-In APISIX, only the authentication logic can be run in the rewrite phase.
Other logic needs to run before proxy should be in access phase.
+Similarly, if you want to modify or process the response body or headers you
can do that in the `body_filter` or in the `header_filter` phases respectively.
The following code snippet shows how to implement any logic relevant to the
plugin in the OpenResty log phase.
