Orderly Client Shutdown

[theduke]

Bug Report

Version

0.7.1

Platform

Linux (probably not relevant)

Description

Not sure if this is a bug, a feature request, or just expected behaviour, but:

Currently, when a client is dropped, the server connection always ends with an error: unexpected end of file.

I assume that's because the client just drops the connection without properly closing it?

There doesn't seem to be any API to orderly terminate the connection.

This is mostly an annoyance because the errors pollute the server log.

[LucioFranco]

@seanmonstar does hyper/h2 send a goaway when its dropped? I feel like I've seen that code before but I would assume that would handle the more graceful aspect of this.