On Wed, Jul 10, 2013 at 3:13 PM, Bruno Oliveira <bruno@abstractj.org> wrote:

I'd say "Could not find requested resource"

Don't give too many hints to an attacker :)

yup, I agree. But folks started using the worng IDs, I guess that was motivation. 

HOWEVER :) once the Admin UI is finished, less folks will use the cURL for "managing" PusApps and Variants. So, a pretty generic thing would be enough... I do agree :)

 

Matthias Wessendorf wrote:
>
>
>
> On Tue, Jul 9, 2013 at 8:40 PM, Kris Borchers <kris@redhat.com

> <mailto:kris@redhat.com>> wrote:
>
>
>     On Jul 9, 2013, at 1:38 PM, Matthias Wessendorf <matzew@apache.org

>     <mailto:matzew@apache.org>> wrote:
>
>>     :-)
>>
>>     We recently change the 404, to have some hint:
>>     https://github.com/aerogear/aerogear-unified-push-server/blob/master/src/main/java/org/jboss/aerogear/connectivity/rest/registry/applications/iOSVariantEndpoint.java#L78
>>
>>     Perhaps it should mention the word "pushApplicationID"
>
>     Yeah, I think "Could not find requested pushApplicationID" would be
>     more helpful.
>
>
> alright :)
>
> See   AGPUSH-146
>
>
>
>
>>
>>
>>     On Tue, Jul 9, 2013 at 8:28 PM, Tommy McCarthy

>>     <tomccart@redhat.com <mailto:tomccart@redhat.com>> wrote:
>>
>>         *sigh*
>>         Yup, that was it. Looks like I've been staring at this too
>>         long. Didn't realize that we got multiple IDs back now. Makes
>>         sense though!
>>
>>         I wish it was a silly question, but I guess not :P
>>
>>         ----- Original Message -----
>>         From: "Sebastien Blanc" <scm.blanc@gmail.com

>>         <mailto:scm.blanc@gmail.com>>
>>         To: "AeroGear Developer Mailing List"
>>         <aerogear-dev@lists.jboss.org

>>         <mailto:aerogear-dev@lists.jboss.org>>
>>         Sent: Tuesday, July 9, 2013 2:23:35 PM
>>         Subject: Re: [aerogear-dev] Registering an Android Variant Fails
>>
>>         Might be a silly question but are you sure you are using the
>>         push App Id and not the "native" id ?
>>
>>
>>         On Tue, Jul 9, 2013 at 8:11 PM, Tommy McCarthy <

>>         tomccart@redhat.com <mailto:tomccart@redhat.com> > wrote:
>>
>>
>>         Hey everyone,
>>
>>         I've run into a slight issue when trying to register an
>>         Android variant. I keep getting a 404 response instead of the
>>         variant ID, secret, etc. I'm not sure if the configuration has
>>         changed since the latest readme in aerogear-unified-push-server.
>>
>>         On the third curl command to register the Android variant:
>>         curl -v -b cookies.txt -c cookies.txt
>>         -v -H "Accept: application/json" -H "Content-type:
>>         application/json"
>>         -X POST
>>         -d '{"googleKey" : "IDDASDASDSA"}'
>>
>>         http://localhost:8080/ag-push/rest/applications/{PUSH_ID}/android

>>         <http://localhost:8080/ag-push/rest/applications/%7BPUSH_ID%7D/android>

>>
>>         I get back a 404. I've tried this on my OpenShift instance and
>>         a local instance as well, with no avail. Every other command
>>         so far has worked (login, register app)
>>
>>         Also, I'm using the latest version of the unified push server
>>         from a clone today.
>>
>>         Any suggestions? I think I've covered all my bases so far!
>>         Tommy Mccarthy
>>         _______________________________________________
>>         aerogear-dev mailing list

>>         aerogear-dev@lists.jboss.org <mailto:aerogear-dev@lists.jboss.org>

>>         https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>         _______________________________________________
>>         aerogear-dev mailing list

>>         aerogear-dev@lists.jboss.org <mailto:aerogear-dev@lists.jboss.org>

>>         https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>         _______________________________________________
>>         aerogear-dev mailing list

>>         aerogear-dev@lists.jboss.org <mailto:aerogear-dev@lists.jboss.org>

>>         https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>>
>>     --
>>     Matthias Wessendorf
>>
>>     blog: http://matthiaswessendorf.wordpress.com/
>>     sessions: http://www.slideshare.net/mwessendorf
>>     twitter: http://twitter.com/mwessendorf
>>     _______________________________________________
>>     aerogear-dev mailing list

>>     aerogear-dev@lists.jboss.org <mailto:aerogear-dev@lists.jboss.org>

>>     https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>     _______________________________________________
>     aerogear-dev mailing list

>     aerogear-dev@lists.jboss.org <mailto:aerogear-dev@lists.jboss.org>

>     https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

--
abstractj

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev

--
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev