Chrome sockets exhaustion

ThreeMammals / Ocelot

.NET API Gateway

https://www.nuget.org/packages/Ocelot

MIT License

8.32k stars 1.63k forks source link

Chrome sockets exhaustion #1719

Closed D3mSgr closed 11 months ago

D3mSgr commented 11 months ago

I'm using Ocelot in an IIS environment. When several HTTP calls are made to the gateway, Chrome opens new ones (different ConnectionIDs) instead of reusing the old ones, exhausting the available sockets (the HTTP request stalled). When I run the gateway with Visual Studio or call the APIs directly this doesn't happen. Has anyone encountered this problem?

Thank you

raman-m commented 11 months ago

@D3mSgr Ask your question in Discussions!