Re: [go-nuts] Golang net/http server returning empty packets

Thanks for the suggestions. Sadly, the race detection doesn't work on ARM platforms. I'll try adding tracing as you suggest and see what comes of it. On Tuesday, 22 January 2019 16:18:17 UTC, robert engels wrote: > > Sounds a lot like a concurrency issue - possibly not flushing the request, >

Re: [go-nuts] Golang net/http server returning empty packets

Sounds a lot like a concurrency issue - possibly not flushing the request, or the request is being processed / timing out from another go routine. I would start by adding some lifecycle request traces and processing these in an automated fashion - almost the only way to debug highly concurrent

[go-nuts] Golang net/http server returning empty packets

I have a moderately complex HTTP server written using net/http HandlerFuncs. Testing one request at a time all is well, but when I start putting significant load on it, it sometimes returns empty packets, ie no HTTP response headers, no status code, nothing. The clients are all written using