- From: Philippe Le Hegaret <plh@w3.org>
- Date: Fri, 27 Mar 2015 09:02:21 -0400
- To: Arthur Barstow <art.barstow@gmail.com>,Mike Smith <mike@w3.org>
- CC: "team-webapps@w3.org" <team-webapps@w3.org>,"www-archive@w3.org" <www-archive@w3.org>
- Message-ID: <44B6CD37-A92D-4CC3-882C-7BEBD0CEF7E1@w3.org>
I don't think anyone is working on this but I will check, Philippe On March 27, 2015 8:58:22 AM EDT, Arthur Barstow <art.barstow@gmail.com> wrote: >[ Cc: www-archive ] > >Hi PLH, All, > >Below is a list of the 41 Web Socket test failures related to what >appears to be a lack of wss: support for the Web Socket test server >running on w3c-test.org. > >Mike said this is a known limitation. Is anyone working on fixing this, > >and if so, what is the rough ETA? > >-Thanks, AB > ><http://w3c.github.io/test-results/websockets/all.html> > >* All 41 of these failures have 4 "ERRORS" (Chrome, Canary, FF and IE) >and 1 TIMEOUT (Opera) > >/websockets/Create-Secure-valid-url-array-protocols.htm >/websockets/Create-Secure-valid-url-binaryType-blob.htm >/websockets/Create-Secure-valid-url-protocol-setCorrectly.htm >/websockets/Create-Secure-valid-url-protocol-string.htm >/websockets/Create-Secure-valid-url.htm > >/websockets/Secure-Close-0.htm >/websockets/Secure-Close-1000-reason.htm >/websockets/Secure-Close-1000-verify-code.htm >/websockets/Secure-Close-1000.htm >/websockets/Secure-Close-1005-verify-code.htm >/websockets/Secure-Close-1005.htm >/websockets/Secure-Close-2999-reason.htm >/websockets/Secure-Close-3000-reason.htm >/websockets/Secure-Close-3000-verify-code.htm >/websockets/Secure-Close-4999-reason.htm >/websockets/Secure-Close-NaN.htm >/websockets/Secure-Close-Reason-124Bytes.htm >/websockets/Secure-Close-Reason-Unpaired-surrogates.htm >/websockets/Secure-Close-null.htm >/websockets/Secure-Close-onlyReason.htm >/websockets/Secure-Close-readyState-Closed.htm >/websockets/Secure-Close-readyState-Closing.htm >/websockets/Secure-Close-server-initiated-close.htm >/websockets/Secure-Close-string.htm >/websockets/Secure-Close-undefined.htm > >/websockets/Secure-Send-65K-data.htm >/websockets/Secure-Send-binary-65K-arraybuffer.htm >/websockets/Secure-Send-binary-arraybuffer.htm >/websockets/Secure-Send-binary-arraybufferview-float64.htm >/websockets/Secure-Send-binary-arraybufferview-int32.htm >/websockets/Secure-Send-binary-arraybufferview-uint16-offset-length.htm >/websockets/Secure-Send-binary-arraybufferview-uint32-offset.htm >/websockets/Secure-Send-binary-arraybufferview-uint8-offset-length.htm >/websockets/Secure-Send-binary-arraybufferview-uint8-offset.htm >/websockets/Secure-Send-binary-blob.htm >/websockets/Secure-Send-data.htm >/websockets/Secure-Send-null.htm >/websockets/Secure-Send-paired-surrogates.htm >/websockets/Secure-Send-unicode-data.htm >/websockets/Secure-Send-unpaired-surrogates.htm > >/websockets/binaryType-wrong-value.htm -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Received on Friday, 27 March 2015 13:02:40 UTC