Lines Matching full:setting

144 * Bug fix: setting verify to false in the StreamHandler now disables peer
178 * Bug fix: Fixing the cURL `body_as_string` setting
224 * Removed the semantics of setting `default` to `true`. This is no longer
313 * Setting a request option to `null` when creating a request with a client will
359 default unless the `rawString` argument is provided when setting the query
487 * Fixed an issue in the CurlFactory that caused setting the `stream=false`
630 * Bug: CURLOPT_SSL_VERIFYHOST is now correctly set to false when setting `$certificateAuthority` to…
658 * Setting the `debug` request parameter to true shows verbose cURL output instead of using the LogP…
679 * Setting `additionalParameters` of a response to false is now honored when parsing responses with …
708 * Bug fix: Setting default options on a client now works
709 * Bug fix: Setting options on HEAD requests now works. See #352
719 * Not setting a `Content-MD5` on a command if calculating the Content-MD5 fails via the CommandCont…
725 …request. You can pass a 'request.options' configuration setting to a client to apply default reque…
771 …ou can now enable E_USER_DEPRECATED warnings to see if you are using a deprecated method by setting
793 * Always setting X-cache headers on cached responses
876 * Setting a response on a request will write to the custom request body from the response body if o…
910 * The new default CURLOPT_TIMEOUT setting has been increased to 150 seconds so that Guzzle works on…
935 * RequestFactory::create() now uses the key of a POST file when setting the POST file name
945 * BC: Setting a service description on a client will no longer modify the client's command factorie…
988 * Setting default headers on a client after setting the user-agent will not erase the user-agent se…
1159 * Bug: Setting the response body of a request to null after completing a request, not when setting
1229 * Bug: Setting the name of each ApiParam when creating through an ApiCommand