My understanding is that COMET implementations of WebSync and SignalR do not directly use IIS and are a few layers lower on the ISO model.

After reading Qualys's blog regarding slow TCP reading, I was wondering if this had any effect on COMET implementations since some are already using "long polling", websockets, or perhaps some other technique?

Are COMET (or reverse AJAX) installations not vulnerable to this class of attack by design?


WebSync runs directly on top of the IIS/.NET stack, and so it relies on the Windows/IIS kernel to process TCP/HTTP for both long-polling and WebSocket transports. I believe SignalR does this as well.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.