Custom Query (2152 matches)
Results (661 - 663 of 2152)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1312 | invalid | Particular characters in JSON cause exception creating package on API | dread | florian.marienfeld@… |
| Description |
From Florian: I am having trouble with the characters "=&;". if they occur e.g. in the title of a package, I get a 400-Bad-Request when I try to register a package by POSTing to ckan/rest/api/package However, when I PUT the same package as an edit to ckan/rest/api/package/existing_package, it works and the title shows correctly on the front end and API. Reproduced(pyenv-ckan)dread@dread-laptop:~/hgroot/ckan$ curl -i http://localhost:5000/api/rest/package -d '{"name": "test3", "title": "Test &"}' -H "Authorization:tester"
HTTP/1.0 400 Bad Request
Server: PasteWSGIServer/0.5 Python/2.6.5
Date: Tue, 06 Sep 2011 14:09:31 GMT
Pragma: no-cache
Cache-Control: no-cache
Content-Type: application/json;charset=utf-8
Content-Length: 87
"Bad request - JSON Error: Unterminated string starting at: line 1 column 27 (char 27)"
|
|||
| #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. |
|||
| #920 | fixed | empty tags are kind of confusing | thejimmyg | hellmann@… |
| Description |
http://ckan.net/tag/linguistsic doesn't have a single entry, but is still kept and displayed. It should be purged !!! |
|||
Note: See TracQuery
for help on using queries.
