RESOLVED INVALID 17448
Secure HTTPS connections fail under some circumstances.
https://bugs.webkit.org/show_bug.cgi?id=17448
Summary Secure HTTPS connections fail under some circumstances.
Thorsten Kramp
Reported 2008-02-20 05:05:39 PST
Description: Connection failures have been observed with a HTTPS proxy running on localhost. During the SSL handshake phase the proxy sometimes receives TWO subsequent client-hello messages on the same socket from Safari! This is a protocol violation and the proxy terminates the connection. Since the probability of the error to occur is higher when many connections and handshakes are initiated by Safari in a short timely manner, the problem could be caused by incorrectly implemented synchronization. It looks like a socket is reused for a new connection although it is still busy. The problem occurs with Safari on Mac OSX Tiger+Leopard and on Windows XP. Depends on: The page content. When the page contains many links and these are retrieved quickly and in parallel, the connections are more likely to fail. The observed misbehaviour is somehow timing-dependent and cannot be reproduced 100% identically.
Attachments
Alexey Proskuryakov
Comment 1 2008-02-21 22:21:03 PST
This is definitely an issue in closed source Apple frameworks below WebKit. Could you please file a bug at <http://bugreport.apple.com> for Apple engineers who work on this code to investigate this issue? Closing as INVALID per our process, as it is not a WebKit issue.
Thorsten Kramp
Comment 2 2008-02-21 22:35:43 PST
OK, I filed the bug at <http://bugreport.apple.com>.
Note You need to log in before you can comment on or make changes to this bug.