This repository has been archived by the owner on Apr 12, 2024. It is now read-only.
$http config.params doesn't treat array values properly #1363
Comments
IgorMinar
pushed a commit
to IgorMinar/angular.js
that referenced
this issue
Nov 26, 2012
Today, calling e.g. $http(url, { params: { a: [1,2,3] } }) results in a query
string like "?a=%5B1%2C2%2C3%5D" which is undesirable. This commit enhances
buildURL to createa query string like "?a=1&a=2&a=3".
BREAKING CHANGE: if the server relied on the buggy behavior then either the
backend should be fixed or a simple serialization of the array should be done
on the client before calling the $http service.
Closes angular#1363
marknadig
pushed a commit
to KonaTeam/angular.js
that referenced
this issue
Jan 28, 2013
Today, calling e.g. $http(url, { params: { a: [1,2,3] } }) results in a query
string like "?a=%5B1%2C2%2C3%5D" which is undesirable. This commit enhances
buildURL to createa query string like "?a=1&a=2&a=3".
BREAKING CHANGE: if the server relied on the buggy behavior then either the
backend should be fixed or a simple serialization of the array should be done
on the client before calling the $http service.
Closes angular#1363
This was referenced Jan 28, 2013
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Today, calling e.g.
$http(url, { params: { a: [1,2,3] } })results in a query string like?a=%5B1%2C2%2C3%5Dwhich is undesirable.The text was updated successfully, but these errors were encountered: