I just wanted to learn about Websockets (from an on-the-wire network view), but it seems the combination of the code at https://blittle.github.io/chrome-dev-tools/network/websockets.html and my Chrome (on Windows Version 90.0.4430.93 (Official Build) (64-bit) ) is causing errors as below and attached. I presuming the API changes are the most relevant.
Error with Permissions-Policy header: Unrecognized feature: 'interest-cohort'.
websockets.html:2 [Deprecation] Application Cache API manifest selection is deprecated and will be removed in M85, around August 2020. See https://www.chromestatus.com/features/6192449487634432 for more details.
websockets.html:1 Creating Application Cache with manifest https://blittle.github.io/chrome-dev-tools/manifest.appcache
websockets.html:1 Application Cache Checking event
websockets.html:1 Application Cache Error event: Invalid or missing manifest origin trial token: https://blittle.github.io/chrome-dev-tools/manifest.appcache
websockets.js:17 Mixed Content: The page at 'https://blittle.github.io/chrome-dev-tools/network/websockets.html' was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint 'ws://echo.websocket.org/'. This request has been blocked; this endpoint must be available over WSS.
testWebSocket @ websockets.js:17
init @ websockets.js:13
(anonymous) @ websockets.js:63
(anonymous) @ websockets.js:64
websockets.js:17 Uncaught DOMException: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS.
at testWebSocket (https://blittle.github.io/chrome-dev-tools/network/websockets.js:17:15)
at init (https://blittle.github.io/chrome-dev-tools/network/websockets.js:13:3)
at https://blittle.github.io/chrome-dev-tools/network/websockets.js:63:2
at https://blittle.github.io/chrome-dev-tools/network/websockets.js:64:2
testWebSocket @ websockets.js:17
init @ websockets.js:13
(anonymous) @ websockets.js:63
(anonymous) @ websockets.js:64
websockets.html:1 Mixed Content: The page at 'https://blittle.github.io/chrome-dev-tools/network/websockets.html' was loaded over HTTPS, but requested an insecure script 'http://cdn.mathjax.org/mathjax/2.0-latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML'. This request has been blocked; the content must be served over HTTPS.
plugin.js:2 Uncaught ReferenceError: MathJax is not defined
at plugin.js:2
at Object.execCb (app.js:1)
at n.check (app.js:1)
at n.enable (app.js:1)
at n.init (app.js:1)
at app.js:1
(anonymous) @ plugin.js:2
execCb @ app.js:1
check @ app.js:1
enable @ app.js:1
init @ app.js:1
(anonymous) @ app.js:1
setTimeout (async)
req.nextTick @ app.js:1
s @ app.js:1
requirejs @ app.js:1
(anonymous) @ plugin.js:1
websockets.js:54 Uncaught ReferenceError: websocket is not defined
at doSend (websockets.js:54)
at HTMLButtonElement.document.getElementById.onclick (websockets.js:7)
doSend @ websockets.js:54
document.getElementById.onclick @ websockets.js:7
I just wanted to learn about Websockets (from an on-the-wire network view), but it seems the combination of the code at https://blittle.github.io/chrome-dev-tools/network/websockets.html and my Chrome (on Windows Version 90.0.4430.93 (Official Build) (64-bit) ) is causing errors as below and attached. I presuming the API changes are the most relevant.
Error with Permissions-Policy header: Unrecognized feature: 'interest-cohort'.
websockets.html:2 [Deprecation] Application Cache API manifest selection is deprecated and will be removed in M85, around August 2020. See https://www.chromestatus.com/features/6192449487634432 for more details.
websockets.html:1 Creating Application Cache with manifest https://blittle.github.io/chrome-dev-tools/manifest.appcache
websockets.html:1 Application Cache Checking event
websockets.html:1 Application Cache Error event: Invalid or missing manifest origin trial token: https://blittle.github.io/chrome-dev-tools/manifest.appcache
websockets.js:17 Mixed Content: The page at 'https://blittle.github.io/chrome-dev-tools/network/websockets.html' was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint 'ws://echo.websocket.org/'. This request has been blocked; this endpoint must be available over WSS.
testWebSocket @ websockets.js:17
init @ websockets.js:13
(anonymous) @ websockets.js:63
(anonymous) @ websockets.js:64
websockets.js:17 Uncaught DOMException: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS.
at testWebSocket (https://blittle.github.io/chrome-dev-tools/network/websockets.js:17:15)
at init (https://blittle.github.io/chrome-dev-tools/network/websockets.js:13:3)
at https://blittle.github.io/chrome-dev-tools/network/websockets.js:63:2
at https://blittle.github.io/chrome-dev-tools/network/websockets.js:64:2
testWebSocket @ websockets.js:17
init @ websockets.js:13
(anonymous) @ websockets.js:63
(anonymous) @ websockets.js:64
websockets.html:1 Mixed Content: The page at 'https://blittle.github.io/chrome-dev-tools/network/websockets.html' was loaded over HTTPS, but requested an insecure script 'http://cdn.mathjax.org/mathjax/2.0-latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML'. This request has been blocked; the content must be served over HTTPS.
plugin.js:2 Uncaught ReferenceError: MathJax is not defined
at plugin.js:2
at Object.execCb (app.js:1)
at n.check (app.js:1)
at n.enable (app.js:1)
at n.init (app.js:1)
at app.js:1
(anonymous) @ plugin.js:2
execCb @ app.js:1
check @ app.js:1
enable @ app.js:1
init @ app.js:1
(anonymous) @ app.js:1
setTimeout (async)
req.nextTick @ app.js:1
s @ app.js:1
requirejs @ app.js:1
(anonymous) @ plugin.js:1
websockets.js:54 Uncaught ReferenceError: websocket is not defined
at doSend (websockets.js:54)
at HTMLButtonElement.document.getElementById.onclick (websockets.js:7)
doSend @ websockets.js:54
document.getElementById.onclick @ websockets.js:7