Zend_Http_Client is based on a connection adapter design. The connection adapter is the object in charge of performing the actual connection to the server, as well as writing requests and reading responses. This connection adapter can be replaced, and you can create and extend the default connection adapters to suite your special needs, without the need to extend or replace the entire HTTP client class, and with the same interface.
Currently, the Zend_Http_Client class provides three built-in connection adapters:
The Zend_Http_Client object's adapter connection adapter is set
using the 'adapter' configuration option. When instantiating the
client object, you can set the 'adapter' configuration option to
a string containing the adapter's name (eg. 'Zend_Http_Client_Adapter_Socket')
or to a variable holding an adapter object (eg.
new Zend_Http_Client_Adapter_Test). You can also set the
adapter later, using the Zend_Http_Client->setConfig() method.
The default connection adapter is the Zend_Http_Client_Adapter_Socket adapter - this adapter will be used unless you explicitly set the connection adapter. The Socket adapter is based on PHP's built-in fsockopen() function, and does not require any special extensions or compilation flags.
The Socket adapter allows several extra configuration options that
can be set using
passed to the client constructor.
|Parameter||Description||Expected Type||Default Value|
|persistent||Whether to use persistent TCP connections||boolean||false|
|ssltransport||SSL transport layer (eg. 'sslv2', 'tls')||string||ssl|
|sslcert||Path to a PEM encoded SSL certificate||string||null|
|sslpassphrase||Passphrase for the SSL certificate file||string||null|
Note: Persistent TCP Connections
Using persistent TCP connections can potentially speed up HTTP requests - but in most use cases, will have little positive effect and might overload the HTTP server you are connecting to.
It is recommended to use persistent TCP connections only if you connect to the same server very frequently, and are sure that the server is capable of handling a large number of concurrent connections. In any case you are encouraged to benchmark the effect of persistent connections on both the client speed and server load before using this option.
Additionally, when using persistent connections it is recommended to enable Keep-Alive HTTP requests as described in Configuration Parameters - otherwise persistent connections might have little or no effect.
Note: HTTPS SSL Stream Parameters
sslpassphraseare only relevant when connecting using HTTPS.
While the default SSL settings should work for most applications, you might need to change them if the server you are connecting to requires special client setup. If so, you should read the sections about SSL transport layers and options » here.
Example #1 Changing the HTTPS transport layer
'Zend_Http_Client_Adapter_Socket', 'ssltransport' => 'tls' ); // Instantiate a client object $client = Zend_Http_Client('https://www.example.com', $config); // The following request will be sent over a TLS secure connection. $response = $client->request();
The result of the example above will be similar to opening a TCP connection using the following PHP command:
The Zend_Http_Client_Adapter_Proxy adapter is similar to the default Socket adapter - only the connection is made through an HTTP proxy server instead of a direct connection to the target server. This allows usage of Zend_Http_Client behind proxy servers - which is sometimes needed for security or performance reasons.
Using the Proxy adapter requires several additional configuration parameters to be set, in addition to the default 'adapter' option:
|Parameter||Description||Expected Type||Example Value|
|proxy_host||Proxy server address||string||'proxy.myhost.com' or '10.1.2.3'|
|proxy_port||Proxy server TCP port||integer||8080 (default) or 81|
|proxy_user||Proxy user name, if required||string||'shahar' or '' for none (default)|
|proxy_pass||Proxy password, if required||string||'secret' or '' for none (default)|
|proxy_auth||Proxy HTTP authentication type||string||Zend_Http_Client::AUTH_BASIC (default)|
proxy_host should always be set - if it is not set, the client will fall back to a direct connection using Zend_Http_Client_Adapter_Socket. proxy_port defaults to '8080' - if your proxy listens on a different port you must set this one as well.
proxy_user and proxy_pass are only required if your proxy server requires you to authenticate. Providing these will add a 'Proxy-Authentication' header to the request. If your proxy does not require authentication, you can leave these two options out.
proxy_auth sets the proxy authentication type, if your proxy server requires authentication. Possibly values are similar to the ones accepted by the Zend_Http_Client::setAuth() method. Currently, only basic authentication (Zend_Http_Client::AUTH_BASIC) is supported.
Example #2 Using Zend_Http_Client behind a proxy server
'Zend_Http_Client_Adapter_Proxy', 'proxy_host' => 'proxy.int.zend.com', 'proxy_port' => 8000, 'proxy_user' => 'shahar.e', 'proxy_pass' => 'bananashaped' ); // Instantiate a client object $client = Zend_Http_Client('http://www.example.com', $config); // Continue working...
As mentioned, if proxy_host is not set or is set to a blank string, the connection will fall back to a regular direct connection. This allows you to easily write your application in a way that allows a proxy to be used optionally, according to a configuration parameter.
Sometimes, it is very hard to test code that relies on HTTP connections. For example, testing an application that pulls an RSS feed from a remote server will require a network connection, which is not always available.
For this reason, the Zend_Http_Client_Adapter_Test adapter is provided. You can write your application to use Zend_Http_Client, and just for testing purposes, for example in your unit testing suite, you can replace the default adapter with a Test adapter (a mock object), allowing you to run tests without actually performing server connections.
The Zend_Http_Client_Adapter_Test adapter provides an additional method, setResponse() method. This method takes one parameter, which represents an HTTP response as either text or a Zend_Http_Response object. Once set, your Test adapter will always return this response, without even performing an actual HTTP request.
Example #3 Testing Against a Single HTTP Response Stub
$adapter )); // Set the expected response $adapter->setResponse( "HTTP/1.1 200 OK" . "\r\n" . "Content-type: text/xml" . "\r\n" . "\r\n" . '' . '
' . ''); $response = $client->request('GET'); // .. continue parsing $response.. ' . ' Premature Optimization' . // and so on... '
The above example shows how you can preset your HTTP client to return the response you need. Then, you can continue testing your own code, without being dependent on a network connection, the server's response, etc. In this case, the test would continue to check how the application parses the XML in the response body.
Sometimes, a single method call to an object can result in that object performing multiple HTTP transactions. In this case, it's not possible to use setResponse() alone because there's no opportunity to set the next response(s) your program might need before returning to the caller.
Example #4 Testing Against Multiple HTTP Response Stubs
$adapter )); // Set the first expected response $adapter->setResponse( "HTTP/1.1 302 Found" . "\r\n" . "Location: /" . "\r\n" . "Content-Type: text/html" . "\r\n" . "\r\n" . '' . '
Moved' . '
This page has moved.' . ''); // Set the next successive response $adapter->addResponse( "HTTP/1.1 200 OK" . "\r\n" . "Content-Type: text/html" . "\r\n" . "\r\n" . '' . '
My Pet Store Home Page' . '
...' . ''); // inject the http client object ($client) into your object // being tested and then test your object's behavior below
The setResponse() method clears any responses in the Zend_Http_Client_Adapter_Test's buffer and sets the first response that will be returned. The addResponse() method will add successive responses.
The responses will be replayed in the order that they were added. If more requests are made than the number of responses stored, the responses will cycle again in order.
In the example above, the adapter is configured to test your object's behavior when it encounters a 302 redirect. Depending on your application, following a redirect may or may not be desired behavior. In our example, we expect that the redirect will be followed and we configure the test adapter to help us test this. The initial 302 response is set up with the setResponse() method and the 200 response to be returned next is added with the addResponse() method. After configuring the test adapter, inject the HTTP client containing the adapter into your object under test and test its behavior.
You can create your own connection adapters and use them. You could, for example, create a connection adapter that uses persistent sockets, or a connection adapter with caching abilities, and use them as needed in your application.
In order to do so, you must create your own adapter class that implements the Zend_Http_Client_Adapter_Interface interface. The following example shows the skeleton of a user-implemented adapter class. All the public functions defined in this example must be defined in your adapter as well:
Example #5 Creating your own connection adapter