During the APP development process, ios data processing is inevitable. During the process of ios' data transmission, JSON data cannot be obtained. At this time, it is the turn of encodeURI and decodeURI.
1、encodeURI,decodeURI
encodeURI: Encode strings as URIs
•ASCII letters and numbers are not encoded, nor are these ASCII punctuation marks (ie: - _ . ! ~ * ' ( ) ).
•The purpose is to encode all URIs, so ASCII punctuation marks (i.e.: ;/?:@&=+$,#) with special meaning in URIs will not be encoded. Therefore, it is not an exaggeration to alias this function to be encodeURL, which is equivalent to PHP's url_encode.
example:
encodeURI("?user=hello The clouds are calm");
// "?user=hello%20%E4%BA%91%E6%B7%A1%E7%84%B6"
decodeURI("?user=hello%20%E4%BA%91%E6%B7%A1%E7%84%B6");
// ?user=hello The clouds are calm
Since encodeURI is the complete encoding of URLs, it is often used for URL jumps:
=encodeURI('/s?word=hello The clouds are calm');
// "/s?word=hello%20%E4%BA%91%E6%B7%A1%E7%84%B6"
Opening this address in each browser will be different:
•The most standardized performance of UI's url (completely encoded according to encodeURI)
• Chrome's url performance is relatively standardized (partially encoded according to encodeURI)
•Firefox's url performance is the most irregular (there is no encodeURI encoding installed at all)
Although the URL performance of each browser is different, the URL is the most readable and the lowest in firefox and chrome.
2. encodeURIComponent and decodeURIComponent
encodeURI encodes the complete URL, while encodeURIComponent encodes the URL parameters, and its encoding characteristics are as follows:
•ASCII letters and numbers are not encoded, nor are these ASCII punctuation marks (i.e.: - _ . ! ~ * ' ( ) ).
•The purpose is to encode the URI part, so ASCII punctuation marks (i.e.: ;/?:@&=+$,#) with special meanings in the URI will be encoded.
encodeURIComponent("?user=hello world");
// "http%3A%2F%%3Fuser%3Dhello%20world"
decodeURIComponent("http%3A%2F%%3Fuser%3Dhello%20world");
// ?user=hello world
Since encodeURIComponent encodes the URL part, it is often used in queryString, hashSearch, hashPath and cookies, such as:
// queryString encoding"?from=" + encodeURIComponent("");
// "?from=http%3A%2F%"
// hashSearch, hashPath encoding"#?from=" + encodeURIComponent("");
// "#?from=http%3A%2F%"
"#!from/" + encodeURIComponent("");
// "#!from/http%3A%2F%"
// cookie encoding = "from=" + encodeURIComponent("");
// "from=http%3A%2F%"
3. Escape and unescape
escape is similar to encodeURI and encodeURIComponent, both encode strings. The difference is that this method does not encode ASCII letters and numbers, nor does it encode these ASCII punctuation marks (i.e.: * @ - _ + . / ) and all other characters are replaced by escaped sequences.
Notice:ECMAScript v3 opposes the use of this method, and the application uses decodeURI() and decodeURIComponent() instead.
The above example of encodeURI and decodeURI for data acquisition of ios is all the content I have shared with you. I hope you can give you a reference and I hope you can support me more.