Hey @tumao
The buffering behavior is currently not configurable. We will discuss internally if that’s something we want to allow the users to configure.
Disabling buffering completely may be somewhat confusing, as we use the buffered data not only for replays, but for retries as well. And such retries may not even be caused by your app behavior. E.g. when we route a request, the proxy may pick an intermediary host which just died (but the proxy hasn’t learned that yet), and without buffered data it might not be possible to retry such a request.
What we tried: 103 Early Hints
We currently don’t support Early Hints. This is something that we want to support in the future, though.
Respond before reading the body (early 200 + streamed body). Works in principle, but forces committing the status code and result headers before the request has been parsed
Have you considered using HTTP trailers as a workaround for that? This will allow you to send more info to the client after the body is fully processed.