| Issue 767: | query json api calls should not require a user login | |
| 1 person starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
The following calls require a user to be logged in: /api/json/reviewrequests/all/ /api/json/reviewrequests/to/group/<group_name>/ /api/json/reviewrequests/to/user/<username>/ /api/json/reviewrequests/from/user/<username>/ /api/json/reviewrequests/repository/<repository_id>/changenum/<changenum>/ Why? You can get this information without a login using a web browser, why is there a login requirement to fetch the data using the API? Can these calls be modified to not require a login? Thanks. |
||||||||||||||||
,
Mar 24, 2009
Thought we had this filed somewhere else, but I can't find it. We just need to provide a new decorator similar to our @check_login_required.
Status: Confirmed
Labels: -Priority-Medium Priority-High Component-API Milestone-Release1.0 EasyFix |
|||||||||||||||||
,
Mar 25, 2009
Fixed in r1854.
Status: Fixed
|
|||||||||||||||||
| ► Sign in to add a comment | |||||||||||||||||