[Webkit-unassigned] [Bug 41419] WE should log the reason when a secure wss WebSocket connection cannot be established

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=41419


Alexey Proskuryakov <ap at webkit.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Secure wss WebSocket        |WE should log the reason
                   |connections cannot be       |when a secure wss WebSocket
                   |established                 |connection cannot be
                   |                            |established
             Status|UNCONFIRMED                 |NEW
          Component|WebCore Misc.               |Web Inspector
                 CC|                            |fishd at chromium.org
     Ever Confirmed|0                           |1




--- Comment #4 from Alexey Proskuryakov <ap at webkit.org>  2010-07-05 12:27:13 PST ---
Logging is absolutely what we should do. I'm not convinced that a warning sheet is a good idea - providing an easy way to bypass security equals to having no security at all, and we can avoid that for WebSocket, that would be good.

We might eventually have to show the warning sheet due to pressure from other browsers (I'm told Chrome does that).

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.