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:
- Build the system.
- Run the test configuration...
- 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
Additional context
This does not seem to happen with an HTTPS request.
Describe the bug
When a bogus
Hostheader 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:
curl --insecure -H 'Host: 123.4^56' https://localhost:8443/foo/barExpected 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
Additional context
This does not seem to happen with an HTTPS request.