Bug 17448
| Summary: | Secure HTTPS connections fail under some circumstances. | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Thorsten Kramp <kramp> |
| Component: | Page Loading | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | ap |
| Priority: | P1 | ||
| Version: | 523.x (Safari 3) | ||
| Hardware: | Mac | ||
| OS: | OS X 10.5 | ||
Thorsten Kramp
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 | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
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
OK, I filed the bug at <http://bugreport.apple.com>.