On Mon, May 15, 2017 at 11:06 AM, Felipe Gasper <felipe@xxxxxxxxxxxxxxxx> wrote: > I’m noticing that mod_proxy sends its entire payload upstream without checking for an early response (e.g., 308 or 404). If upstream sends such a response then closes the connection, mod_proxy never sees it and reports a 502 back. > > Browsers don’t behave this way; they see the response and forward it as expected. Is this a bug in mod_proxy? It sounds like a behavior that could be improved. The backend could also consume the body before sending the response or tearing down the connection. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|