Hi,
On Mon, Dec 04, 2017 at 10:56:22PM +0000, Gregory Storme wrote:
> Hi,
>
> Fixed by removing "option abortonclose" from the defaults section.
There's indeed an incompatibility between abortonclose and H2 which
I don't yet know how to solve, I guess we'll have to move that option
from the proxy to the stream being served and invalidate it when running
from H2. The reason is the difference in behaviour in browsers between
H1 and H2 :
- in H1, when the user clicks "stop", the browser can only send a
shutdown(write) which results in an end of stream being detected.
Option abortonclose then serves to turn this received close into
an abort request.
- in H2, we do have this abort signal via the RST_STREAM frame, and
requests carry an end of stream signal to indicate the request is
complete (headers and optionally payload). In this case we must not
use abortonclose, it never is a valid indicator that the user clicked
on stop.
For now the best we could do would be to document it but I fear
ossification, so I'd rather address it at the root so that abortonclose
doesn't have this undesired effect on H2.
Regards,
Willy
