I don't know why it does this, but for example attempting to fetch or post to the key abc/def in the Swagger API explorer will actually fetch or post to abc%2Fdef, the URL-encoded version of the path. This is confusing students using Swagger and the browser/requests to access their database stuff because they are looking at two different keys.
I don't know why it does this, but for example attempting to fetch or post to the key
abc/defin the Swagger API explorer will actually fetch or post toabc%2Fdef, the URL-encoded version of the path. This is confusing students using Swagger and the browser/requests to access their database stuff because they are looking at two different keys.