Erik Dubbelboer

If only half of your nginx workers is doing anything then that probably means that nginx doesn't need more? Why not reduce the worker count there? Setting a low `MaxIdleConnDuration`...

Even if `sleepFor` is less than 0 for one iteration. I won't constantly be less than 0. So I don't see how that could cause 100% CPU usage for longer.

I'm guessing this has nothing to do with fasthttp. Or does a normal `net/http` server work?

I'm not sure what you mean? You want to reuse a single Request and Response multiple times? If so, then yes you can do this, but you have to call...

Do you have a stacktrace for me? The reason this panics is that it shouldn't be possible to happen. It should always call `Discard` with a number of bytes it...

Which version of fasthttp are you using? Can you please update to the latest version. Unless you are using the `RequestCtx`, `Request` or `RequestHeaders` after your handler has returned, it's...

A URL like that is tested exactly here: https://github.com/valyala/fasthttp/blob/2c8ce3b40e933669366c9519503bc8df4f1a8b8a/client_test.go#L243-L281 Is it possible for you to modify this test in such a way that it fails?

Sounds good but might be complicated. Keep in mind that an Accept-Encoding header can look like this for example: `Accept-Encoding: deflate, gzip;q=0.9, *;q=0.5`. Not sure how you want to store...

I'm not sure, you'll have to read the RFC I guess.

In theory you can just close the listener, and keep a list of connections using [`Server.ConnState`](https://pkg.go.dev/github.com/valyala/fasthttp?utm_source=godoc#Server.ConnState) and close those as well.