Bad host error kinda gets swallowed with HTTP2

[danfuzz]

Describe the bug
When a bogus Host header is passed to an HTTP2 request, the connection gets closed abruptly, but no error appears in the system log, and the connection/socket object seems to remain in some form.

To reproduce
Steps to reproduce the behavior:

1. Build the system.
2. Run the test configuration...
3. In a terminal: curl --insecure -H 'Host: 123.4^56' https://localhost:8443/foo/bar

Expected behavior
An error shows up in the system log, and the connection gets properly closed.

Actual behavior
The connection actually gets closed, but there is no indication in the system log that anything is amiss. It's like the request is still being processed or something.

Environment

• OS: macOs

Additional context
This does not seem to happen with an HTTPS request.

[danfuzz]

It looks like the Node HTTP2 library is swallowing this and not reporting any event to client code. Unclear if there is anything to be done about it.