> On 15 May 2017, at 11:13 AM, Eric Covener wrote:
>
> On Mon, May 15, 2017 at 11:06 AM, Felipe Gasper
> 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 clos
On Mon, May 15, 2017 at 11:06 AM, Felipe Gasper 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
Hello,
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
