REST API library CodeIgniter Ajax PUT throw 403 Forbidden

Question

I left the whole library fully working, just trying to generate api keys and throwing a 403 ban when executed via ajax.

({"status":false,"error":"Invalid API Key."})

I traced it to the _remap function in REST_Controller .. almost as if I had called the URL incorrectly?

workflow: user visits site1.com -> registers for account -> generates api key for their domain -> key recorded in db -> key displayed

The following form will be on site1.com after registration for the account that they click "generate key."

ajax call:

 /** * Generate an API Key for Us to use */ $("#submitGetApiKey").click(function(){ $.ajax({ url: "http://dev.site1.com/api/key", crossDomain: true, type: "PUT", dataType: "jsonp", error: function(XMLHttpRequest, textStatus, errorThrown){ alert(errorThrown); }, success: function(data){ for (var i = keys.length - 1; i >= 0; i--) { console.log(keys[i]); }; } }); }); 

REST-SERVER on GitHub: https://github.com/philsturgeon/codeigniter-restserver

look specifically at key.php under application/controllers/api/key.php

A fragment of the key.php file that should relate to this process:

 /** * Key Create * * Insert a key into the database. * * @access public * @return void */ public function index_put() { // Build a new key $key = self::_generate_key(); // If no key level provided, give them a rubbish one $level = $this->put('level') ? $this->put('level') : 1; $ignore_limits = $this->put('ignore_limits') ? $this->put('ignore_limits') : 1; // Insert the new key if (self::_insert_key($key, array('level' => $level, 'ignore_limits' => $ignore_limits))) { $this->response(array('status' => 1, 'key' => $key), 201); // 201 = Created } else { $this->response(array('status' => 0, 'error' => 'Could not save the key.'), 500); // 500 = Internal Server Error } } 

Response / Request Header

 Request URL:http://dev.mapitusa.com/api/key Request Method:PUT Status Code:403 Forbidden Request Headersview source Accept:application/json, text/javascript, */*; q=0.01 Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 Accept-Encoding:gzip,deflate,sdch Accept-Language:en-US,en;q=0.8 Connection:keep-alive Content-Length:0 Cookie:ci_session=a%3A4%3A%7Bs%3A10%3A%22session_id%22%3Bs%3A32%3A%22e165df34aa4fda5936e940658030f83d%22%3Bs%3A10%3A%22ip_address%22%3Bs%3A9%3A%22127.0.0.1%22%3Bs%3A10%3A%22user_agent%22%3Bs%3A118%3A%22Mozilla%2F5.0+%28Macintosh%3B+Intel+Mac+OS+X+10_7_3%29+AppleWebKit%2F535.19+%28KHTML%2C+like+Gecko%29+Chrome%2F18.0.1025.3+Safari%2F535.19%22%3Bs%3A13%3A%22last_activity%22%3Bi%3A1328291821%3B%7Dac0f163b112dbd3769e67f4bb7122db2 Host:dev.mapitusa.com Origin:http://dev.mapitusa.com Referer:http://dev.mapitusa.com/api_test.html User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_3) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.3 Safari/535.19 Response Headersview source Cache-Control:max-age=0, public Connection:Keep-Alive Content-Encoding:gzip Content-Length:69 Content-Type:application/json Date:Fri, 03 Feb 2012 18:03:54 GMT Expires:Fri, 03 Feb 2012 18:03:54 GMT Keep-Alive:timeout=5, max=98 Server:Apache Set-Cookie:ci_session=a%3A4%3A%7Bs%3A10%3A%22session_id%22%3Bs%3A32%3A%22f2f466f7b97b89f2a9b557d2d9a0dbcc%22%3Bs%3A10%3A%22ip_address%22%3Bs%3A9%3A%22127.0.0.1%22%3Bs%3A10%3A%22user_agent%22%3Bs%3A118%3A%22Mozilla%2F5.0+%28Macintosh%3B+Intel+Mac+OS+X+10_7_3%29+AppleWebKit%2F535.19+%28KHTML%2C+like+Gecko%29+Chrome%2F18.0.1025.3+Safari%2F535.19%22%3Bs%3A13%3A%22last_activity%22%3Bi%3A1328292234%3B%7D6821b96c7e58b55f1767eb265ffdb79e; expires=Fri, 03-Feb-2012 20:03:54 GMT; path=/ Status:403 Vary:Accept-Encoding,User-Agent X-Powered-By:PHP/5.3.6 X-UA-Compatible:IE=Edge,chrome=1 

Answer 1

As a result, it turned out that the 403 ban was caused by the fact that I did not provide an api key for generating keys.

Whatever was written in Phil's documentation, an existing api key is required before creating keys.

I just created a dummy key in a table in db and indicated that when calling / key / index X-API-KEY = boguskey

Answer 2

I solved the problem of generating the api key. I am using Phil Sturgeon REST API Server. Call the keyboard controller using an ajax call as such:

 $("#submitGetApiKey").click(function(){ $.ajax({ url: "http://sitename.com/api/key/index?X-API-KEY=your_key_here", crossDomain: true, /* remove this if using the same domain*/ type: "PUT", dataType: "jsonp", error: function(XMLHttpRequest, textStatus, errorThrown){ alert(errorThrown); }, success: function(data){ for (var i = keys.length - 1; i >= 0; i--) { console.log(keys[i]); }; } }); }); 

Internal keyboard controller: Find the function _generate_key () and set for reference $ this-> load-> ('security') ;. The security assistant must be loaded for do_hash to work, otherwise you will get 500 internal server errors.

 public function index_put() { // Build a new key $key = self::_generate_key(); // If no key level provided, give them a rubbish one $level = $this->put('level') ? $this->put('level') : 1; $ignore_limits = $this->put('ignore_limits') ? $this->put('ignore_limits') : 1; // Insert the new key if (self::_insert_key($key, array('level' => $level, 'ignore_limits' => $ignore_limits))) { $this->response(array('status' => 1, 'key' => $key), 201); // 201 = Created } else { $this->response(array('status' => 0, 'error' => 'Could not save the key.'), 500); // 500 = Internal Server Error } } 

In addition, you can call http://sitename.com/api/keyindex?X-API-KEY=your_key_here in the address bar of the browser, making a small change in your key controller, you can replace the name of the index_put function with index_get.

thanks

Answer 3

If you call this from another domain, you may run into some XSS issues. You may need to run it from your own server and call a function from your own domain, or perhaps use the JSONP capabilities.

UPDATE: Can you see the transaction in Firebug using the NET tab? Do you get JSON Back? Sometimes you need to add callback =? to url request: http://dev.site1.com/api/key?callback= ?

Update2: You can bring the page in the browser: (http://dev.mapitusa.com/api/key) If you get the same error, try to give 777 (full read / write access) to the site.

Answer 4

This seems like a problem with the browser. Perhaps the incorrect implementation of PUT in the XMLHttpRequest stack.

I would try quickly converting it to POST to make sure it works. It might be better to leave it as POST anyway just for compatibility purposes.