Installation License Contributing Reporting a security vulnerability Quickstart Make a Request Using Responses Query String Parameters Uploading Data Cookies Redirects Exceptions Clients Creating a client Options Event Subscribers Environment Variables Request and Response Messages Headers Body Requests Responses Event System Event Emitters Event Priorities Working With Request Events Streams Creating Streams stream context options? Why am I getting an SSL verification error? What is this Maximum function nesting error? Why am I getting a 417 error response? HTTP Components There are a number of optional libraries

URLs. You can find out all about clients in the Clients page of the documentation. 1.2.2 Using Responses In the previous examples, we retrieved a $response variable. This value is actually a GuzzleHt $response->getBody(); while (!$body->eof()) { echo $body->read(1024); } JSON Responses You can more easily work with JSON responses using the json() method of a response. $response = $client->get('http://httpbin PHP’s json_decode() function to parse responses. If Guzzle is unable to parse the JSON response body, then a GuzzleHttp\Exception\ParseException is thrown. XML Responses You can use a response’s xml() method

synchronous and asynchronous requests using the same interface. Uses PSR-7 interfaces for requests, responses, and streams. This allows you to utilize other PSR-7 compatible libraries with Guzzle. Abstracts Making a Request Creating a Client Sending Requests Async Requests Concurrent requests Using Responses Query String Parameters Uploading Data POST/Form Requests Cookies Redirects Exceptions Environment Complex Headers Body Requests Request Methods Request URI Scheme Host Port Path Query string Responses Start-Line Body Streams Creating Streams Metadata Stream Decorators Handlers and Middleware

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.2.2 Using Responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.2.3 Query String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 1.4.4 Responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 1.4 1.7.5 Why am I getting an SSL verification error? . . . . . . . . . . . . . . . . . . . . . . . . . . 45 1.7.6 What is this Maximum function nesting error? . . . . . . . . . . . . . . . . . . . . .

synchronous and asynchronous requests using the same interface. Uses PSR-7 interfaces for requests, responses, and streams. This allows you to utilize other PSR-7 compatible libraries with Guzzle. Abstracts Making a Request Creating a Client Sending Requests Async Requests Concurrent requests Using Responses Query String Parameters Uploading Data POST/Form Requests Cookies Redirects Exceptions Environment Complex Headers Body Requests Request Methods Request URI Scheme Host Port Path Query string Responses Start-Line Body Streams Creating Streams Metadata Stream Decorators Handlers and Middleware

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.2.2 Using Responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.2.3 Query String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 1.4.4 Responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 1.4 1.7.5 Why am I getting an SSL verification error? . . . . . . . . . . . . . . . . . . . . . . . . . . 45 1.7.6 What is this Maximum function nesting error? . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.2.2 Using Responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.2.3 Query String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 1.4.4 Responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 1.4 1.7.5 Why am I getting an SSL verification error? . . . . . . . . . . . . . . . . . . . . . . . . . . 43 1.7.6 What is this Maximum function nesting error? . . . . . . . . . . . . . . . . . . . . .

synchronous and asynchronous requests using the same interface. Uses PSR-7 interfaces for requests, responses, and streams. This allows you to utilize other PSR-7 compatible libraries with Guzzle. Abstracts Making a Request Creating a Client Sending Requests Async Requests Concurrent requests Using Responses Query String Parameters Uploading Data POST/Form Requests Cookies Redirects Exceptions Environment Complex Headers Body Requests Request Methods Request URI Scheme Host Port Path Query string Responses Start-Line Body Streams Creating Streams Metadata Stream Decorators Handlers and Middleware

Old Input iv. Cookies v. Files vi. Other Request Information v. Responses i. Basic Responses ii. Redirects iii. Other Responses iv. Response Macros vi. Views i. Basic Usage ii. View Composers Request Validation iv. Working With Error Messages v. Error Messages & Views vi. Available Validation Rules vii. Conditionally Adding Rules viii. Custom Error Messages ix. Custom Validation Rules x. These service providers provide various bootstrapping functions to your application, such as error handling, logging, route loading, and more. Of course, you are free to create additional service

request processing via middleware components and hooks Strict adherence to RFCs Idiomatic HTTP error responses Straightforward exception handling Snappy testing with WSGI/ASGI helpers and mocks CPython 3 Introducing Hooks Error Handling What Now? Tutorial (ASGI) First Steps Hosting Our App Configuration Image Store Images Resource(s) Running Our Application Dynamic Thumbnails Caching Responses Testing Our Capitalizing Response Header Names Parsing Nested Multipart Forms Outputting CSV Files Prettifying JSON Responses Decoding Raw URL Path Request ID Logging FAQ Design Philosophy Performance Routing Extensibility