bug: After the forward-auth verification is passed, the upstream cannot obtain the request body (payload) with 504 Timeout about apisix HOT 5 OPEN

Hi, Can you please provide the reproducing steps?

from apisix.

Hi, Can you please provide the reproducing steps?

ok
Step 1: Set up two routes and two upstreams in the dashboard. Associate route A with upstream A, and route B with upstream B. Route B is used for forwarding requests to an external authentication service (i.e., upstream B).

Step 2: Enable the forward-auth plugin for route A and set the URI to http://localhost:9080/authApi/api/authorization/authorization1 (Note: authApi is the path of route B, which means that when calling the external authentication, it should go through route B).

Step 3: Once the routes and upstreams are set up, test a POST request to the interface corresponding to upstream A through route A at http://localhost:9080/userCenterApi/api/GetToken/GetData (Note: userCenterApi is the path of route A, which means that accessing this path will make apisix forward the request).

Outcome: The external authentication service successfully validates, and during debugging, it was noticed that the request body content can be read normally. I use the following code to read the request body:

using (StreamReader reader = new StreamReader(Request.Body, Encoding.UTF8))
{
body = await reader.ReadToEndAsync();
// Do something with the body...
}
After successful external validation, when the request is forwarded by route A to upstream A, upstream A is unable to read the request body. I use the following code to read the request body:

using (StreamReader reader = new StreamReader(Request.Body, Encoding.UTF8))
{
body = await reader.ReadToEndAsync();
// Do something with the body...
}
The reason for not being able to read is due to the occurrence of an exception, Microsoft.AspNetCore.Connections.ConnectionResetException, with the message: "The client has disconnected." Subsequently, the apisix log shows: "upstream timed out (110: Connection timed out) while reading response header from upstream." Once I commented out the code for reading the request body, the exception did not occur, and there was no 504 timeout.

As a beginner, I am unable to identify the root cause of this error. Your assistance in resolving this issue would be greatly appreciated. Thank you!

from apisix.

I am also running into the 504 timeout error with the following log:

*3516 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.21.0.1, server: _, request: "POST /anything HTTP/1.1", upstream: "http://174.129.50.9:80/anything", host: "127.0.0.1:9080"

It is unclear how to correctly use the "request_method": "POST" option without invoking this error. I am changing very minimal config from the doc example and will be easier to reproduce.

Details:

Things run well without "request_method": "POST" in the plugin config.

from apisix.

Related: #11050, from the convo it looks like 3.6.0 does not have this issue. To be tested.

from apisix.

Related: #11050, from the convo it looks like 3.6.0 does not have this issue. To be tested.相关： #11050 ，从 convo 来看，3.6.0 没有这个问题。待测试。

Thanks for the reply, I'll try it in version 3.6.0

from apisix.