In some testing, we make several get requests for beacons on the same host, and they all get redirected. The proxy is using http.request to make these calls, and for some reason the sockets are getting kept alive, which is blocking subsequent beacon firings after the first 5. This is due to the default max request setting for http.request for the same host:
In some testing, we make several get requests for beacons on the same host, and they all get redirected. The proxy is using http.request to make these calls, and for some reason the sockets are getting kept alive, which is blocking subsequent beacon firings after the first 5. This is due to the default max request setting for http.request for the same host:
http://stackoverflow.com/questions/16472497/nodejs-max-socket-pooling-settings
This can be fixed by:
I will create a pull request for this.