With new version of DroneLogBook service there new responses for authorization checks:
In case of wrong email:
{"status":1,"description":"Email not exist."}
In case of wrong password:
{"status":2,"description":"Bad password."}
In case of successfull authorization:
{"status":6,"description":""}
(but http code is still 401)
With new version of DroneLogBook service there new responses for authorization checks: In case of wrong email: {"status":1,"description":"Email not exist."}
In case of wrong password: {"status":2,"description":"Bad password."}
In case of successfull authorization: {"status":6,"description":""} (but http code is still 401)