The server is currently failing to treat %2c as a comma in the query string. Until this is corrected, frameworks which follow RFC3986 will be unable to use these API calls.
eg.
curl -i -X GET https://test-queue.drivesrvr-dev.com/v1/queues/demonqueue/messages?ids=5255a7078357ea7f647ab658,5255a7078357ea7f647ab659s -H "Content-type: application/json" -H "X-Auth-Token: 5ff778e0fb5446e5bca9bc29330fc7b2" -H "X-Project-Id: 806067" -H "Client-ID: 8944d987-3114-11e3-9a19-28cfe91478b9" -H "Accept: application/json"
HTTP/1.1 200 OK
with encoded URL
curl -i -X GET https://test-queue.drivesrvr-dev.com/v1/queues/demonqueue/messages?ids=5255a7078357ea7f647ab658%2C5255a7078357ea7f647ab659s -H "Content-type: application/json" -H "X-Auth-Token: 5ff778e0fb5446e5bca9bc29330fc7b2" -H "X-Project-Id: 806067" -H "Client-ID: 8944d987-3114-11e3-9a19-28cfe91478b9" -H "Accept: application/json"
HTTP/1.1 204 OK
https:/