Ticket #742 (defect)

In an application that is using the digest_auth tool, if an unauthenticated client initiates authentication with a POST request then the response to the second POST request (the one with the Authorization header) will be an HTTP 405 Method Not Allowed.

This happens because the digest_auth tool is hooked before the request body has been read from the socket. The error handler for the 401 raised by digest_auth neither reads the socket's read buffer not flushes the buffer, with the result that when the next request is made and the server reads the socket at HTTPRequest.parse_request, the previous request's body concatenated to the new request's method.

The error handler should somehow flush the socket when a request fails.