I am seeing this as well when connecting to haproxy 1.8 locally. About 1 in 1000 requests. They all seem to have the "Connection: Close" header FWIW. The backends behind haproxy never see the request.
On Thursday, February 20, 2014 at 6:23:13 PM UTC-8, freeformz wrote: > > I send a lot of data via golang"s http.Client.Do() and sometimes get EOF > errors. > > AFAICT I get EOFs because the underlying network connection has closed and > I can no longer send or read the bytes I expect to read/send. > > But given the structured nature of http streams I'd expect to get > ErrUnexpectedEOF in that case. > > What am I missing? > > -- > Edward Muller > @freeformz > -- 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.
