bug (?) in the REST API

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

bug (?) in the REST API

ffraticelli
This post was updated on .
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 fewer '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/device

With the actual token (without the f list) t doesn't work either, 400 error.

Reply | Threaded
Open this post in threaded view
|

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

Sebastien Blanc

On Fri, Apr 15, 2016 at 4:07 PM, ffraticelli <[hidden email]> wrote:
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/device With the actual token (without the f list) t doesn't work either, 400 error.

View this message in context: bug (?) in the REST API
Sent from the aerogear-users mailing list archive at Nabble.com.

_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users



_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users
Reply | Threaded
Open this post in threaded view
|

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

Matthias Wessendorf
In reply to this post by ffraticelli
Hi,

I am unable to reproduce the problem, using latest 1.2.0-alpha.1, both tokens worked, for an iOS variant:
* fffffffffffffffffffffffffffffffffffffe432da6199aa9b1c49f6ab99f7e20bdf9ae5df25569e7b43fc550c6c461aecd
* ffffffffffffffffffffffffffffffffffffe432da6199aa9b1c49f6ab99f7e20bdf9ae5df25569e7b43fc550c6c461aecd

What's the version you are on? 

-Matthias



On Fri, Apr 15, 2016 at 4:07 PM, ffraticelli <[hidden email]> wrote:
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/device With the actual token (without the f list) t doesn't work either, 400 error.

View this message in context: bug (?) in the REST API
Sent from the aerogear-users mailing list archive at Nabble.com.

_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users




--

_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users
Reply | Threaded
Open this post in threaded view
|

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

ffraticelli
In reply to this post by Sebastien Blanc
It could be the token validator, I don't have a developer platform and I cannot debug it on my own.

The real (following) token doesn't pass through:
fe432da6199aa9b1c49f6ab99f7e20bdf9ae5df25569e7b43fc550c6c461aecd

I tested the above token with other push servers and it works for both registration and notification receiving.
Reply | Threaded
Open this post in threaded view
|

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

Matthias Wessendorf
ok, looking!

Mind sharing the version ? 


On Fri, Apr 15, 2016 at 4:29 PM, ffraticelli <[hidden email]> wrote:
It could be the token validator, I don't have a developer platform and I
cannot debug it on my own.

The real (following) token doesn't pass through:
fe432da6199aa9b1c49f6ab99f7e20bdf9ae5df25569e7b43fc550c6c461aecd

I tested the above token with other push servers and it works for both
registration and notification receiving.



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/bug-in-the-REST-API-tp592p595.html
Sent from the aerogear-users mailing list archive at Nabble.com.
_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users



--

_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users
Reply | Threaded
Open this post in threaded view
|

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

ffraticelli
Sure.
 
AeroGear UnifiedPush Server 1.1.0.Final and WildFly

Reply | Threaded
Open this post in threaded view
|

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

Matthias Wessendorf
I am now checking 1.1.2 :) 

will let you know in a bit 

On Fri, Apr 15, 2016 at 4:32 PM, ffraticelli <[hidden email]> wrote:
Sure.

AeroGear UnifiedPush Server 1.1.0.Final and WildFly





--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/bug-in-the-REST-API-tp592p597.html
Sent from the aerogear-users mailing list archive at Nabble.com.
_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users



--

_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users
Reply | Threaded
Open this post in threaded view
|

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

Matthias Wessendorf
On UPS 1.1.2, it works:

Here is my CURL:
curl -u "96c9e3f4-f503-48a1-ab47-0c651df696ab:b62414df-4581-4d6d-92d0-5e9a249674ef" -v -H "Accept: application/json" -H "Content-type: application/json" -X POST -d '{"deviceToken" : "fe432da6199aa9b1c49f6ab99f7e20bdf9ae5df25569e7b43fc550c6c461aecd", "deviceType" : "iPhone"}' https://tokentest-pushee.rhcloud.com/ag-push/rest/registry/device

and here is the variant, with that one token:


-Matthias



On Fri, Apr 15, 2016 at 4:32 PM, Matthias Wessendorf <[hidden email]> wrote:
I am now checking 1.1.2 :) 

will let you know in a bit 

On Fri, Apr 15, 2016 at 4:32 PM, ffraticelli <[hidden email]> wrote:
Sure.

AeroGear UnifiedPush Server 1.1.0.Final and WildFly





--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/bug-in-the-REST-API-tp592p597.html
Sent from the aerogear-users mailing list archive at Nabble.com.
_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users



--



--

_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users
Reply | Threaded
Open this post in threaded view
|

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

ffraticelli
Wow, that was fast :)
Thanks a lot.

Do you know if there is any plan for openshift to upgrade their UPS version?
Reply | Threaded
Open this post in threaded view
|

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

Matthias Wessendorf
I also did on 1.1.0:

curl -u "7c1e9096-7409-4f05-97ce-79ce7d02ea48:d6c26bbb-5534-4eaf-92c3-86bb379e072e" -v -H "Accept: application/json" -H "Content-type: application/json" -X POST -d '{"deviceToken" : "fe432da6199aa9b1c49f6ab99f7e20bdf9ae5df25569e7b43fc550c6c461aecd", "deviceType" : "iPad", "operatingSystem" : "iOS", "osVersion" : "6.1.2"}' https://someolderpush-pushee.rhcloud.com/ag-push/rest/registry/device


works too - sorry !


but caution :-) ATM there is no 'update' feature enabled on our AeroGear UPS cartridge

On Fri, Apr 15, 2016 at 4:40 PM, ffraticelli <[hidden email]> wrote:
Wow, that was fast :)
Thanks a lot.

Do you know if there is any plan for openshift to upgrade their UPS version?



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/bug-in-the-REST-API-tp592p600.html
Sent from the aerogear-users mailing list archive at Nabble.com.
_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users



