Custom Query (2152 matches)
Results (10 - 12 of 2152)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #377 | wontfix | API Should return JSON in all cases | glen@… | |
| Description |
When the API returns any response it should always retunr JSON. For example a 404 response should return something like {'status': 404, 'message': 'package somename not found'}
When errors are encountered when creating a package: {'status': nnn, 'message': 'Validation Errors', 'errors':['description':'name cannot be
blank', 'description':'license code must be an integer']}
Not authorised: {'status': 503, 'message': 'You are not authorised to create this package.'}
The reason being that screeds of html coming back in the response just makes it harder to debug and understand. Having the proper error codes/messages means that you can see why your package was not created. |
|||
| #381 | invalid | Test defect | johnbywater | |
| Description |
please ignore |
|||
| #395 | duplicate | Set up profiling to analyze performance issues | pudo | |
| Description |
At the moment, some pages within CKAN tend to load slowly. We should create a profiling setup in which we can measure response times for complete requests and individual methods calls. This could be used to identify bottlenecks and find an appropriate caching or tuning strategy to improve CKAN performance. NB: We should also agree on a maximum request latency. TODO: Read up on all those QoS tickets to avoid overlapping efforts. |
|||
