On Tue, 8 Sep 2015 11:35:48 +0300 Vladimir Mihailenco <[email protected]> wrote:
> That is very unlikely since haproxy and Go app run on same machine. But > probably Go expects more data than haproxy buffers - I don't know how to > check this assumption... The appropriate Go code is > https://github.com/golang/go/blob/master/src/net/http/server.go#L1348 Hi, you can run a tcpdump network capture between your two processes (even if the processes are on the same machine), and you will see which one introduce a delay. Thierry > On Sun, Sep 6, 2015 at 1:17 PM, <[email protected]> wrote: > > > On Sat, 5 Sep 2015 18:13:57 +0300 > > Vladimir Mihailenco <[email protected]> wrote: > > > > > Thanks for advice. It turns out that Go silently (without any reply and > > log > > > message) closes the connection when it can't fully read request headers. > > > Which is kinda strange, because I thought that haproxy fully reads > > request > > > headers to route it to proper backend... > > > > Its sure: HAProxy read entirely the headers (if it os configured with > > the mode http). Maybe your problem is between HAProy and your Go > > server ? > >
