Lines Matching refs:requests

43   the `query` request option when creating requests with clients. The `query`
152 The `body` option no longer accepts an array to send POST requests. Please use
163 HTTP requests. The `adapter` option in a `GuzzleHttp\Client` constructor
198 requests from completing. This can now be handled by throwing the exception or
199 by cancelling a pool of requests or each outstanding future request
226 - No longer requires cURL to send requests.
315 - Added the concept of adapters that are used to transfer requests over the
318 - Sending requests in parallel is still possible, but batching is no longer a
352   send multiple requests in parallel.
365   `batch_adapter` to use a custom adapter for sending requests in parallel, or
366   a `message_factory` to change the factory used to create HTTP requests and
369 - Creating requests with a client no longer automatically utilize a URI
386   separation between requests that contain a body and requests that do not
393   both requests and responses and is implemented in
445 Streaming requests can now be created by a client directly, returning a
496 Requests previously submitted a large number of requests. The number of events
565 - Message: Message parsing logic for both requests and responses has been moved
588   sending. This subscriber is attached to all requests by default.
666 was used in Guzzle 3 broke the actual interface of sending streaming requests
668 PHP requests are now implemented through the `GuzzleHttp\Adapter\StreamAdapter`.
851 to a single client can pollute requests dispatched from other clients.