René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"crypto: getDecoder throws \"AssertionError: Cannot change encoding\" when encoding is \"ucs2\", \"ucs-2\" or \"utf-16le\".","articleBody":"- **v6.3.0**:\n- **Windows 64-bit**:\n\nI've got similar issue as:\n[#5655](https://github.com/nodejs/node-v0.x-archive/issues/5655)\nwhen I'm using as output encoding 'ucs2', 'usc-2' or 'utf-16le'. If I'm using 'utf16le' the code works.\n\nHere is the not working code:\n`var decrypted = decipher.update(value, 'base64', 'usc2');`\n\nOutput:\n\n`Stack:\n    AssertionError: Cannot change encoding\n        at getDecoder (crypto.js:105:3)\n        at Decipheriv.Cipher.update (crypto.js:146:21)`\n\nand here the working one:\n`var decrypted = decipher.update(value, 'base64', 'utf16le');`\n\n[According to the documentation:](https://nodejs.org/api/crypto.html#crypto_decipher_update_data_input_encoding_output_encoding)\n\n\u003e The output_encoding specifies the output format of the enciphered data, and can be 'latin1', 'ascii' or 'utf8'.\n\nthe utf16le is not supported as output encoding, but it works if you specify 'utf16le'.\n\nThe change in [lib/crypto.js](https://github.com/nodejs/node/blob/master/lib/crypto.js#L104) fix the issue with utf-8, but not with utf-16le.\nThere is a function 'normalizeEncoding' in [lib/internal/util.js](https://github.com/nodejs/node/blob/master/lib/internal/util.js#L109) that can be used to normalize the encoding.\n","author":{"url":"https://github.com/atstoyanov","@type":"Person","name":"atstoyanov"},"datePublished":"2016-08-23T13:17:57.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/8236/node/issues/8236"}