25.1. Introduction

Zend_Http_Client provides an easy interface for preforming Hyper-Text Transfer Protocol (HTTP) requests. Zend_Http_Client supports most simple features expected from an HTTP client, as well as some more complex features such as HTTP authentication and file uploads. Successful requests (and most unsuccessful ones too) return a Zend_Http_Response object, which provides access to the response's headers and body (see Section 25.6, “Zend_Http_Response”).

25.1.1. Using Zend_Http_Client

The class constructor optionally accepts a URL as its first parameter (can be either a string or a Zend_Uri_Http object), and an array or Zend_Config object containing configuration options. Both can be left out, and set later using the setUri() and setConfig() methods.

Example 25.1. Instantiating a Zend_Http_Client Object

$client = new Zend_Http_Client('', array(
    'maxredirects' => 0,
    'timeout'      => 30));

// This is actually exactly the same:
$client = new Zend_Http_Client();
    'maxredirects' => 0,
    'timeout'      => 30));

// You can also use a Zend_Config object to set the client's configuration
$config = new Zend_Config_Ini('httpclient.ini, 'secure');

[Note] Note

Zend_Http_Client uses Zend_Uri_Http to validate URLs. This means that some special characters like the pipe symbol ('|') or the caret symbol ('^') will not be accepted in the URL by default. This can be modified by setting the 'allow_unwise' option of Zend_Uri to 'true'. See Section, “Allowing "Unwise" characters in URIs” for more information.

25.1.2. Configuration Parameters

The constructor and setConfig() method accept an associative array of configuration parameters, or a Zend_Config object. Setting these parameters is optional, as they all have default values.

Table 25.1. Zend_Http_Client configuration parameters

Parameter Description Expected Values Default Value
maxredirects Maximum number of redirections to follow (0 = none) integer 5
strict Whether perform validation on header names. When set to false, validation functions will be skipped. Usually this should not be changed boolean true
strictredirects Whether to strictly follow the RFC when redirecting (see Section 25.2.1, “HTTP Redirections”) boolean false
useragent User agent identifier string (sent in request headers) string 'Zend_Http_Client'
timeout Connection timeout (seconds) integer 10
httpversion HTTP protocol version (usually '1.1' or '1.0') string '1.1'
adapter Connection adapter class to use (see Section 25.3, “Zend_Http_Client - Connection Adapters”) mixed 'Zend_Http_Client_Adapter_Socket'
keepalive Whether to enable keep-alive connections with the server. Useful and might improve performance if several consecutive requests to the same server are performed. boolean false
storeresponse Whether to store last response for later retrieval with getLastResponse(). If set to false getLastResponse() will return null. boolean true

25.1.3. Performing Basic HTTP Requests

Performing simple HTTP requests is very easily done using the request() method, and rarely needs more than three lines of code:

Example 25.2. Performing a Simple GET Request

$client = new Zend_Http_Client('');
$response = $client->request();

The request() method takes one optional parameter - the request method. This can be either GET, POST, PUT, HEAD, DELETE, TRACE, OPTIONS or CONNECT as defined by the HTTP protocol [ ]. For convenience, these are all defined as class constants: Zend_Http_Client::GET, Zend_Http_Client::POST and so on.

If no method is specified, the method set by the last setMethod() call is used. If setMethod() was never called, the default request method is GET (see the above example).

Example 25.3. Using Request Methods Other Than GET

// Preforming a POST request
$response = $client->request('POST');

// Yet another way of preforming a POST request
$response = $client->request();

25.1.4. Adding GET and POST parameters

Adding GET parameters to an HTTP request is quite simple, and can be done either by specifying them as part of the URL, or by using the setParameterGet() method. This method takes the GET parameter's name as its first parameter, and the GET parameter's value as its second parameter. For convenience, the setParameterGet() method can also accept a single associative array of name => value GET variables - which may be more comfortable when several GET parameters need to be set.

Example 25.4. Setting GET Parameters

// Setting a get parameter using the setParameterGet method
$client->setParameterGet('knight', 'lancelot');

// This is equivalent to setting such URL:

// Adding several parameters with one call
    'first_name'  => 'Bender',
    'middle_name' => 'Bending'
    'made_in'     => 'Mexico',

While GET parameters can be sent with every request method, POST parameters are only sent in the body of POST requests. Adding POST parameters to a request is very similar to adding GET parameters, and can be done with the setParameterPost() method, which is similar to the setParameterGet() method in structure.

Example 25.5. Setting POST Parameters

// Setting a POST parameter
$client->setParameterPost('language', 'fr');

// Setting several POST parameters, one of them with several values
    'language'  => 'es',
    'country'   => 'ar',
    'selection' => array(45, 32, 80)

Note that when sending POST requests, you can set both GET and POST parameters. On the other hand, while setting POST parameters for a non-POST request will not trigger and error, it is useless. Unless the request is a POST request, POST parameters are simply ignored.

25.1.5. Accessing Last Request and Response

Zend_Http_Client provides methods of accessing the last request sent and last response received by the client object. Zend_Http_Client->getLastRequest() takes no parameters and returns the last HTTP request sent by the client as a string. Similarly, Zend_Http_Client->getLastResponse() returns the last HTTP response received by the client as a Zend_Http_Response object.

Table of Contents

25.1. Introduction
25.1.1. Using Zend_Http_Client
25.1.2. Configuration Parameters
25.1.3. Performing Basic HTTP Requests
25.1.4. Adding GET and POST parameters
25.1.5. Accessing Last Request and Response
25.2. Zend_Http_Client - Advanced Usage
25.2.1. HTTP Redirections
25.2.2. Adding Cookies and Using Cookie Persistence
25.2.3. Setting Custom Request Headers
25.2.4. File Uploads
25.2.5. Sending Raw POST Data
25.2.6. HTTP Authentication
25.2.7. Sending Multiple Requests With the Same Client
25.3. Zend_Http_Client - Connection Adapters
25.3.1. Overview
25.3.2. The Socket Adapter Customizing and accessing the Socket adapter stream context
25.3.3. The Proxy Adapter
25.3.4. The cURL Adapter
25.3.5. The Test Adapter
25.3.6. Creating your own connection adapters
25.4. Migrating from previous versions
25.4.1. Migrating from 1.8 or older to 1.9 or newer Changes to internal uploaded file information storage Deprecation of Zend_Http_Client::_getParametersRecursive()
25.5. Zend_Http_Cookie and Zend_Http_CookieJar
25.5.1. Introduction
25.5.2. Instantiating Zend_Http_Cookie Objects
25.5.3. Zend_Http_Cookie getter methods
25.5.4. Zend_Http_Cookie: Matching against a scenario
25.5.5. The Zend_Http_CookieJar Class: Instantiation
25.5.6. Adding Cookies to a Zend_Http_CookieJar object
25.5.7. Retrieving Cookies From a Zend_Http_CookieJar object
25.6. Zend_Http_Response
25.6.1. Introduction
25.6.2. Boolean Tester Methods
25.6.3. Accessor Methods
25.6.4. Static HTTP Response Parsers

Previous topic


Next topic



© 2006-2018 by Zend, a Rogue Wave Company. Made with by awesome contributors.

This website is built using zend-expressive and it runs on PHP 7.