Encoding
Last updated
Last updated
It can be useful to convert bytes to strings. For example, to represent or to create shareable and public keys. Hex and Base64 encoding can be used to do this.
Returns the hexadecimal string that represents the data.
data
has a length of 0.
The data could not be converted to hex. This should never be thrown.
Returns a byte array from a hexadecimal string. Common separator characters are ignored by default. ignoreChars
can be null
to disallow any non-hexadecimal characters.
hex
is null.
hex
has a length of 0.
Unable to parse the hex string.
Returns the Base64 string representing the data. Choose one variant (e.g. Base64URL for file names/URLs) and only ever use that variant.
data
has a length of 0.
The data could not be converted to Base64. This should never be thrown.
Returns a byte array from a Base64 string. The variant must match the one used for encoding. ignoreChars
can be null
to disallow any non-Base64 characters.
base64
is null.
base64
has a length of 0.
Unable to parse the Base64 string.
Do NOT support multiple variants of Base64 in your application (e.g. Base64 with and without padding). This can lead to .
Unlike in the .NET library, these functions run in constant time to avoid potential . Furthermore, the Base64 implementation should be more resistant to .
Base64 has a better compression rate than hex. However, they tend to be used for different purposes. For instance, hex is often used for and , whereas Base64 is more commonly used for .