4 ms·
maybe there is a problem. this is not the solution. another checkmark on a long list of frustration with firefox 4.
by catshirt 16y ago
maybe there is a problem. this is not the solution.
another checkmark on a long list of frustration with firefox 4.
- weavejester 16y agoWhat else can they do? If the websocket protocol is insecure, they need to wait until its fixed. They'll probably re-enable it in Firefox 4.0.1 or 4.0.2 with a fixed websocket implementation.
- drdaeman 16y agoStop spreading FUD. Websocket protocol is perfectly fine. What's insecure are broken proxies.
- weavejester 16y agoWhy take such an aggressive and accusatory tone? You don't have to reply with such vitriol. Secondly, I didn't actually say websockets were insecure; I said if they were, then Firefox is sensible not to include them. Third, even if the websocket protocol is secure in theory, if the majority of proxies don't correctly implement the upgrade header, then using websockets is insecure in practise.