Try attaching this page: More complex privilege management with setpriv
Hey @olejorgenb
You can try to encode the web URI with %2c
as the comma part.
Many URI include components consisting of or delimited by, certain special characters. These characters are called “reserved”, since their usage within the URI component is limited to their reserved purpose. If the data for a URI component would conflict with the reserved purpose, then the conflicting data must be escaped before forming the URI.
I hope that helps
Thanks for the suggested workaround.
I would say this is something Cody should handle though. If I read RFC 3986 - Uniform Resource Identifier (URI): Generic Syntax correctly ,
is indeed “reserved”, but that doesn’t mean it’s required to be encoded:
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.
Even if that’s a misunderstanding on my part wild-life URL use ,
unencoded and I don’s see any reason why the UI for URL entry couldn’t handle this for me?