Why Is This Website Port Scanning Me?

Re:Why Is This Website Port Scanning Me? by homami on Wednesday May 20, 2020 @04:08PM (#23251165)

How does it work in practice? It seems in Chrome these errors cannot be caught try-catch blocks.

    try {
      var socket = new WebSocket('ws://localhost:808');
    }
    catch (ex) {
      console.log(ex) // control does not reach here
    }

[ Parent | on HN ]

Re:Why Is This Website Port Scanning Me? by mdouglass on Wednesday May 20, 2020 @04:19PM (#23251286)

It probably fires as an async error, I'd expect this would log it (if inserted at the end of the try block):

    socket.onerror = (...args) => console.log('async error', ...args)

[ Parent | on HN ]

Re:Why Is This Website Port Scanning Me? by homami on Wednesday May 20, 2020 @04:35PM (#23251452)

socket.onerror event happens for both cases. But there does not seem to be any difference between the error object that is passed to the these handlers.

[ Parent | on HN ]