问题
I picked this character 〉 as a separator for my combo-key-field for my DynamoDb database.
That character surfaces in the browser as part of a next-page-query token. (in an endless scroll list view)
Chrome properly sends that character to the backend (as part of the next-page-query token).
However, Safari, sends that character as this character: 〉, which is different, and as a result, my backend is unable to recognise it.
Why is the browser changing the character? Is this behaviour expected? Did I miss declaring a char-set somewhere?
Probably an important finding is that running '〉' === '〉' returns true in Safari.
wAt?
来源：https://stackoverflow.com/questions/65167158/how-to-prevent-safari-from-implicitly-converting-character-in-xhr-request