4 ms·
Revealing my non-nerd credentials: when I click "Get this page, byte by byte" I just see: > We begin the TLS handshake by sending a client hello message (sourc
by JadeNB 3y ago
Revealing my non-nerd credentials: when I click "Get this page, byte by byte" I just see:
> We begin the TLS handshake by sending a client hello message (source):
and nothing else seems to happen, no matter how long I wait. I thought I might have to click the button again, but it just seems to display the same message, no matter how often I click it. What else should I be doing?
- gmac 3y agoHuh, that’s odd. Are you able to open your browser dev tools and check for JS errors in the console?
- JadeNB 3y agoI tried in Firefox, Safari, and Chrome. Here it is from Chrome: > index.js:2231 WebSocket connection to 'wss://ws.manipulexity.com/v1?address=subtls.pages.dev:443' failed: > ws @ index.js:2231 > index.js:2235 ws error: Event [I didn't expand this, but let me know if you need it] > connection closed index.js:2238
- gmac 3y agoHmm. Could you be behind some kind of interfering proxy that doesn't like WebSockets? Does this demo page work for you? https://libwebsockets.org/testserver/ https://libwebsockets.org/testserver/
- JadeNB 3y ago> Hmm. Could you be behind some kind of interfering proxy that doesn't like WebSockets? I'm at work, so it's possible, but I'm not sure. > Does this demo page work for you? https://libwebsockets.org/testserver/ https://libwebsockets.org/testserver/ It shows me a rapidly incrementing number, that resets when I click "reset counter". Nothing obviously happens when I click "send junk". Is that what should happen?
- JadeNB 3y ago> Hmm. Could you be behind some kind of interfering proxy that doesn't like WebSockets? I tried again from home, and it worked fine, so that must be it.
- gmac 3y agoGreat!