Before you submit transcoding jobs to ApsaraVideo Media Processing, you must perform URL encoding on the file path where your file resides. Otherwise, you may fail to locate the file that you want to transcode. This topic describes the URL encoding method for ApsaraVideo Media Processing.
URL encoding method
ApsaraVideo Media Processing conforms with the RFC2396 specification for UTF-8 URL encoding. For example, Alibaba Cloud/mts HD +.mp4 is encoded as Alibaba%20Cloud/mts%20HD%2B.mp4. For more information, see RFC2396.
Comparison between URL encoding standards
ApsaraVideo Media Processing conforms with the RFC2396 specification for URL encoding. Characters such as spaces and plus signs (+) are encoded differently based on the implemented specification, as shown in the following examples:
| Encoding specification | Space (' ') | Plus sign ('+') |
|---|---|---|
| x-www-form-urlencoded | '+' | '%2B'Note Spaces are encoded as plus signs in x-www-form-urlencoded to indicate connections. Therefore, plus signs must be escaped. |
| RFC1738 | '%20' | '+' |
| RFC2396 | '%20' | '%2B'Note The plus sign is a reserved word in RFC2396 and therefore must be escaped. |
| RFC3986 | '%20' | '%2B' |
Note mark is a reserved word in RFC3986 and therefore must be escaped. mark does not need to be escaped in RFC2396.