FM / docs

/home/techb158/ileadtechnology.com/SSM/vendor/rmccue/requests/docs/

/home/techb158/ileadtechnology.com/SSM/vendor/rmccue/requests/docs

Name	Size	Mode	Actions
authentication-custom.md	1287	0644	edit dl rm
authentication.md	925	0644	edit dl rm
goals.md	1106	0644	edit dl rm
hooks.md	2628	0644	edit dl rm
proxy.md	527	0644	edit dl rm
README.md	810	0644	edit dl rm
usage-advanced.md	2668	0644	edit dl rm
usage.md	3917	0644	edit dl rm
why-requests.md	7713	0644	edit dl rm

Edit: /home/techb158/ileadtechnology.com/SSM/vendor/rmccue/requests/docs/authentication-custom.md (1287B)

Custom Authentication
=====================
Custom authentication handlers are designed to be extremely simple to write.
In order to write a handler, you'll need to implement the `Requests_Auth`
interface.

An instance of this handler is then passed in by the user via the `auth`
option, just like for normal authentication.

Let's say we have a HTTP endpoint that checks for the `Hotdog` header and
authenticates you if said header is set to `Yummy`. (I don't know of any
services that do this; perhaps this is a market waiting to be tapped?)

```php
class MySoftware_Auth_Hotdog implements Requests_Auth {
	protected $password;

public function __construct($password) {
		$this->password = $password;
	}

public function register(Requests_Hooks &$hooks) {
		$hooks->register('requests.before_request', array(&$this, 'before_request'));
	}

public function before_request(&$url, &$headers, &$data, &$type, &$options) {
		$headers['Hotdog'] = $this->password;
	}
}
```

We then use this in our request calls:

```
$options = array(
	'auth' => new MySoftware_Auth_Hotdog('yummy')
);
$response = Requests::get('http://hotdogbin.org/admin', array(), $options);
```

(For more information on how to register and use hooks, see the [hooking
system documentation][hooks])

[hooks]: hooks.md

cmd: