Bug 232774

Summary: Regression(r284472) http/tests/security/mixedContent/websocket/insecure-websocket-in-iframe.html is flaky
Product: WebKit Reporter: Chris Dumez <cdumez>
Component: Tools / TestsAssignee: Chris Dumez <cdumez>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: achristensen, webkit-bug-importer, youennf
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch ews-feeder: commit-queue-

Chris Dumez
Reported 2021-11-05 17:05:42 PDT
http/tests/security/mixedContent/websocket/insecure-websocket-in-iframe.html is flaky: Diff: --- /Volumes/Data/worker/debug-wk2-tests/build/OpenSource/layout-test-results/http/tests/security/mixedContent/websocket/insecure-websocket-in-iframe-expected.txt +++ /Volumes/Data/worker/debug-wk2-tests/build/OpenSource/layout-test-results/http/tests/security/mixedContent/websocket/insecure-websocket-in-iframe-actual.txt @@ -2,7 +2,6 @@ CONSOLE MESSAGE: WebSocket connection failed. CONSOLE MESSAGE: WebSocket connection failed: WebSocket is closed before the connection is established. -CONSOLE MESSAGE: WebSocket closed. This test loads an iframe that creates an insecure WebSocket connection. We should block the connection and trigger a mixed content callback because the main frame is HTTPS, but the data sent over the socket could be recorded or controlled by an attacker.
Attachments
Patch (1.79 KB, patch)
2021-11-05 17:08 PDT, Chris Dumez
ews-feeder: commit-queue-
Chris Dumez
Comment 1 2021-11-05 17:06:09 PDT
Chris Dumez
Comment 2 2021-11-05 17:08:47 PDT
Chris Dumez
Comment 3 2021-11-08 07:20:38 PST
*** This bug has been marked as a duplicate of bug 232810 ***
Note You need to log in before you can comment on or make changes to this bug.