CMIIW, I doubt if it is explicitly needed to close the request's body in
handler, as it seems, close of request's body is handled by stdlib upon
completion of handler.
Handler, in net/http, is called
here: https://github.com/golang/go/blob/master/src/net/http/server.go#L1804
Finish
Request
Behalf Of l...@pinkfroot.com
Sent: Wednesday, October 18, 2017 14:35
To: golang-nuts
Subject: Re: [go-nuts] accept4: too many open files;
In the end the fix seemed to be implementing some timeouts. I found a good
guide here...
https://blog.cloudflare.com/the-complete-guide-to-golang-net-http-timeout
In the end the fix seemed to be implementing some timeouts. I found a good
guide here...
https://blog.cloudflare.com/the-complete-guide-to-golang-net-http-timeouts/
On Tuesday, October 17, 2017 at 10:01:17 PM UTC+1, Tamás Gulácsi wrote:
>
> Yes.
--
You received this message because you are su
Yes.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
This is 1.9.1 and I had not thought of switching to http2 although do need to
maintain the 1.1 for older clients.
The closing of the body could explain it though which I thought was automatic
on a return from the handlers? Do I need to explicitly call that in the
handlers??
--
You received t
What version of Go are you using? Have you tried HTTP/2?
The only thing that jumps out at me is that r.Body() is never closed.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send
