help request: apisix how implement the try_files feature

[zzqCh]

Description

the nginx document is : https://nginx.org/en/docs/http/ngx_http_core_module.html#try_files

Environment

• APISIX version (run apisix version):
• Operating system (run uname -a):
• OpenResty / Nginx version (run openresty -V or nginx -V):
• etcd version, if relevant (run curl http://127.0.0.1:9090/v1/server_info):
• APISIX Dashboard version, if relevant:
• Plugin runner version, for issues related to plugin runners:
• LuaRocks version, for installation issues (run luarocks --version):

[shreemaan-abhishek]

Whar do you want it for? Please describe your use case.

[zzqCh]

Whar do you want it for? Please describe your use case.

I think the advantage of APISIX is that it can replace nginx and supports dynamic features, but I don't see any replacement for try-files at the moment, so I would like to know how to implement the try-files functionality.

[shreemaan-abhishek]

Do you have a use case? I do not fully understand the try-flies feature, your use case scenario might help me understand.

[zzqCh]

Do you have a use case? I do not fully understand the try-flies feature, your use case scenario might help me understand.

Now there is a route，the path is /a, when a client access /a, the apisix needs to access /a/b and /a/c of the backend service in orderly(if /a/b returns 200 then end the request, otherwise continue with the request /a/b), and /b and /c are actually configured in the try-files plugin of the /a route

[shreemaan-abhishek]

This feature isn't yet supported, would you like to submit a PR for this feature?

[zzqCh]

This feature isn't yet supported, would you like to submit a PR for this feature?

I don't know how to implement it, I considered intercept the request (such as before_proxy phase) before forwarding to the upstream, then send requests using resty library, but this approach will cause the upstream_status and other information to be empty, do you have a good solution?

[github-actions[bot]]

This issue has been marked as stale due to 350 days of inactivity. It will be closed in 2 weeks if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the [email protected] list. Thank you for your contributions.

[github-actions[bot]]

This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time.