[ckan-discuss] Can't PUT/POST to CKAN API anymore

Rufus Pollock rufus.pollock at okfn.org
Sat Sep 25 14:44:12 BST 2010

Hi Anja,

To follow up John's comments:

1. We've investigated and can reproduce the 403 on ckan.net. However
does not turn on our test instance running exactly the same code.

2. Having had similar issue in the pass we suspect this is related to
apache (or the cache) not passing the authorization header through

3. Recently we introduced the ability to set the api key in a
dedicated header X-CKAN-API-KEY (with this header getting checked
first -- this allows you to use both 'normal' authorization and the
api key at the same time).

Using this alternative header we were able to post successfully. This
indicates this is indeed an issue with apache or the cache.

4. We're still resolving where the issue lies in the apache/the cache
but for the time being an immediate fix for you is to switch your code
to set the X-CKAN-API-KEY header with your api key.

Please let us know if this resolves things at your end and we'll
continue to dig into why the authorization header is not getting
passed along correctly.


On 25 September 2010 10:03, Anja Jentzsch <anja at anjeve.de> wrote:
> Hi all,
> I have been updating a lot of the CKAN packages these days. Sometimes I used the API to do so. But since several days the API won't accept my API key anymore. I get a 403 ("403: Not Authorized") whenever I try using PUT or POST. I am using the PHP API client.
> Does anybody know what's going wrong or if any of the parameters changed recently?
> Thanks & Cheers,
> Anja
> _______________________________________________
> ckan-discuss mailing list
> ckan-discuss at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-discuss

Open Knowledge Foundation
Promoting Open Knowledge in a Digital Age
http://www.okfn.org/ - http://blog.okfn.org/

More information about the ckan-discuss mailing list