- From: qingxinwu <notifications@github.com>
- Date: Wed, 22 Mar 2023 09:35:20 -0700
- To: whatwg/url <url@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 22 March 2023 16:35:32 UTC
Sorry, after a closing look, I was wrong about our code using `application/x-www-form-urlencoded`. It seems it uses [component percent-encode set](https://url.spec.whatwg.org/#component-percent-encode-set), since [EscapeQueryParamValue](https://crsrc.org/c/base/strings/escape.h;drc=b4bc946c63b2b95e1f05dec4e84adcadd10499c6;l=29) does not encode `!'()~`. So I think we cannot use urlencoded-serializer. I think we didn't invent a key/value format. It's still `&key=value`, but different values of a key are concatenated using commas, e.g., "https://a.com?&key1=value1,value11&key2=value2,value22...". I think our use case needs an entry point which allows setting `percentEncodeSet` to "component percent-encode set" and `percentEncodeSet` to true. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/url/issues/765#issuecomment-1479901737 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/url/issues/765/1479901737@github.com>
Received on Wednesday, 22 March 2023 16:35:32 UTC