angular.js/test/ng, branch v1.1.1

fix($http): only set X-XSFR-TOKEN header for same-domain request

2012-11-26T22:58:59+00:00

This is needed to prevent CORS preflight checks. The XSFR token
is quite useless for CORS requests anyway.

BREAKING CHANGE: X-XSFR-TOKEN is no longer send for cross domain
requests. This shouldn't affect any known production service.

Closes #1096

fix($http): remove 'X-Requested-With' from header defaults

2012-11-26T22:36:40+00:00

X-Requested-With header is rarely used in practice and by using
it all the time we are triggering preflight checks for crossdomain
requests.

We could try detecting if we are doing CORS requests or not, but
it doesn't look like it's worth the trouble.

BREAKING CHANGE: X-Requested-With header is not set by $http service
any more. If anyone actually uses this header it's quite easy to add
it back via:

```
myAppModule.config(['$httpProvider', function($httpProvider) {
    $httpProvider.defaults.headers.common["X-Requested-With"] = 'XMLHttpRequest';
}]);
```

Closes #1004

fix($location): reset $location.$$replace with every watch call

2012-11-26T22:21:02+00:00

Closes #1111

fix(ngRepeat): support mostly-stable repeating for primitives

2012-11-26T19:36:53+00:00

I'm reverting changes that were originally done to ngRepeat to fix #933,
because these are now not necessary after the previous changes to keep
ngModel always synced with the DOM.

test(ngRepeat): clean up and improve tests

2012-11-26T19:36:52+00:00

test(ngRepeat): add test for issue #1076

2012-11-26T19:17:11+00:00

feat(form): add ability to reset a form to pristine state

2012-11-26T15:44:34+00:00

Retting a form to pristine state will cause all of the nested
form and form controls to be recursively reset as well.

Closes #856

fix(Scope): allow removing a listener during event

2012-11-25T10:39:54+00:00

feat($cacheFactory): cache.put now returns the added value

2012-11-24T23:01:34+00:00

This allows common programming patterns to be expressed with more
concise code.

See #1583 for code examples.

fix($http): config.param should expand array values properly

2012-11-24T21:26:23+00:00

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 #1363