[
https://issues.apache.org/jira/browse/GEODE-7938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072941#comment-17072941
]
Darrel Schneider edited comment on GEODE-7938 at 4/1/20, 4:32 PM:
------------------------------------------------------------------
The solution is to change the endpoint from:
{noformat}
/{region}/{keys}
{noformat}
to:
{noformat}
/{region}/**
{noformat}
This allows the server code to parse ** as the keys without giving special
meaning to '/' and '.'.
was (Author: dschneider):
The solution is to change the endpoint from "/{keys}" to "/**". This allows the
server code to parse ** as the keys without giving special meaning to '/' and
'.'.
> 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
>
> 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)
