Andrey

I've noticed the same with `content-length` header for POST request (not sure about other types of requests). **Version:** 1.0.7

No way to create/start IdleConnectionEvictor ourselves due to no way to have access to connection manager what is created inside. :(

In case there is a bug and connection/stream is not closed and marked as busy forever. I have fixed the root cause but I would like to prevent similar issues...

@Nirmal-zymr I've checked it once again in the code and actually **IdleConnectionEvictor** has one more thing `connectionManager.closeExpiredConnections();`. It is what we need I suppose, not idle connections agree.

@debora-ito I didn't check new versions/releases, but based on @Nirmal-zymr comment it is still an issue with expired connections.

I'm very disappointed with this issue and had to switch to pure npm. I wonder why yarn community can't fix the issue so long.

@esutton `yarn install --network-concurrency 1` doesn't fully help me I still have errors like this: ``` yarn install v1.16.0 [1/4] Resolving packages... [2/4] Fetching packages... error An unexpected error occurred:...

@FrancescoSaverioZuppichini could you verify whether you use any body parsers in your proxy configuration above? I had a similar issue when I have invalid body parser configured above.

Everything works with `devServer.use(bodyParser.urlencoded());` only. I didn't play with extra options but with a combination of parsers and default settings, it doesn't work for me as well. Try to play...

@FrancescoSaverioZuppichini I wonder what has helped you finally