openresty / openresty/lua-nginx-module
body_filter_by_lua case some strange behaviors
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 11.8k
- Forks
- 2.1k
- Avg merge
- 6h 1m
- Merged PRs (30d)
- 6
Description
中文讨论：https://groups.google.com/g/openresty/c/kCQM3WcLC-k/m/xPckMVBSBwAJ
by using body_filter_by_lua with ngx.arg[1] uncahange，it return strange truncated response
add chunked_transfer_encoding off ,it return duplicate response line
#file-zcurl-filterandchunkoff-out-L97 && #file-zcurl-filterandchunkoff-out-L142
i test it on latest openresty 1.21.4.1 and Tengine/2.3.2(nginx/1.17.3) , Tengine is all ok
see full conf and debug log here: https://gist.github.com/9268/a9491787efa50201fbc48d82e5de1406
if someone can provide some test case example ，i can write some cases
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Google Groups discussion and the full configuration and debug log in the referenced Gist. Reproduce the body_filter_by_lua behavior on OpenResty 1.21.4.1, comparing unchanged ngx.arg[1] and chunked_transfer_encoding off with the reported Tengine result. Done means a focused test case captures the truncated or duplicate response behavior and its expected output is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, lua, nginx
- Domain
- backend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100