Cause: When returning an error page to the client, for example for a 404 or 403 condition, the </body> and </html> closing tags were missing (not sent to the client) although their presence was accounted for in the requests Content-Length header field value. Consequence: Occasionally depending on the client, the TCP connection between the client the the Rados Gateway would be closed by an RST packet from the client on the account of the incorrect Content-Length header field value instead of a FIN packet under normal circumstances. Fix: Send the </body> and </html> closing tags to the client under all required conditions. Result: The value of the Content-Length header field correctly represents the legth of data sent to the client, and the client no longer reset the connection for an incorrect Content-Length reason.