Hi Team,
Upon checking one of the issue with the client I learnt about the concept of URL encoding which converts few keywords in the URL to a different keywords(ASCII).
Since URLs often contain characters outside the ASCII set, the URL has to be converted into a valid ASCII format. URL encoding replaces unsafe ASCII characters with a “%” followed by two hexadecimal digits, URLs cannot contain spaces. URL encoding normally replaces a space with a plus (+) sign or with %20.
Example: –
Our LeadSquared Access Keys are the perfect example for the same.
If you see our Access keys has the initials as u$ra this usually gets converted as u%24 whenever it is used in the process and this is because URL’s have to be converted into a valid ASCII format to be transmitted over the Internet.
You can refer to the mentioned link for the list of few keywords => https://www.w3schools.com/tags/ref_urlencode.ASP#:~:text=ASCII%20Encoding%20Reference
Summarizing the content :-
You can refer to the mentioned link for the list of few keywords => https://www.w3schools.com/tags/ref_urlencode.ASP#:~:text=ASCII%20Encoding%20Reference
Summarizing the content :-
If the Access keys or the URLs are getting changed on the server level we will have to check for the ASCII values of the changed characters as the characters or the words can be changed because of the URL encoding concept.
