|
|
|
|
|
|
by dillondoyle
1817 days ago
|
|
|
Was going to add this. No IE support. The polyfill below gives a similar example with a caveat of adding a content-type header. It looks like it does escape at least a few ~( etc with function encode. But there are a billion emojis, unicode whatever to escape? I've read in the past that browsers have all kinds of URL quirks, and I've seen examples that i've copied into my own code which base64 encode / decode before sending (or GET an image pixel with params). https://www.npmjs.com/package/url-search-params-polyfill |
|
|