According to the examples in OpenAPI
The query in URI could be something like /users?id=3,4,5.
And according to RFC3986:
The purpose of reserved characters is to provide a set of delimiting
characters that are distinguishable from other data within a URI.
URIs that differ in the replacement of a reserved character with its
corresponding percent-encoded octet are not equivalent. Percent-
encoding a reserved character, or decoding a percent-encoded octet
that corresponds to a reserved character, will change how the URI is
interpreted by most applications. Thus, characters in the reserved
set are protected from normalization and are therefore safe to be
used by scheme-specific and producer-specific algorithms for
delimiting data subcomponents within a URI.
I suppose enforcing the percent-encode for reserved characters is not that reasonable. Could you help take a look?
According to the examples in OpenAPI The query in URI could be something like
/users?id=3,4,5
. And according to RFC3986:I suppose enforcing the percent-encode for reserved characters is not that reasonable. Could you help take a look?