Guzzle, PHP HTTP client and webservice framework
Guzzle is a PHP HTTP client and framework for building RESTful web service clients.
- Extremely powerful API provides all the power of cURL with a simple interface.
- Truly take advantage of HTTP/1.1 with persistent connections, connection pooling, and parallel requests.
- Service description DSL allows you build awesome web service clients faster.
- Symfony2 event-based plugin system allows you to completely modify the behavior of a request.
- Includes a custom node.js webserver to test your clients.
- Unit-tested with PHPUnit with 100% code coverage.
Getting started
- Download the phar and include it in your project (minimal phar)
- Docs: www.guzzlephp.org
- Forum: https://groups.google.com/forum/?hl=en#!forum/guzzle
- IRC: #guzzlephp channel on irc.freenode.net
Installing via Composer
The recommended way to install Guzzle is through composer. You will need to add Guzzle as a dependency in your project's composer.json
file:
{
"require": {
"guzzle/guzzle": "*"
}
}
You can find out more on how to install Composer, configure autloading, and other best-practices for defining dependencies at http://getcomposer.org/doc/00-intro.md
Features
- Supports GET, HEAD, POST, DELETE, PUT, PATCH, OPTIONS, and any custom verbs
- Allows full access to request and response headers
- Persistent connections are implicitly managed by Guzzle, resulting in huge performance benefits
- Send requests in parallel
- Cookie sessions can be maintained between requests using the CookiePlugin
- Allows custom entity bodies, including sending data from a PHP stream and downloading data to a PHP stream
- Responses can be cached and served from cache using the caching forward proxy plugin
- Failed requests can be retried using truncated exponential backoff with custom retry policies
- Entity bodies can be validated automatically using Content-MD5 headers and the MD5 hash validator plugin
- All data sent over the wire can be logged using the LogPlugin
- Subject/Observer signal slot system for unobtrusively modifying request behavior
- Supports all of the features of libcurl including authentication, compression, redirects, SSL, proxies, etc
- Web service client framework for building future-proof interfaces to web services
- Includes a service description DSL for quickly building webservice clients
- Full support for URI templates
- Advanced batching functionality to efficiently send requests or commands in parallel with customizable batch sizes and transfer strategies
HTTP basics
<?php
use Guzzle\Http\Client;
$client = new Client('http://www.example.com/api/v1/key/{{key}}', array(
'key' => '***'
));
// Issue a path using a relative URL to the client's base URL
// Sends to http://www.example.com/api/v1/key/***/users
$request = $client->get('users');
$response = $request->send();
// Relative URL that overwrites the path of the base URL
$request = $client->get('/test/123.php?a=b');
// Issue a head request on the base URL
$response = $client->head()->send();
// Delete user 123
$response = $client->delete('users/123')->send();
// Send a PUT request with custom headers
$response = $client->put('upload/text', array(
'X-Header' => 'My Header'
), 'body of the request')->send();
// Send a PUT request using the contents of a PHP stream as the body
// Send using an absolute URL (overrides the base URL)
$response = $client->put('http://www.example.com/upload', array(
'X-Header' => 'My Header'
), fopen('http://www.test.com/', 'r'));
// Create a POST request with a file upload (notice the @ symbol):
$request = $client->post('http://localhost:8983/solr/update', null, array (
'custom_field' => 'my value',
'file' => '@/path/to/documents.xml'
));
// Create a POST request and add the POST files manually
$request = $client->post('http://localhost:8983/solr/update')
->addPostFiles(array(
'file' => '/path/to/documents.xml'
));
// Responses are objects
echo $response->getStatusCode() . ' ' . $response->getReasonPhrase() . "\n";
// Requests and responses can be cast to a string to show the raw HTTP message
echo $request . "\n\n" . $response;
// Create a request based on an HTTP message
$request = RequestFactory::fromMessage(
"PUT / HTTP/1.1\r\n" .
"Host: test.com:8081\r\n" .
"Content-Type: text/plain"
"Transfer-Encoding: chunked\r\n" .
"\r\n" .
"this is the body"
);
Send requests in parallel
<?php
try {
$client = new Guzzle\Http\Client('http://www.myapi.com/api/v1');
$responses = $client->send(array(
$client->get('users'),
$client->head('messages/123'),
$client->delete('orders/123')
));
} catch (Guzzle\Common\Exception\ExceptionCollection $e) {
echo "The following requests encountered an exception: \n";
foreach ($e as $exception) {
echo $exception->getRequest() . "\n" . $exception->getMessage() . "\n";
}
}
URI templates
Guzzle supports the entire URI templates RFC.
<?php
$client = new Guzzle\Http\Client('http://www.myapi.com/api/v1', array(
'path' => '/path/to',
'a' => 'hi',
'data' => array(
'foo' => 'bar',
'mesa' => 'jarjar'
)
));
$request = $client->get('http://www.test.com{+path}{?a,data*}');
The generated request URL would become: http://www.test.com/path/to?a=hi&foo=bar&mesa=jarajar
You can specify URI templates and an array of additional template variables to use when creating requests:
<?php
$client = new Guzzle\Http\Client('http://test.com', array(
'a' => 'hi'
));
$request = $client->get(array('/{?a,b}', array(
'b' => 'there'
));
The resulting URL would become http://test.com?a=hi&b=there
Unit testing
You will first need to clone the GitHub repository:
git clone git@github.com:guzzle/guzzle.git
cd guzzle
Next you will need to make sure PHPUnit is configured, Composer is installed, and you have installed Guzzle's
testing dependencies. This can be achieved using the test-init
Phing task. After running this task, run phpunit
.
phing test-init
phpunit
If you do not have Phing installed, you will need to perform the installation steps manually:
curl -s http://getcomposer.org/installer | php
php composer.phar install --dev
cp phpunit.xml.dist phpunit.xml
phpunit