Guzzle 6.1 solution right from the docs. use GuzzleHttp\Client; use GuzzleHttp\TransferStats; $client = new Client; $client->get(‘http://some.site.com’, [ ‘query’ => [‘get’ => ‘params’], ‘on_stats’ => function (TransferStats $stats) use (&$url) { $url = $stats->getEffectiveUri(); } ])->getBody()->getContents(); echo $url; // http://some.site.com?get=params
If you are using Guzzle v=6.0.* $client = new GuzzleHttp\Client([‘headers’ => [‘X-Foo’ => ‘Bar’]]); read the doc, there are more options.
Why use Guzzle? First of all Guzzle is an abstraction layer for http request, although it uses cURL by default you can use any other http client that you want: Does Guzzle require cURL? No. Guzzle can use any HTTP handler to send requests. This means that Guzzle can be used with cURL, PHP’s stream … Read more
If you’re using Guzzle 5.0 or newer, the docs say that basic auth is specified using the auth parameter: $client = new GuzzleHttp\Client(); $response = $client->get(‘http://www.server.com/endpoint’, [ ‘auth’ => [ ‘username’, ‘password’ ] ]); Please note that the syntax is different if you’re using Guzzle 3.0 or earlier. The constructor is different, and you also … Read more
You should use $this->client = new GuzzleClient([‘defaults’ => [ ‘verify’ => false ]]); i.e. a Boolean false, not the string ‘false’ The documentation is here: https://docs.guzzlephp.org/en/5.3/clients.html#verify Note: a few people have given other answers that apply to Guzzle 6+. They’re good answers if you are using those versions (but the original question was explicitly about … Read more
Depending on your project, disabling exceptions for guzzle might be necessary. Sometimes coding rules disallow exceptions for flow control. You can disable exceptions for Guzzle 3 like this: $client = new \Guzzle\Http\Client($httpBase, array( ‘request.options’ => array( ‘exceptions’ => false, ) )); This does not disable curl exceptions for something like timeouts, but now you can … Read more
Since Marco’s answer is deprecated, you must use the following syntax (according jasonlfunk’s comment) : $client = new \GuzzleHttp\Client(); $response = $client->request(‘POST’, ‘http://www.example.com/user/create’, [ ‘form_params’ => [ ’email’ => ‘test@gmail.com’, ‘name’ => ‘Test user’, ‘password’ => ‘testpassword’, ] ]); Request with POST files $response = $client->request(‘POST’, ‘http://www.example.com/files/post’, [ ‘multipart’ => [ [ ‘name’ => ‘file_name’, … Read more
Guzzle 6.x Per the docs, the exception types you may need to catch are: GuzzleHttp\Exception\ClientException for 400-level errors GuzzleHttp\Exception\ServerException for 500-level errors GuzzleHttp\Exception\BadResponseException for both (it’s their superclass) Code to handle such errors thus now looks something like this: $client = new GuzzleHttp\Client; try { $client->get(‘http://google.com/nosuchpage’); } catch (GuzzleHttp\Exception\ClientException $e) { $response = $e->getResponse(); $responseBodyAsString … Read more
I use json_decode($response->getBody()) now instead of $response->json(). I suspect this might be a casualty of PSR-7 compliance.
Guzzle implements PSR-7. That means that it will by default store the body of a message in a Stream that uses PHP temp streams. To retrieve all the data, you can use casting operator: $contents = (string) $response->getBody(); You can also do it with $contents = $response->getBody()->getContents(); The difference between the two approaches is that … Read more