$xhr posts JSON data as form-urlencoded

[efleming969]

When posting an object via $xhr

$xhr('/some/uri', 'POST', {some:'object'});

The default behavior is to encode that object as JSON. This would be fine if the default Content-Type of $browser.xhr was application/json, but it's application/x-www-form-urlencoded.

Since you can't set the Content-Type via $xhr (see #180), then this feature is virtually unusable, confusing and probably an inappropriate default.

Solution is to urlencode the object instead of JSON

[IgorMinar]

as of 0.9.17 you can override the default headers, and we do plan to make further changes to deal with this better, but giving the flexibility to change headers is the first step.