[
https://issues.apache.org/jira/browse/GEODE-7938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072951#comment-17072951
]
ASF subversion and git services commented on GEODE-7938:
--------------------------------------------------------
Commit 0cb54ca91cd874a42b9b8ec5a9bafdda35e0e6a9 in geode's branch
refs/heads/develop from Darrel Schneider
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=0cb54ca ]
GEODE-7938: change dev rest api to support slashes in key parameters (#4885)
* Now uses ** instead of {keys}. This allows keys
to have a slash in them without the client needing
to encode the keys. Since the server no longer decodes
then this should not break any existing use cases.
* The swagger UI does not know what to do with ** but swagger docs were added
describing that ** is a comma separated list of keys.
> dev rest api should allow '.' and '/' characters in region keys
> ---------------------------------------------------------------
>
> Key: GEODE-7938
> URL: https://issues.apache.org/jira/browse/GEODE-7938
> Project: Geode
> Issue Type: Bug
> Components: rest (dev)
> Reporter: Darrel Schneider
> Assignee: Darrel Schneider
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The dev rest api has multiple endpoints that can take region entry keys
> either as path variables or as query parameters. If the key contains a "/"
> then it can cause problems with parsing the URL. The '.' character also
> causes problems.
> The operations and endpoints that do not allow '.' and '/' in region keys are:
> {noformat}
> GET, PUT, and DELETE on /v1/{region}/{keys}
> POST on /v1/{region}?key={key}
> {noformat}
> A solution should be found that does not break backwards compatibility but
> that also allows these characters to be in the specified region key(s).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
