hcldan opened a new issue, #13366: URL: https://github.com/apache/apisix/issues/13366
### Description Our backend application will accept file uploads under certain (proper) conditions. Session must be valid, request must make sense, etc. If any of these checks fail we will respond appropriately with an error code. This error code appears to be swallowed by apisix and we get a 502 as a response, it seems due to the response returning immediately. However, the backend behavior is desired, so as not to cause un-needed uploads if they are just going to fail. How can we get around this issue? Is this a fundamental problem with apisix or is our http server perhaps behaving incorrectly when responding so as to cause apisix to behave this way? Could we change the behavior with a custom plugin? Buffering the entire request, or reading the entire request and discarding it is not desired in this case, for large files that would be just as bad as not returning immediately. ### Environment I don't have this information readily available but we are using something pretty recent in k8s on RHEL 10 nodes. I will update the ticket with more info as I get it if it is needed. - 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`): -- 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]
