help request: core.response.exit will NOT interrupt the execution of the current request

[chenyyyang]

Description

https://github.com/openresty/lua-nginx-module?tab=readme-ov-file#ngxexit

When status >= 200 (i.e., ngx.HTTP_OK and above), it will interrupt the execution of the current request and return status code to Nginx.

According to this document,I tried
core.response.exit(200, "anything") on "Access" phase
and
core.response.exit(500, "anything")on "Access" phase

I check the logs and found that apisix will NOT interrupt the request . The "header_filter" ,"body_filter","log" phase will also be executed.

Environment

• APISIX version (run apisix version): 2.15
• Operating system (run uname -a): ubuntu (WSL)
  resty 0.28
  nginx version: openresty/1.21.4.1
  built with OpenSSL 1.1.1n 15 Mar 2022

[shreemaan-abhishek]

I check the logs and found that apisix will NOT interrupt the request . The "header_filter" ,"body_filter","log" phase will also be executed.

this is by design.

[chenyyyang]

Hi @shreemaan-abhishek .Thank you for participating in the discussion
Is this behavior of the ngx.exit method changed by modifying the code of the lua-nginx-module?
According to the original documentation, executing ngx.exit(201) in the access phase should immediately respond to the client and prevent further execution of the header_filter and body_filter phases.
I'm quite curious about this.

[bzp2010]

@chenyyyang

The core.response.exit uses ngx.exit internally, so it has the same behavior as ngx.exit and we have not made any behavioral changes.

According to the discussion here (openresty/lua-nginx-module#2279), this is the status quo of ngx.exit, and header_filter and body_filter are not affected by ngx.exit to skip. I've proven this on my personal tests.

https://github.com/api7/apisix-nginx-module/blob/3787343a3341798a82e481f937d6e7e267a13d2d/lib/resty/apisix/response.lua#L40-L59

If skipping them is required, APISIX does have some internal APIs that will do it, but since it's an out-of-tree module, you'll have to keep track of its compatibility to avoid upgrades that break your code.

[chenyyyang]

Thank you for your response. The link you provided has indeed answered my questions. Thank you. @bzp2010