--

_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users
Reply | Threaded
Open this post in threaded view
|

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

Matthias Wessendorf
btw... can you share details about the variant ? 

and, is the cartridge installed on a 'medium' sized machine? the (free) default (small) is not working

On Fri, Apr 15, 2016 at 4:47 PM, Matthias Wessendorf <[hidden email]> wrote:
I also did on 1.1.0:

curl -u "7c1e9096-7409-4f05-97ce-79ce7d02ea48:d6c26bbb-5534-4eaf-92c3-86bb379e072e" -v -H "Accept: application/json" -H "Content-type: application/json" -X POST -d '{"deviceToken" : "fe432da6199aa9b1c49f6ab99f7e20bdf9ae5df25569e7b43fc550c6c461aecd", "deviceType" : "iPad", "operatingSystem" : "iOS", "osVersion" : "6.1.2"}' https://someolderpush-pushee.rhcloud.com/ag-push/rest/registry/device


works too - sorry !


but caution :-) ATM there is no 'update' feature enabled on our AeroGear UPS cartridge

On Fri, Apr 15, 2016 at 4:40 PM, ffraticelli <[hidden email]> wrote:
Wow, that was fast :)
Thanks a lot.

Do you know if there is any plan for openshift to upgrade their UPS version?



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/bug-in-the-REST-API-tp592p600.html
Sent from the aerogear-users mailing list archive at Nabble.com.
_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users



--



--

_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users
Reply | Threaded
Open this post in threaded view
|

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

ffraticelli
it's the free default (small) gear. 1 GB

it works for registering and sending notifications, but it's not 100% stable and has this unfortunate bug (version 1.0)

Fausto

-----[hidden email] wrote: -----
To: "[hidden email]" <[hidden email]>
From: Matthias Wessendorf
Sent by: [hidden email]
Date: 04/15/2016 04:51PM
Subject: Re: [Aerogear-users] bug (?) in the REST API

btw... can you share details about the variant ? 

and, is the cartridge installed on a 'medium' sized machine? the (free) default (small) is not working

On Fri, Apr 15, 2016 at 4:47 PM, Matthias Wessendorf <[hidden email]> wrote:
I also did on 1.1.0:

curl -u "7c1e9096-7409-4f05-97ce-79ce7d02ea48:d6c26bbb-5534-4eaf-92c3-86bb379e072e" -v -H "Accept: application/json" -H "Content-type: application/json" -X POST -d '{"deviceToken" : "fe432da6199aa9b1c49f6ab99f7e20bdf9ae5df25569e7b43fc550c6c461aecd", "deviceType" : "iPad", "operatingSystem" : "iOS", "osVersion" : "6.1.2"}' https://someolderpush-pushee.rhcloud.com/ag-push/rest/registry/device


works too - sorry !


but caution :-) ATM there is no 'update' feature enabled on our AeroGear UPS cartridge

On Fri, Apr 15, 2016 at 4:40 PM, ffraticelli <[hidden email]> wrote:
Wow, that was fast :)
Thanks a lot.

Do you know if there is any plan for openshift to upgrade their UPS version?



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/bug-in-the-REST-API-tp592p600.html
Sent from the aerogear-users mailing list archive at Nabble.com.
_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users



--



--
_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users

_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users
Reply | Threaded
Open this post in threaded view
|

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

Matthias Wessendorf
Hello Fausto!

ok, be my guest and use my 'tokentest' version :-) 
Please don't use the someolderpush version - thanks!

Oh, are you OK I delete my variant/app ? 

You are currently evaluating the UPS for usage at the UN? In case your mgmt team approves it will be used inside the UN's Docker farm?
Mind keeping me up-to-date, if UPS usage was approved? 

PS: we also have Docker images for UPS ;-)

Thanks,
Matthias



On Fri, Apr 15, 2016 at 5:03 PM, Fausto FRATICELLI <[hidden email]> wrote:
it's the free default (small) gear. 1 GB

it works for registering and sending notifications, but it's not 100% stable and has this unfortunate bug (version 1.0)

Fausto

-----[hidden email] wrote: -----
To: "[hidden email]" <[hidden email]>
From: Matthias Wessendorf
Sent by: [hidden email]
Date: 04/15/2016 04:51PM
Subject: Re: [Aerogear-users] bug (?) in the REST API


btw... can you share details about the variant ? 

and, is the cartridge installed on a 'medium' sized machine? the (free) default (small) is not working

On Fri, Apr 15, 2016 at 4:47 PM, Matthias Wessendorf <[hidden email]> wrote:
I also did on 1.1.0:

curl -u "7c1e9096-7409-4f05-97ce-79ce7d02ea48:d6c26bbb-5534-4eaf-92c3-86bb379e072e" -v -H "Accept: application/json" -H "Content-type: application/json" -X POST -d '{"deviceToken" : "fe432da6199aa9b1c49f6ab99f7e20bdf9ae5df25569e7b43fc550c6c461aecd", "deviceType" : "iPad", "operatingSystem" : "iOS", "osVersion" : "6.1.2"}' https://someolderpush-pushee.rhcloud.com/ag-push/rest/registry/device


works too - sorry !


but caution :-) ATM there is no 'update' feature enabled on our AeroGear UPS cartridge

On Fri, Apr 15, 2016 at 4:40 PM, ffraticelli <[hidden email]> wrote:
Wow, that was fast :)
Thanks a lot.

Do you know if there is any plan for openshift to upgrade their UPS version?



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/bug-in-the-REST-API-tp592p600.html
Sent from the aerogear-users mailing list archive at Nabble.com.
_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users



--



--
_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users

_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users




--

_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users