1 Answer
- Newest
- Most votes
- Most comments
1
From RFC 8187, we see non US-ASCII values require encoding.
By default, header field values in Hypertext Transfer Protocol (HTTP) messages cannot easily carry characters outside the US-ASCII coded character set. [...] This document specifies an encoding suitable for use in HTTP header fields that is compatible with a simplified profile of the encoding defined in RFC 2231.
Patiāla
was UTF-8 character encoded, and then percent-encoded to be Pati%C4%81la
Here is a JavaScript example on how to decode that value:
console.log(decodeURIComponent('Pati%C4%81la'))
answered 6 months ago
Relevant content
- asked 2 years ago
- asked 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 2 months ago
Just letting you know that "Patiala" name shouldn't have accented a character. You can confirm the name on Google Maps. In fact none of the places in India would need special characters.