Erik Dubbelboer

This is indeed intended behavior, `Header.Peek` will normalize the header to `Etag` and won't be able to find it. There currently isn't a `Header.PeekCanonical()`, I'm also not sure if we...

I'm not sure what you mean? This is a HTTP1 only library. HTTP1 doesn't support out of order responses, only HTTP2 does. If a client does another request on another...

That is called HTTP Pipelining and you can use [`fasthttp.PipelineClient`](https://godoc.org/github.com/valyala/fasthttp#PipelineClient) for that. But not all servers might support it. The fasthttp Server does.

These both works for me with your code: ```go func main() { Request("http://34.188.203.116/test") Request("http://static.34.188.203.116.clients.your-server.de/test") } ``` How are you calling `Request`?

Looks like the server doesn't want to handle that many connections at the same time. Not much fasthttp can do about that.

The problem is that we can't really add it to the error as that would change the API. If we make the error dynamic doing `err == fasthttp.ErrDialTimeout` won't work...

@phuslu that would still break for users who currently do `err == fasthttp.ErrDialTimeout` in their code.

I guess you could test if a server supports pipelining by sending a batch of multiple requests and measure the time between responses to see if they arrive in the...

Indeed just use`net.LookupHost` and create a `PipelinceClient` for address and add them to a `LBClient`. `MaxConnections` and `MaxPendingRequests` can't be changed after the `PipelinceClient` is in use so you can't...

If you only have control over the client httpteleport is not going to work.