File Explorer

/var/runtime/node_modules/@aws-sdk/node_modules/mqtt/lib/connect

This explorer reads the filesystem of the server it runs on, so /workspace/user isn't present here. Browsing and the terminal still work against this server's own disk from /.

tls.js1.4 KB · 49 lines
'use strict'const tls = require('tls')const net = require('net')const debug = require('debug')('mqttjs:tls') function buildBuilder (mqttClient, opts) {  opts.port = opts.port || 8883  opts.host = opts.hostname || opts.host || 'localhost'   if (net.isIP(opts.host) === 0) {    opts.servername = opts.host  }   opts.rejectUnauthorized = opts.rejectUnauthorized !== false   delete opts.path   debug('port %d host %s rejectUnauthorized %b', opts.port, opts.host, opts.rejectUnauthorized)   const connection = tls.connect(opts)  /* eslint no-use-before-define: [2, "nofunc"] */  connection.on('secureConnect', function () {    if (opts.rejectUnauthorized && !connection.authorized) {      connection.emit('error', new Error('TLS not authorized'))    } else {      connection.removeListener('error', handleTLSerrors)    }  })   function handleTLSerrors (err) {    // How can I get verify this error is a tls error?    if (opts.rejectUnauthorized) {      mqttClient.emit('error', err)    }     // close this connection to match the behaviour of net    // otherwise all we get is an error from the connection    // and close event doesn't fire. This is a work around    // to enable the reconnect code to work the same as with    // net.createConnection    connection.end()  }   connection.on('error', handleTLSerrors)  return connection} module.exports = buildBuilder