Custom Query (2152 matches)
Results (2104 - 2106 of 2152)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#1174 | wontfix | API Representation Registry | pudo | pudo |
Description |
As CKAN grows, more and more optional representations of packages will become used. Besides RDF (which is the motivation for this ticket), support for DSPL, home-grown XML, or CSV listings is imaginable. To properly support this CKAN should have an extensible representation registry that can be extended when new output types become available (and without changing the API in the process). This needs to integrate in two places:
To support this we should have a registry with two registers:
This should be set up on load_environment so that IConfigurer plugins can feed into it. The registry should then first be added to _finish in the REST API (which needs to be refactored to be passed the {format} part of the URL if one is given. Based on the format part and HTTP headers, an appropriate representation can be generated by the registry and then be returned to the user. Forwarding of requests to the regular WUI controllers with Accept headers set or a format specified can be implemented in a separate effort. |
|||
#482 | wontfix | API Rate Limiting | thejimmyg | johnbywater |
#2942 | wontfix | API POST barfs on interesting Content-Type headers | dread | dread |
Description |
When POSTing to the API, if specified, the 'Content-Type' header must be blank or 'application/x-www-form-urlencoded'. Otherwise we get an error like: "Bad request - JSON Error: Could not extract request body data: Bad content type: \'; charset=utf-8\'"" The problem is that this is a very reasonable header to send. Indeed requests 0.14 sends this particular header. This affects all versions of CKAN. This is due to webob/requests.py:1248 being pretty basic. |