Infinite request loop when server sends status code 200

[foxdrodd]

Through another condition our load-balancer sent code 200 on those sockjs /xhr/../xhr_streaming requests.
sockjs handles this with an extreme infinite loop of requests.

This is dangerous, as it hammers down the whole network, if there are enough open browser windows.

Of course it is wrong to send the 200 response, but the result is so harmful, that a general handling to prevent those fast request loops within sockjs would be really good.

[voliva]

I'm having the same problem - I found the source of the infinite loop, but without fully understanding the logic behind this, I'm not sure if it's just safe to throttle down the requests.

It's in here:

sockjs-client/lib/transport/lib/polling.js

Lines 23 to 39 in 0ab53b8

	Polling.prototype._scheduleReceiver = function() {
	debug('_scheduleReceiver');
	var self = this;
	var poll = this.poll = new this.Receiver(this.receiveUrl, this.AjaxObject);
	poll.on('message', function(msg) {
	debug('message', msg);
	self.emit('message', msg);
	});
	poll.once('close', function(code, reason) {
	debug('close', code, reason, self.pollIsClosing);
	self.poll = poll = null;
	if (!self.pollIsClosing) {
	if (reason === 'network') {
	self._scheduleReceiver();

So Polling.scheduleReciever is getting the poll object emitting 'close', and if the reason is 'network', then it reschedules again.

[brycekahle]

Throttling the speed at which these requests happen, would also slow-down connections that are actually sending data at a high-rate, even if only for a short while.