In Go 1.8 the HTTP server finishes a request after it was handled by setting a read timeout. The behaviour of setting deadlines affecting ongoing reads is new since Go 1.8. Because of that reading fails with an i/o timeout error. This issue was discussed here.
In Go 1.8 the HTTP server finishes a request after it was handled by setting a read timeout. The behaviour of setting deadlines affecting ongoing reads is new since Go 1.8. Because of that reading fails with an
i/o timeouterror. This issue was discussed here.Currently we close the connection on any read errors. But since this error is expected, we should ignore it.
Related to #75