Handling 100-continue in Hyper for Reverse Proxy

[heiwais25]

Hi,

I have a quick question about the behavior of Hyper when it works as the reverse proxy.

The following diagram is for the explanation of the setup

client <-----> hyper (using for reverse proxy) <----> backend

When we use Hyper to forward the requests to the other backend using conn.send_request(request), Hyper sends the 100-continue for the expect request header to the client immediately since Hyper thinks we are reading the bytes.

This is expected behavior of Hyper, but it changes the behavior in client perspective because 100-continue is sent back to the client even before the backend made the decision to send the 100-continue.

One example case is that client sends the request body even though the backend decided to reject the request and it resulted in broken pipe on Hyper side.

So, could I know if there is any way to control 100-continue case or other general guidance to use Hyper for the reverse proxy?

Thanks,