Wprowadzenie do Zend Framework

     Nauka Zend Framework


     Przewodnik po Zend Framework

  • Zend_Gdata
  • Zend_Http
  • Zend_InfoCard
  • Zend_Json
  • Zend_Layout
  • Zend_Ldap
  • Zend_Loader
  • Zend_Locale
  • Zend_Log
  • Zend_Mail
  • Zend_Markup
  • Zend_Measure
  • Zend_Memory
  • Zend_Mime
  • Zend_Navigation
  • Zend_Oauth
  • Zend_OpenId
  • Zend_Paginator
  • Zend_Pdf
  • Zend_ProgressBar
  • Zend_Queue
  • Zend_Reflection
  • Zend_Registry
  • Zend_Rest

  • Zend_Search_Lucene
  • Zend_Serializer
  • Zend_Server
  • Zend_Service
  • Zend_Session
  • Zend_Soap
  • Zend_Tag
  • Zend_Test
  • Zend_Text
  • Zend_TimeSync
  • Zend_Tool
  • Zend_Tool_Framework
  • Zend_Tool_Project
  • Zend_Translate
  • Zend_Uri
  • Zend_Validate
  • Zend_Version
  • Zend_View
  • Zend_Wildfire
  • Zend_XmlRpc
  • ZendX_Console_Process_Unix
  • ZendX_JQuery
  • Translation 21.3% Update 2011-11-16 - Revision 24356 - Version ZF 1.11.x

    Rozdział 35. Zend_Http

    Spis treści

    35.1. Introduction
    35.1.1. Using Zend_Http_Client
    35.1.2. Configuration Parameters
    35.1.3. Performing Basic HTTP Requests
    35.1.4. Adding GET and POST parameters
    35.1.5. Accessing Last Request and Response
    35.2. Zend_Http_Client - Advanced Usage
    35.2.1. HTTP Redirections
    35.2.2. Adding Cookies and Using Cookie Persistence
    35.2.3. Setting Custom Request Headers
    35.2.4. File Uploads
    35.2.5. Sending Raw POST Data
    35.2.6. HTTP Authentication
    35.2.7. Sending Multiple Requests With the Same Client
    35.2.8. Data Streaming
    35.3. Zend_Http_Client - Connection Adapters
    35.3.1. Overview
    35.3.2. The Socket Adapter Customizing and accessing the Socket adapter stream context
    35.3.3. The Proxy Adapter
    35.3.4. The cURL Adapter
    35.3.5. The Test Adapter
    35.3.6. Creating your own connection adapters
    35.4. Zend_Http_Cookie and Zend_Http_CookieJar
    35.4.1. Introduction
    35.4.2. Instantiating Zend_Http_Cookie Objects
    35.4.3. Zend_Http_Cookie getter methods
    35.4.4. Zend_Http_Cookie: Matching against a scenario
    35.4.5. The Zend_Http_CookieJar Class: Instantiation
    35.4.6. Adding Cookies to a Zend_Http_CookieJar object
    35.4.7. Retrieving Cookies From a Zend_Http_CookieJar object
    35.5. Zend_Http_Response
    35.5.1. Introduction
    35.5.2. Boolean Tester Methods
    35.5.3. Accessor Methods
    35.5.4. Static HTTP Response Parsers
    35.6. Zend_Http_UserAgent
    35.6.1. Overview
    35.6.2. Quick Start
    35.6.3. Configuration Options
    35.6.4. Available Methods
    35.6.5. Examples
    35.7. The UserAgent Device Interface
    35.7.1. Overview
    35.7.2. Quick Start
    35.7.3. Configuration Options
    35.7.4. Available Methods
    35.7.5. Examples
    35.8. The UserAgent Features Adapter
    35.8.1. Overview
    35.8.2. Quick Start
    35.8.3. Configuration Options
    35.8.4. Available Methods
    35.9. The WURFL UserAgent Features Adapter
    35.9.1. Overview
    35.9.2. Quick Start
    35.9.3. Configuration Options
    35.9.4. Available Methods
    35.10. The DeviceAtlas UserAgent Features Adapter
    35.10.1. Overview
    35.10.2. Quick Start
    35.10.3. Configuration Options
    35.10.4. Available Methods
    35.11. The TeraWurfl UserAgent Features Adapter
    35.11.1. Overview
    35.11.2. Quick Start
    35.11.3. Configuration Options
    35.11.4. Available Methods
    35.12. The UserAgent Storage Interface
    35.12.1. Overview
    35.12.2. Quick Start
    35.12.3. Configuration Options
    35.12.4. Available Methods
    35.13. The Session UserAgent Storage Adapter
    35.13.1. Overview
    35.13.2. Quick Start
    35.13.3. Configuration Options
    35.13.4. Available Methods

    35.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 this section).

    35.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.

    Przykład 35.1. Instantiating a Zend_Http_Client Object

    $client = new Zend_Http_Client('http://example.org', 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');

    [Notatka] Notatka

    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 this section for more information.

    35.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.

    Tabela 35.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 this section) 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 this section) 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
    encodecookies Whether to pass the cookie value through urlencode/urldecode. Enabling this breaks support with some web servers. Disabling this limits the range of values the cookies can contain. boolean TRUE

    35.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:

    Przykład 35.2. Performing a Simple GET Request

    $client = new Zend_Http_Client('http://example.org');
    $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 [6]. 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).

    Przykład 35.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();

    35.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.

    Przykład 35.4. Setting GET Parameters

    // Setting a get parameter using the setParameterGet method

    // This is equivalent to setting such URL:

    // Adding several parameters with one call
    'first_name'  => 'Bender',
    'middle_name' => 'Bending'
    => '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.

    Przykład 35.5. Setting POST Parameters

    // Setting a POST parameter

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

    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.

    35.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.

    digg delicious meneame google twitter technorati facebook