It looks like there is a timeout (aka deadline) set on the connection, so small responses are sent without problems, while large responses are interrupted by the timeout. See https://blog.cloudflare.com/the-curious-case-of-slow-downloads/ for details.
On Thursday, January 28, 2016 at 7:06:38 PM UTC+2, vijayan jay wrote: > > We are using net.Conn.Write(response) in our program were response is a > json data of length 84317829 bytes. > Is there any chance for failure of write in golang when length of data is > more ? > Because i could see that in one more scenario when length is 3585632 then > write is working fine. > > I have copied the error which i printed in the program, > (EXTRA string=write tcp 127.0.0.1:3988->127.0.0.1:28459: write: broken > pipe) > > So could you please help here what could be reason for this issue ? > > Please let me know if you need any other information. > -- 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.