Jetty throws and sends an invalid HTTP response if the servlet exhausts the connector's header buffer

If a servlet exhausts the connector's header buffer (for example, by setting too many headers), an ArrayOutOfBoundsException is thrown while flushing the content to the socket and jetty then forgets to append the termination characters to the HTTP headers, resulting in a damaged HTTP response that ends up looking like this in a normal browser:

</body>
</html>

because the last two \n of Jetty's default HTML error message get interpreted as the header/payload transition.

While it's always possible to increase the connector's buffer, this problem prevents the server to return any reasonable error message.