Re: [Dhis2-devs] API not showing 401 Unauthorized error

2018-04-20 Thread Morten Olav Hansen
It should be district, not distric... but also people keep changing our internal passwords (our database resets every 24 hour) -- Morten Olav Hansen Senior Engineer, DHIS 2 University of Oslo http://www.dhis2.org On Fri, Apr 20, 2018 at 12:09 PM, Rangarirai Matavire wrote: > By the way, its no

Re: [Dhis2-devs] API not showing 401 Unauthorized error

2018-04-20 Thread Rangarirai Matavire
Hi Morten, The password is set wrong deliberately so as to get a 401 or other response. The problem is when you set the wrong password or username you get endless redirects from the API. Regards, On Fri, Apr 20, 2018 at 1:24 PM, Morten Olav Hansen wrote: > It should be district, not distric..

Re: [Dhis2-devs] WEB API Error in DHIS2.30

2018-04-20 Thread mahdi asgari
Thanks for your reply On Fri, Apr 20, 2018 at 11:16 AM, Edouard Lavaud wrote: > Hi there, > > Starting from 2.29 the trackedEntity field has been renamed to > trackedEntityType. > > Best, > > Edouard > > 2018-04-20 4:44 GMT+02:00 Ocaya Stephen : > >> Please note that 2.30 has not yet been offic

Re: [Dhis2-devs] API not showing 401 Unauthorized error

2018-04-20 Thread Jason Pickering
Just to try and make it a bit more clear Morten, I think this is the issue Rangarai is asking about is below: In 2.29 and 2.28, an unauthorized username/password returns a 302. curl -I -u admin:distric -H 'Accept: application/json' https://play.dhis2.org/2.29/api/me HTTP/1.1 302 Server: nginx/1.