RC5 Breaking Change - Http UMD

[robinkedia]

I'm submitting a ... (check one with "x")

[ X] bug report
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior
Post RC5 upgrade, facing below error -

platform-browser.umd.js:937 EXCEPTION: TypeError: Cannot read property 'toString' of nullBrowserDomAdapter.logError @ platform-browser.umd.js:937BrowserDomAdapter.logGroup @ platform-browser.umd.js:947ExceptionHandler.call @ core.umd.js:4389next @ core.umd.js:9971schedulerFn @ core.umd.js:9168SafeSubscriber.__tryOrUnsub @ Subscriber.ts:240SafeSubscriber.next @ Subscriber.ts:192Subscriber._next @ Subscriber.ts:133Subscriber.next @ Subscriber.ts:93Subject._finalNext @ Subject.ts:154Subject._next @ Subject.ts:144Subject.next @ Subject.ts:90EventEmitter.emit @ core.umd.js:9156onError @ core.umd.js:9394onHandleError @ core.umd.js:9266ZoneDelegate.handleError @ zone.js:327Zone.runTask @ zone.js:259drainMicroTaskQueue @ zone.js:474ZoneTask.invoke @ zone.js:426
platform-browser.umd.js:937 STACKTRACE:BrowserDomAdapter.logError @ platform-browser.umd.js:937ExceptionHandler.call @ core.umd.js:4391next @ core.umd.js:9971schedulerFn @ core.umd.js:9168SafeSubscriber.__tryOrUnsub @ Subscriber.ts:240SafeSubscriber.next @ Subscriber.ts:192Subscriber._next @ Subscriber.ts:133Subscriber.next @ Subscriber.ts:93Subject._finalNext @ Subject.ts:154Subject._next @ Subject.ts:144Subject.next @ Subject.ts:90EventEmitter.emit @ core.umd.js:9156onError @ core.umd.js:9394onHandleError @ core.umd.js:9266ZoneDelegate.handleError @ zone.js:327Zone.runTask @ zone.js:259drainMicroTaskQueue @ zone.js:474ZoneTask.invoke @ zone.js:426
platform-browser.umd.js:937 TypeError: Cannot read property 'toString' of null
at Request.Body.text (http.umd.js:1138)
at Request.getBody (http.umd.js:1720)
at Observable.eval as _subscribe
at Observable.subscribe (Observable.ts:93)
at Observable._subscribe (Observable.ts:152)
at MapOperator.call (map.ts:54)
at Observable.subscribe (Observable.ts:93)
at Observable._subscribe (Observable.ts:152)
at CatchOperator.call (catch.ts:32)
at Observable.subscribe (Observable.ts:93)BrowserDomAdapter.logError @ platform-browser.umd.js:937ExceptionHandler.call @ core.umd.js:4392next @ core.umd.js:9971schedulerFn @ core.umd.js:9168SafeSubscriber.__tryOrUnsub @ Subscriber.ts:240SafeSubscriber.next @ Subscriber.ts:192Subscriber._next @ Subscriber.ts:133Subscriber.next @ Subscriber.ts:93Subject._finalNext @ Subject.ts:154Subject._next @ Subject.ts:144Subject.next @ Subject.ts:90EventEmitter.emit @ core.umd.js:9156onError @ core.umd.js:9394onHandleError @ core.umd.js:9266ZoneDelegate.handleError @ zone.js:327Zone.runTask @ zone.js:259drainMicroTaskQueue @ zone.js:474ZoneTask.invoke @ zone.js:426
zone.js:463 TypeError: Cannot read property 'toString' of null(…)consoleError @ zone.js:463drainMicroTaskQueue @ zone.js:477ZoneTask.invoke @ zone.js:426

Angular version: 2.0.0-rc.5

• Browser: [all]
• Language: [all | TypeScript 1.8.10 | ES5]

[goldibex]

I get this error also on HTTP requests:

browser_adapter.ts:82 TypeError: Cannot read property 'toString' of null
    at Request.Body.text (body.ts:56)
    at Request.getBody (static_request.ts:152)
    at Observable.eval [as _subscribe] (xhr_backend.ts:134)
    at Observable.subscribe (Observable.ts:93)
    at Object.subscribeToResult (subscribeToResult.ts:32)
    at SwitchMapSubscriber._innerSub (switchMap.ts:109)
    at SwitchMapSubscriber._next (switchMap.ts:101)
    at SwitchMapSubscriber.Subscriber.next (Subscriber.ts:93)
    at FirstSubscriber._emitFinal (first.ts:140)
    at FirstSubscriber._emit (first.ts:124)

BrowserDomAdapter.logError @ browser_adapter.ts:82
ExceptionHandler.call @ exception_handler.ts:62
next @ application_ref.ts:362
schedulerFn @ async.ts:95
SafeSubscriber.__tryOrUnsub @ Subscriber.ts:240
SafeSubscriber.next @ Subscriber.ts:192
Subscriber._next @ Subscriber.ts:133
Subscriber.next @ Subscriber.ts:93
Subject._finalNext @ Subject.ts:154
Subject._next @ Subject.ts:144
Subject.next @ Subject.ts:90
EventEmitter.emit @ async.ts:80
onError @ ng_zone.ts:142
onHandleError @ ng_zone_impl.ts:95
ZoneDelegate.handleError @ zone.js:327
Zone.runTask @ zone.js:259
ZoneTask.invoke @ zone.js:423

[goldibex]

And I've double-checked that the response did, in fact, have body text.

[goldibex]

Ah, but the request didn't, because it was a GET.

[goldibex]

For me, this turned out to be because I use Http#request directly with a RequestOptionsArgs that I constructed myself. I tried explicitly setting an empty body (body: "") and everything works again.

[robinkedia]

@goldibex - Could you please help share some sample code so I can understand better. Appreciate your help. Thanks!

[qdouble]

basically, if you're using request options, you have to make a get request, you can't leave the body empty.

options = new RequestOptions({
    body: '',
    headers: this.noPreFlightHeaders,
    withCredentials: true
  });

[robinkedia]

@qdouble @goldibex - What has changed from RC4 to RC5 that we have to explicitly set body to ''. Thanks!

[robwormald]

this would be an easy PR if anybody wants to fix

[qdouble]

@robinkedia it's not documented, but it must have been one of the recent commits to http. I see rob has just labeled it as a bug.

[robinkedia]

@goldibex @qdouble - Thanks, I have temporarily fixed this using body:''