It's not WebSockets it's your broken proxy

It's not WebSockets it's your broken proxy(blog.pusherapp.com)

43 points by maxthelion 15 years ago | 6 comments

sedachv 15 years ago |

Everything I hear about WebSockets (things like http://www.ietf.org/mail-archive/web/hybi/current/msg02149.h... and http://blogs.webtide.com/gregw/entry/how_to_improve_websocke... and now this) makes me convinced the current draft standard is unworkable.

m_eiman 15 years ago |

It doesn't really matter, since it's easier to fix four browsers under active development than it is to fix a myriad of old firewalls and proxies.

luigi 15 years ago |

I'd expect to see exploits using Flash sockets as the attack vector before seeing attacks using native WebSockets.

trotsky 15 years ago | |

A vast majority of the installations with these types of vulnerable firewalls don't allow outbound traffic on port 843 which flash needs to be able to communicate on to get raw socket communication permission.

mloughran 15 years ago | | |

Where are you getting the 20-30x number from? There is no demonstrated WebSockets attack in the "Transparent Proxies: Threat or Menace?" paper.