openresty / openresty/lua-nginx-module
why access_by_lua at the end of access phase
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 11.8k
- Forks
- 2.1k
- Avg merge
- 6h 1m
- Merged PRs (30d)
- 6
Description
https://github.com/openresty/lua-nginx-module/blob/master/src/ngx_http_lua_accessby.c#L368
when rc==NGX_OK
return NGX_OK;
i have two modules
HTTP_AUX_FILTER_MODULES module ngx-lua-module
HTTP_MODULES B
./configure
--add-module=ngx-lua-module
--add-module=B
then the access phase of ngx-lua-module will be run firstly. because ngx_http_lua_access_by_chunk return NGX_OK, so the access_phase of B will be skiped,
how can i fix this case
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 at src/ngx_http_lua_accessby.c#L368 and trace ngx_http_lua_access_by_chunk through NGINX's access phase. Reproduce the configuration with ngx-lua-module and module B, then determine whether NGX_OK is intended to stop later handlers; done means the interaction and any supported fix or limitation are clearly established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, lua, nginx
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100