This package is abandoned and no longer maintained. The author suggests using the egeloen/http-adapter package instead.

Provides adapters for common HTTP Client libraries

dev-develop 2014-12-08 22:01 UTC

This package is not auto-updated.

Last update: 2022-02-01 12:41:48 UTC


Latest Version Software License Build Status Code Coverage Quality Score HHVM Status Total Downloads

Provides adapters for common HTTP Client libraries.

Why an other HTTP library again?

The proposed HTTP Message PSR is going to be great....but that won't let anyone create HTTP Client agnostic packages. For example you cannot typehint for a ClientInterface. You can only operate on the same messages. The PSR Meta also mentions adapter packages as a valid approach. There are many cool adapter packages out there, but all of them implement a simple logic based on the author's need. You can consider this package as a simple Adapter providing you full control over the common fetures of the implemented HTTP Client libraries. However, it must be noted that the specific features are out of scope. For example: if you need to use Guzzle specific feature, depend on it instead.

This package also provides a simple implementation of the latest PSR interfaces.


Via Composer

$ composer require indigophp/http-adapter


Simple usage

You are free to directly use any adapters in your application.

use Indigo\Http\Adapter;

class MyAdapterAware
     * @var Adapter
    private $adapter;

    public function __construct(Adapter $adapter)
        $this->adapter = $adapter;

    public function get()
        $request = new Request;

        return $this->adapter->send($request);

You can also use the client class for the most common client usage. (Guzzle is only used as an example)

use GuzzleHttp\Client as GuzzleClient;
use Indigo\Http\Adapter\Guzzle4;
use Indigo\Http\Client;

$adapter = new Guzzle4(new GuzzleClient);
$client = new Client($adapter);


Advanced usage

For testing you can use the Mock adapter.

use Indigo\Http\Adapter\Mock;
use Psr\Http\Message\RequestInterface as Request;
use Psr\Http\Message\ResponseInterface as Response;

// ... your testing logic

// you can directly pass the Response object to the constructor
$adapter = new Mock(function(Request $request) {
    return new Response;

// Optionally
$adapter->setResponse(new Response);

// ... your testing logic

You can decorate your adapters with various decorators.

Event decorator

Event decorator emitts two events:

  • Before (request)
  • Complete (response)

Both events receive the Adapter and the Request. The Complete event contains the Response as well.

use Indigo\Http\Adapter\Event;
use Indigo\Http\Event;

$adapter = new Event($decoratedAdapter);

// Optionally
// $adapter->setEmitter($emitter);

$adapter->addListener('before', function(Event\Before $event) {
    $adapter = $event->getAdapter();
    $request = $event->getRequest();

    // ... do something with the adapter and the request

$adapter->addListener('complete', function(Event\Complete $event) {
    $adapter = $event->getAdapter();
    $request = $event->getRequest();
    $response = $event->getResponse();

    // ... do something with the adapter, request and the response

You can also use Subscribers with the Event adapter.

use Indigo\Http\Adapter\Event;
use Indigo\Http\Subscriber\Auth;

$adapter = new Event($decoratedAdapter);

// This will always attach authentication data to your requests
$adapter->addSubscriber(new Auth('username', 'password', Auth::BASIC));

Currently league/event is used as event backend.

Cache decorator

You can use a local cache for returned Responses. Based on cached items you can send Requests to the server with If-Modified-Since and If-None-Match (ETag header required in response) headers. If the server return with 304 status then the cached item is returned, otherwise it gets cached for future.

use Indigo\Http\Adapter\Cache;

$adapter = new Cache($decoratedAdapter);

// Optionally
// $adapter->setPool($pool);

// Status: 200 OK
$response = $adapter->send($request);

// Status: 304 Not Modified
// Returned from cache
$response = $adapter->send($request);

Currently Stash is used as cache backend.


There are two main type of exceptions:

  • AdapterException: Thrown when some sort of adapter problem occurs.
  • RequestException: Thrown if the response itself is an error response (4xx, 5xx) or the request cannot be completed (no response returned).


$ phpspec run


Please see CONTRIBUTING for details.


Inspired by

  • Guzzle
  • fXmlRpc


The MIT License (MIT). Please see License File for more information.