You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RESTCONF defers to RFC 3986 for a definition of URL and its processing
the percent-encoding definition in RFC 3986 says that it MUST NOT be used for some reserved characters
it also explicitly says that two URL strings which are only different in percent-encoding of a reserved character, are in fact two different URLs
the colon : is listed as one of the reserved characters.
So, you could argue that our implementation is broken because it does not accept an URL like this:
/restconf/ds/ietf-datastores:operationa%6C
...because that one should be interpreted as /restconf/ds/ietf-datastores:operational, but I think it would be actually a violation of 3986 if we treated this:
/restconf/ds/ietf-datastores%3Aoperational
...as an URL that's equivalent to /restconf/ds/ietf-datastores:operational.
I think that urllib3/urllib3#3135 is the relevant bugreport for the Python implementation.
But again, this is a complex matter, so if you can point out any standard which says otherwise, please say so.
When sending a RESTCONF request using python requests , it is automatically URL encode as percent-encoded but after 96cbf73 I only get:
If i remove that patch, it works again.
works though.
The text was updated successfully, but these errors were encountered: