On Fri, Dec 2, 2016 at 5:56 AM, Robert Haas <robertmh...@gmail.com> wrote:
> On Fri, Nov 25, 2016 at 4:16 AM, Mithun Cy <mithun...@enterprisedb.com> wrote:
>> Reason is we first decode the URI(percent encoded character) then try to
>> split the string into multiple host assuming they are separated by ','. I
>> think we need to change the order here. Otherwise difficult the say whether
>> ',' is part of USD path or a separator.
> Yeah, we should change that. Are you going to write a patch?
The interesting bit in rfc3986:
Aside from dot-segments in hierarchical paths, a path segment is
considered opaque by the generic syntax. URI producing applications
often use the reserved characters allowed in a segment to delimit
scheme-specific or dereference-handler-specific subcomponents. For
example, the semicolon (";") and equals ("=") reserved characters are
often used to delimit parameters and parameter values applicable to
that segment. The comma (",") reserved character is often used for
similar purposes. For example, one URI producer might use a segment
such as "name;v=1.1" to indicate a reference to version 1.1 of
"name", whereas another might use a segment such as "name,1.1" to
indicate the same. Parameter types may be defined by scheme-specific
semantics, but in most cases the syntax of a parameter is specific to
the implementation of the URI's dereferencing algorithm.
So not being able to distinguish commas in names and separators is
clearly a bug.
Sent via pgsql-hackers mailing list (email@example.com)
To make changes to your subscription: