[Aerogear-users] bug (?) in the REST API

ffraticelli ffraticelli at unog.ch
Fri Apr 15 10:07:32 EDT 2016


Hello, I found this (blocking) issue using the REST API for registering
devices.It's a test container, you can use the commands below and I will
delete the variant once this issue is confirmed by your team.The following
curl works and registers the device token:   curl -u
"daa39c18-fdae-4696-b24f-041008f8a28a:a3186331-5e54-48b1-be2f-30b348d9dd40" 
\   -v -H "Accept: application/json" -H "Content-type: application/json" -H
"aerogear-push-id: someid" \   -X POST  -d \  '{     "deviceToken" :
"fffffffffffffffffffffffffffffffffffffe432da6199aa9b1c49f6ab99f7e20bdf9ae5df25569e7b43fc550c6c461aecd",    
"deviceType" : "iPad",     "operatingSystem" : "iOS",     "osVersion" :
"6.1.2"   }'  \  
https://aerogear-unog.rhcloud.com/ag-push/rest/registry/device*While the
following receives an HTTP 400 Bad Request. The only different between the 2
is an additional 'f' in the following token.*   curl -u
"daa39c18-fdae-4696-b24f-041008f8a28a:a3186331-5e54-48b1-be2f-30b348d9dd40" 
\   -v -H "Accept: application/json" -H "Content-type: application/json" -H
"aerogear-push-id: someid" \   -X POST  -d \  '{     "deviceToken" :
"ffffffffffffffffffffffffffffffffffffe432da6199aa9b1c49f6ab99f7e20bdf9ae5df25569e7b43fc550c6c461aecd",    
"deviceType" : "iPad",     "operatingSystem" : "iOS",     "osVersion" :
"6.1.2"   }'  \  
https://aerogear-unog.rhcloud.com/ag-push/rest/registry/deviceWith the
actual token (without the f list) t doesn't work either, 400 error.



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/bug-in-the-REST-API-tp592.html
Sent from the aerogear-users mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160415/f4ba0289/attachment-0001.html 


More information about the Aerogear-users mailing list