Y2XNishan opened a new pull request, #14176: URL: https://github.com/apache/apisix/pull/14176
### Description Document that ext-plugin-post-resp cannot be combined with grpc-transcode: its lua-resty-http upstream client supports HTTP/1.0 and HTTP/1.1 rather than the HTTP/2 transport required by gRPC. Add matching explanations and local grpc-transcode links to the English and Chinese plugin pages. Existing examples and runtime source are unchanged. Acknowledges @moying2026's earlier documentation proposal in #13394. The wording was checked against the current implementation and pinned HTTP-client dependency. Validation on Windows 11 (build 26200), Node.js 24.16.0 and Python 3.13.5: - Markdownlint CLI 0.25.0 on both files: exit 0; Node emitted an fs.R_OK deprecation warning. - AutoCorrect 2.6.2 on the Chinese file: exit 0, zero errors and warnings. - Offline verification: all 12 relative file targets exist; all eight fenced examples match the base revision; only the two requested documentation files changed. - git diff --check: exit 0. No runtime tests were added or run because this is a documentation-only clarification. The plugin combination was source-inspected, not rerun against a live gateway. Codex assisted with drafting and local validation. Contributor reviewed and approved the documentation change. #### Which issue(s) this PR fixes: Fixes #10787 ### Checklist - [x] I have explained the need for this PR and the problem it solves - [x] I have explained the changes or the new features added to this PR - [ ] I have added tests corresponding to this change - [x] I have updated the documentation to reflect this change - [x] I have verified that this change is backward compatible (If not, please discuss on the [APISIX mailing list](https://github.com/apache/apisix/tree/master#community) first) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
