1berry/nodejs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc: encoding is ignored if input is a Buffer

Browse Source 
NOTE: it wasn't in 0.8

fixes #6386
This commit is contained in:
Fedor Indutny 2013-10-21 16:26:29 +04:00 committed by Timothy J Fontaine
parent 849c92fec7
commit 0be5a94c56
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
doc/api/crypto.markdown
View File

@ -101,6 +101,7 @@ Returned by `crypto.createHash`.
Updates the hash content with the given `data`, the encoding of which
is given in `input_encoding` and can be `'utf8'`, `'ascii'` or
`'binary'`. If no encoding is provided, then a buffer is expected.
If `data` is a `Buffer` then `input_encoding` is ignored.
This can be called many times with new data as it is streamed.
@ -191,6 +192,7 @@ methods are also supported.
Updates the cipher with `data`, the encoding of which is given in
`input_encoding` and can be `'utf8'`, `'ascii'` or `'binary'`. If no
encoding is provided, then a buffer is expected.
If `data` is a `Buffer` then `input_encoding` is ignored.
The `output_encoding` specifies the output format of the enciphered
data, and can be `'binary'`, `'base64'` or `'hex'`. If no encoding is
@ -243,6 +245,7 @@ plain-text data on the the readable side. The legacy `update` and
Updates the decipher with `data`, which is encoded in `'binary'`,
`'base64'` or `'hex'`. If no encoding is provided, then a buffer is
expected.
If `data` is a `Buffer` then `input_encoding` is ignored.
The `output_decoding` specifies in what format to return the
deciphered plaintext: `'binary'`, `'ascii'` or `'utf8'`. If no