Padding is important when you are concatenating base64 encodings of multiple strings.
Padding is not necessary when you are sending a single string.
That brings a very important topic related to base64 encoding which is ‘Is padding necessary’. Before we see an example of Raw STD encoding we want to explain why the raw version of std encoding exists which omits padding characters. This is the same as StdEncoding just that it omits padding characters. This is because ‘+’ is present in STD encoding but in URL encoding ‘+’ is replaced with ‘-‘ RawStdEncoding Then we are printing both the StdEncoding as well as URL Encoding of the above string encodedStringURL := (byte(sample)) Notice that in the above example we have taken the example of the below string sample := "�" OriginalStringBytes, err := (encodedStringURL) Hence it ‘\’ is replaced with ‘_’ĮncodedStringURL := (byte(sample))įmt.Printf("URL Encoding: %s\n", encodedStringURL)ĮncodedStringSTD := (byte(sample))įmt.Printf("STD Encoding: %s\n", encodedStringSTD) For eg ‘+’ will be converted to ‘%2B’ and ‘\’ will be encoded to ‘%2F’ in the URL encoding.įilenames: ‘\’ is used in file paths in both Unix and Windows. URL: In URLs ‘+’ and ‘\’ are further encoded into hexadecimal sequences due to URL encoding thereby further increasing the length of the URL. They are replaced to make them compatible with filenames and URLs. In this, the ‘+’ and ‘\’ sign is replaced with ‘-‘ and ‘_’. It correctly outputs the original string back on decoding URLEncoding Then we are decoding the base64 encoded string back to the original string originalStringBytes, err := (encodedString) Output that in the above example we are encoding the below string using base64 Std encoding sample := := (byte(sample)) Log.Fatalf("Some error occured during base64 decode. OriginalStringBytes, err := (encodedString) Value Encoding Value Encoding Value Encoding Value Encoding It uses the below 64 characters set along with padding character ‘=’. This is the standard base64 encoding which is defined in RFC 4648. Let’s see a detailed example of each StdEncoding It takes the encoded string as an input and returns the original string depending upon which one of the above 4 encodings is used.įunc (enc *Encoding) DecodeString(s string) (byte, error)
DecodeString – Below is the signature of the method.
It takes bytes as an input and returns the base64 encoded string depending upon which one of the above 4 encodings is used.įunc (enc *Encoding) EncodeToString(src byte) string
EncodeToString – Below is the signature of the method.
So it is unpadded base64 URL encoding.Įach of the above encodings is represented by the Encoding structĮncoding struct further defines two methods for encoding and decoding
RawURLEncoding – This is also the same as URL encoding just that it omits padding characters.
RawStdEncoding – This is the same as StdEncoding just that it omits padding characters.
Below is the character set for base64 URL encodingĪBCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789-_
URLEncoding – Same as StdEncoding just that in this, the ‘+’ and ‘\’ sign is replaced with ‘-‘ and ‘_’.
It encodes into below charactersĪBCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/
StdEncoding– Standard 64 characters with padding.
Golang provides an encoding/base64 package that can be used to encode strings to base64 and decode the base64 encoded string back to the original string.
0 kommentar(er)
