Lines Matching refs:in

21   is now present in the `GuzzleHttp\Psr7` namespace provided by the
29      Note: there has been movement in the React project to modify promises to
38 - `GuzzleHttp\Mimetypes` has been moved to a function in
46   string in as a string. There are a couple helper functions that will make
52   present in RingPHP have been modified to work directly with PSR-7 messages
53   and placed in the `GuzzleHttp\Handler` namespace. This significantly reduces
54   complexity in Guzzle, removes a dependency, and improves performance. RingPHP
78 - Guzzle now uses `Psr\Http\Message\UriInterface` (implements in
80 - Static functions in `GuzzleHttp\Utils` have been moved to namespaced
96 side effects in order to work. With immutable messages, you have to change your
103 the way in and the promise of the response on the way out. This is a much
123 middleware. The idiomatic way in v6 to modify the request/response lifecycle is
163 HTTP requests. The `adapter` option in a `GuzzleHttp\Client` constructor
188   deprecated in favor of using `GuzzleHttp\Pool::batch()`.
206 a similar behavior in a number of ways. One example might be to use a
232   now utilized in `GuzzleHttp\Event\EmitterInterface` (resulting in significant
274   `GuzzleHttp\Event\Event`, and Guzzle now has an EventInterface in
318 - Sending requests in parallel is still possible, but batching is no longer a
325 - `GuzzleHttp\StaticClient` has been removed. Use the functions provided in
327 - Exceptions in `GuzzleHttp\Exception` have been updated to all extend from
352   send multiple requests in parallel.
365   `batch_adapter` to use a custom adapter for sending requests in parallel, or
371   `createRequest`, `get`, `put`, etc.) in order to expand a URI template.
393   both requests and responses and is implemented in
419   of the custom headers are now handled separately in specific
459 // Read some data off of the stream in the response body
465 The `configureRedirects()` method has been removed in favor of a
501 methods and a way in which to modify the transaction at that specific point in
545   it's easier to just wrap an iterator in a generator that maps values.
559 make it possible to plug in custom parsers for cookies, messages, URI
560 templates, and URLs; however, this level of complexity is not needed in Guzzle
567   used in debugging or deserializing messages, so it doesn't make sense for
572 - Url: URL parsing is now performed in `GuzzleHttp\Url::fromString` (previously
598   after normal response parsing occurs in the guzzle/command package.
601 in separate repositories:
641 - `getMetadata` and `setMetadata` have been removed in favor of
666 was used in Guzzle 3 broke the actual interface of sending streaming requests
729 …tp\ClientInterface::get($uri = null, $headers = null, $options = array())`. You can still pass in a
736 The following methods were removed from interfaces. All of these methods are still available in the…
754 …ProviderInterface and DefaultCacheKeyProvider are no longer used. All of this logic is handled in a
755   CacheStorageInterface. These two objects and interface will be removed in a future version.
775 …Keeping the Host header and URL host in sync is now handled by overriding the addHeader method in …
788 * Removed Guzzle\Http\Message\Request::receivedRequestHeader() and implemented this functionality in
842 Emitting IO events from a RequestMediator is now a parameter that must be set in a request's curl o…
1128 …e\Plugin`. Many other changes occur within this namespace and are detailed in their own sections b…
1199 (See #217) (Fixed in 09daeb8c666fb44499a0646d655a8ae36456575e)