@opal @Suiseiseki Oh yeah, that could be a reason. Although, bloat doesn't set a timeout for connections. It did use 30s timeout for bloat->upstream server connection, but I removed it after a while because it makes more sense to let the upstream server handle the timeouts.
Also, Go's HTTP and other network libraries have a concept of a "Context" which makes it very easy to pass around timeout and cancellation information to subsequent network calls. In bloat, pressing the browser stop button will also cancel the bloat->upstream server request. So it makes little sense to have timeouts in bloat.