Lines Matching refs:query

182 * Bug fix: `form_params` and `query` now always uses the `&` separator.
206 * Fixed a bug with serializing the `query` request option where the `&`
292   associative array passed into the `query` request option. The query string
294   can pass the query string in as a string.
323 * `Query` no longer typehints on the `$query` argument in the constructor,
330 This change updates query strings so that they are treated as un-encoded values
333 means that even value query string values (e.g., ":") are url encoded. This
335 want to send requests over the wire using valid query string characters that do
337 pass true as the second argument to specify that the query string is a raw
339 subsequently made, forcing the query-string to be converted into a Query
354   * No longer double percent-encoding characters in the path or query string if
358   * Note: This has been changed in 5.0.3 to now encode query string values by
359     default unless the `rawString` argument is provided when setting the query
361     query string without being percent encoded. See http://tools.ietf.org/html/rfc3986#appendix-A
542   the query aggregator used before uploading
543 * Added much more robust query string parsing
639 * Merging URLs will now use the query string object from the relative URL (thus allowing custom que…
673 * OauthPlugin now supports adding authentication to headers or query string (#425)
700 * `Guzzle\Http\QueryString::factory()` now guesses the most appropriate query aggregator to used ba…
726 …every request created by a client (e.g. default query string variables, headers, curl options, etc…
730       created by a command (e.g. custom headers, query string variables, timeout settings, etc.).
901 * Bug fix: Parsing a query string with a single PHP array value will now result in an array. #263
1031 * Bug: QueryString::fromString now properly parses query string parameters that contain equal signs
1167 * Bug: Query string values set to 0 are no longer dropped from the query string
1169 * Bug: `+` is now treated as an encoded space when parsing query strings