René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Already buffered data when creating a TLSSocket doesn't trigger/throw 'error'","articleBody":"Brought over from https://github.com/joyent/node/issues/9355\n\nIf you pass a socket with already buffered data to TLSSocket and there's an error like:\n\n```\n[Error: 139745410942944:error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher:s3_srvr.c:1352]\n```\n\nIt will fire as a `_tlsError` immediately while in the constructor instead of either throwing an error (if there were no error handlers) or waiting till the next tick to fire the `_tlsError`.\n\nThis can be solved by wrapping `this._init(socket)` in a `process.nextTick` or delaying:\n\n```\n  // Socket already has some buffered data - emulate receiving it\n  if (socket \u0026\u0026 socket._readableState.length) {\n    var buf;\n    while ((buf = socket.read()) !== null)\n      this.ssl.receive(buf);\n  }\n```\n\nIt seems like the second option (delaying the initial buffer read) is better but let me know what you guys think.\n","author":{"url":"https://github.com/jameshartig","@type":"Person","name":"jameshartig"},"datePublished":"2015-03-10T07:29:09.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":6},"url":"https://github.com/1114/node/issues/1114"}