Yannick Warnier 76a0eae5ea Add static resources and remove tests dir for beta release | %!s(int64=5) %!d(string=hai) anos | |
---|---|---|
.. | ||
bin | %!s(int64=5) %!d(string=hai) anos | |
docs | %!s(int64=5) %!d(string=hai) anos | |
examples | %!s(int64=5) %!d(string=hai) anos | |
library | %!s(int64=5) %!d(string=hai) anos | |
tests | %!s(int64=5) %!d(string=hai) anos | |
.coveralls.yml | %!s(int64=5) %!d(string=hai) anos | |
.gitignore | %!s(int64=5) %!d(string=hai) anos | |
.travis.yml | %!s(int64=5) %!d(string=hai) anos | |
CHANGELOG.md | %!s(int64=5) %!d(string=hai) anos | |
LICENSE | %!s(int64=5) %!d(string=hai) anos | |
README.md | %!s(int64=5) %!d(string=hai) anos | |
composer.json | %!s(int64=5) %!d(string=hai) anos | |
package.xml.tpl | %!s(int64=5) %!d(string=hai) anos |
Requests is a HTTP library written in PHP, for human beings. It is roughly based on the API from the excellent Requests Python library. Requests is ISC Licensed (similar to the new BSD license) and has no dependencies, except for PHP 5.2+.
Despite PHP's use as a language for the web, its tools for sending HTTP requests are severely lacking. cURL has an interesting API, to say the least, and you can't always rely on it being available. Sockets provide only low level access, and require you to build most of the HTTP response parsing yourself.
We all have better things to do. That's why Requests was born.
$headers = array('Accept' => 'application/json');
$options = array('auth' => array('user', 'pass'));
$request = Requests::get('https://api.github.com/gists', $headers, $options);
var_dump($request->status_code);
// int(200)
var_dump($request->headers['content-type']);
// string(31) "application/json; charset=utf-8"
var_dump($request->body);
// string(26891) "[...]"
Requests allows you to send HEAD, GET, POST, PUT, DELETE, and PATCH HTTP requests. You can add headers, form data, multipart files, and parameters with simple arrays, and access the response data in the same way. Requests uses cURL and fsockopen, depending on what your system has available, but abstracts all the nasty stuff out of your way, providing a consistent API.
If you're using Composer to manage dependencies, you can add Requests with it.
composer require rmccue/requests
or
{
"require": {
"rmccue/requests": ">=1.0"
}
}
To install the source code:
$ git clone git://github.com/rmccue/Requests.git
And include it in your scripts:
require_once '/path/to/Requests/library/Requests.php';
You'll probably also want to register an autoloader:
Requests::register_autoloader();
Alternatively, you can fetch a tarball or zipball:
$ curl -L https://github.com/rmccue/Requests/tarball/master | tar xzv
(or)
$ wget https://github.com/rmccue/Requests/tarball/master -O - | tar xzv
If you're using a class loader (e.g., Symfony Class Loader) for PSR-0-style class loading:
$loader->registerPrefix('Requests', 'path/to/vendor/Requests/library');
The best place to start is our prose-based documentation, which will guide you through using Requests.
After that, take a look at the documentation for
Requests::request()
, where all the parameters are fully
documented.
Requests is 100% documented with PHPDoc. If you find any problems with it, create a new issue!
Requests strives to have 100% code-coverage of the library with an extensive set of tests. We're not quite there yet, but we're getting close.
To run the test suite, first check that you have the PHP JSON extension enabled. Then simply:
$ cd tests
$ phpunit
If you'd like to run a single set of tests, specify just the name:
$ phpunit Transport/cURL
master
branch (or branch off of it)