After the s3 api returns 307, the redirected http request does not seem to carry the original request body?

[simon791110]

Hello everyone

I hope anyone can help me

I'm implementing a simple s3 compatible object storage server
And use cyberduck and cloudberry for testing

Because my server is distributed, in some cases s3 requests will return 307 status code
I confirmed that cyberduck will indeed resend the request to the new location after receiving 307
But the new request does not seem to bring the original body

Now my GET apis can be redirected and processed normally on cyberduck,
But the apis that need to bring the body will fail after redirect

I thought it was a 100-continue issue, but it doesn't look like it's
Because after I return 100-continue, the next packet still has no body

In addition, in the same situation, cloudberry handles the forwarding behavior completely normally