This has nothing to do with Riak, but rather how you need to avoid URLs, so the server (including Riak) does not interpret the slash as a path separator:
PUT https://riak:8069/buckets/key/keys/11111%2F2
Then you can get it the same way:
GET https://riak:8069/riak/key/11111%2F2
%2F is the value / when using URL Encoding - if your keys contain characters that are considered special characters in URLs, you need to do this with your keys.
You can make sure that this worked correctly in Riak by specifying the keys in your key bucket (on the test server - do not do this on the production server, as it is very expensive):
GET https://riak:8069/riak/key?keys=true
At the end of the JSON output, you will find:
... "keys":[...,"11111/2",...]}
source share