[jira] [Updated] (IGNITE-1773) REST API should accept replace(), put() and other modifying calls via HTTP POST not HTTP GET

["Michael Griggs (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Griggs updated IGNITE-1773:
-----------------------------------
    Summary: REST API should accept replace(), put() and other modifying calls via HTTP POST not HTTP GET  (was: replace(), put() or similar modifying operations cannot be made via the REST API)

> REST API should accept replace(), put() and other modifying calls via HTTP POST not HTTP GET
> --------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-1773
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1773
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: ignite-1.4
>            Reporter: Michael Griggs
>
> The replace() method requires a key and a newVal to be supplied, both of type String. If my newVal is of type JSON then I have to put this data on the URI, because replace() is an HTTP GET method. If this JSON has non-URI safe characters (very likely it will) then it has to be URL-encoded. However, it is not correctly decoded when retrieved from the cache. 
> If I do
> ignite/?cmd=replace&key=mykey&value=[URL-encoded json-data]&cacheName=c 
> followed by
> ignite /?cmd=get&key=mykey
> then the data that is returned from the get() has all of the double quotes escaped with the "\" character. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)