[
https://issues.apache.org/jira/browse/GEODE-7929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072928#comment-17072928
]
Darrel Schneider commented on GEODE-7929:
-----------------------------------------
Changing the current dev rest api to decode the keys on the server would break
existing users who are not encoding their keys if their keys contain any of the
special characters that decode transforms. For this reason it was decided not
to do this. In the future we may decide to offer a new version of the api that
supports encoded keys so this ticket will not be closed.
> dev rest api should allow utf-8 encoded keys
> --------------------------------------------
>
> Key: GEODE-7929
> URL: https://issues.apache.org/jira/browse/GEODE-7929
> Project: Geode
> Issue Type: Bug
> Components: rest (dev)
> Reporter: Darrel Schneider
> Assignee: Darrel Schneider
> Priority: Major
> Time Spent: 2h
> 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 normal thing a user
> should do is utf-8 encode by changing "/" to "%2F". But this will not work
> since the dev rest api does not decode the keys. It does decode the region
> name.
> The endpoints that are not decoding keys are:
> GET, PUT, and DELETE on /v1/{region}/{keys}
> POST on /v1/{region}?key={key}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
