While the non-blocking HTTP handler (#425) introduced in 0.6.0 addresses a number of the usability and performance issues with the HTTP handler, it does not address the case of needing to fully buffer HTTP responses before sending. In addition, reverse proxy functionality would also require this ability.
This issue will track an API feature that would allow streaming HTTP responses.
While the non-blocking HTTP handler (#425) introduced in 0.6.0 addresses a number of the usability and performance issues with the HTTP handler, it does not address the case of needing to fully buffer HTTP responses before sending. In addition, reverse proxy functionality would also require this ability.
This issue will track an API feature that would allow streaming HTTP responses.