AbstractRequestEvent::getTransaction() as public.
GuzzleHttp\Client::getDefaultUserAgent as deprecated.
AppliesHeadersInterface to make applying headers to a request based on the body more generic and not specific to
null when creating a request with a client will ensure that the option is not set. This allows you to overwrite default request options on a per-request basis. See https://github.com/guzzle/guzzle/pull/937.
protocols array in the
allow_redirects request option.
"0" is now an allowed URI path. See https://github.com/guzzle/guzzle/pull/935.
Query no longer typehints on the
$query argument in the constructor, allowing for strings and arrays.
end event are now correctly wrapped with Guzzle specific exceptions if necessary.
This change updates query strings so that they are treated as un-encoded values by default where the value represents an un-encoded value to send over the wire. A Query object then encodes the value before sending over the wire. This means that even value query string values (e.g., ":") are url encoded. This makes the Query class match PHP's http_build_query function. However, if you want to send requests over the wire using valid query string characters that do not need to be encoded, then you can provide a string to Url::setQuery() and pass true as the second argument to specify that the query string is a raw string that should not be parsed or encoded (unless a call to getQuery() is subsequently made, forcing the query-string to be converted into a Query object).
to multipart/form-data payloads. See https://github.com/guzzle/guzzle/pull/871
GuzzleHttp\Pool::send() convenience method to match the docs.
application/x-www-form-urlencoded header when sending POST requests, allowing for customized headers. See https://github.com/guzzle/guzzle/issues/877
rawString argument is provided when setting the query string on a URL: Now allowing many more characters to be present in the query string without being percent encoded. See http://tools.ietf.org/html/rfc3986#appendix-A
getResponse method of these events if the response did not complete. https://github.com/guzzle/guzzle/issues/867
Adding support for non-blocking responses and some minor API cleanup.
GuzzleHttp\Pool which implements FutureInterface and transfers requests concurrently using a capped pool size as efficiently as possible.
hasListeners() to EmitterInterface.
GuzzleHttp\ClientInterface::sendAll and marked
GuzzleHttp\Client::sendAll as deprecated (it's still there, just not the recommended way).
The breaking changes in this release are relatively minor. The biggest thing to look out for is that request and response objects no longer implement fluent interfaces.
return $this) from requests, responses,
GuzzleHttp\Cookie\SetCookie. This blog post provides a good outline of why I did this: http://ocramius.github.io/blog/fluent-interfaces-are-evil/. This also makes the Guzzle message interfaces compatible with the current PSR-7 message proposal.
GuzzleHttp\Utils using camelCase.
GuzzleHttp\json_decode moved to
GuzzleHttp\get_path moved to
GuzzleHttp\set_path moved to
GuzzleHttpBatch should now be
GuzzleHttp\Pool::batch, which returns an
objectStorage. Using functions.php caused problems for many users: they aren't PSR-4 compliant, require an explicit include, and needed an if-guard to ensure that the functions are not declared multiple times.
GuzzleHttp\Adapter, these are now implemented as callables that are stored in
GuzzleHttp\Transaction. The Transaction object now exposes the request, response, and client as public properties. The getters and setters have been removed.
asArray parameter from
GuzzleHttp\Message\MessageInterface::getHeader. If you want to get a header value as an array, then use the newly added
getHeaderAsArray() method of
MessageInterface. This change makes the Guzzle interfaces compatible with the PSR-7 interfaces.
GuzzleHttp\Message\MessageFactory no longer allows subclasses to add custom request options using double-dispatch (this was an implementation detail). Instead, you should now provide an associative array to the constructor which is a mapping of the request option name mapping to a function that applies the option value to a request.
GuzzleHttp\Stream\StreamInterface::getContents() no longer accepts a
maxLen parameter. This update makes the Guzzle streams project compatible with the current PSR-7 proposal.
GuzzleHttp\Stream\Utils::create no longer accept a size in the second argument. They now accept an associative array of options, including the "size" key and "metadata" key which can be used to provide custom metadata.
request_fulluri in stream adapter proxies.
Content-Encoding response bodies using the
decode_content request option. This is set to
true by default to decode the response body if it comes over the wire with a
Content-Encoding. Set this value to
false to disable decoding the response content, and pass a string to provide a request
Accept-Encoding header and turn on automatic response decoding. This feature now allows you to pass an
Accept-Encoding header in the headers of a request but still disable automatic response decoding. Closes https://github.com/guzzle/guzzle/issues/764
Please login to add feedback.