We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using BrowserClient instead of HttpRequest throws a spurious error: "Invalid status code 0" even when the http response code is 200
--------------EXCEPTION------------------------------------------ EXCEPTION: Invalid argument(s): Invalid status code 0. VM14600:1 STACKTRACE:(anonymous function) @ VM14600:1 VM14600:1 package:http/src/base_response.dart 48:7 BaseResponse.BaseResponse package:http/src/streamed_response.dart 31:7 StreamedResponse.StreamedResponse package:http/browser_client.dart 64:32 BrowserClient.send.<async>.<fn>.<fn> package:stack_trace StackZoneSpecification.registerUnaryCallback.<fn> package:angular2/src/core/zone/ng_zone_impl.dart 162:40 NgZoneImpl._runUnary.<fn> dart:async _ZoneDelegate.run package:angular2/src/core/zone/ng_zone_impl.dart 155:21 NgZoneImpl._run package:angular2/src/core/zone/ng_zone_impl.dart 162:7 NgZoneImpl._runUnary package:stack_trace StackZoneSpecification.registerUnaryCallback.<fn> package:angular2/src/core/zone/ng_zone_impl.dart 162:40 NgZoneImpl._runUnary.<fn> dart:async _ZoneDelegate.run package:angular2/src/core/zone/ng_zone_impl.dart 155:21 NgZoneImpl._run package:angular2/src/core/zone/ng_zone_impl.dart 162:7 NgZoneImpl._runUnary -----async gap----- dart:async _Future.then package:http/browser_client.dart 62:27 BrowserClient.send.<async>.<fn> package:stack_trace StackZoneSpecification.registerUnaryCallback.<fn> package:angular2/src/core/zone/ng_zone_impl.dart 162:40 NgZoneImpl._runUnary.<fn> dart:async _ZoneDelegate.run package:angular2/src/core/zone/ng_zone_impl.dart 155:21 NgZoneImpl._run package:angular2/src/core/zone/ng_zone_impl.dart 162:7 NgZoneImpl._runUnary package:stack_trace StackZoneSpecification.registerUnaryCallback.<fn> package:angular2/src/core/zone/ng_zone_impl.dart 162:40 NgZoneImpl._runUnary.<fn> dart:async _ZoneDelegate.run package:angular2/src/core/zone/ng_zone_impl.dart 155:21 NgZoneImpl._run package:angular2/src/core/zone/ng_zone_impl.dart 162:7 NgZoneImpl._runUnary -----async gap----- dart:async _Future.then package:http/browser_client.dart 56:22 BrowserClient.send.<async> package:stack_trace StackZoneSpecification.registerUnaryCallback.<fn> package:angular2/src/core/zone/ng_zone_impl.dart 162:40 NgZoneImpl._runUnary.<fn> dart:async _ZoneDelegate.run package:angular2/src/core/zone/ng_zone_impl.dart 155:21 NgZoneImpl._run package:angular2/src/core/zone/ng_zone_impl.dart 162:7 NgZoneImpl._runUnary dart:async _Future._asyncComplete.<fn> package:angular2/src/core/zone/ng_zone_impl.dart 176:11 NgZoneImpl._scheduleMicrotask.<fn> dart:async _ZoneDelegate.run package:angular2/src/core/zone/ng_zone_impl.dart 155:21 NgZoneImpl._run -----async gap----- dart:async _asyncThenWrapperHelper package:http/browser_client.dart BrowserClient.send package:http/src/base_client.dart 171:38 BaseClient._sendUnstreamed.<async> dart:async _ZoneDelegate.run package:angular2/src/core/zone/ng_zone_impl.dart 155:21 NgZoneImpl._run dart:async _CustomZone.bindCallback.<fn> package:angular2/src/core/zone/ng_zone_impl.dart 176:11 NgZoneImpl._scheduleMicrotask.<fn> dart:async _ZoneDelegate.run package:angular2/src/core/zone/ng_zone_impl.dart 155:21 NgZoneImpl._run -----async gap----- dart:async Future.Future.microtask package:http/src/base_client.dart BaseClient._sendUnstreamed package:http/src/base_client.dart 34:5 BaseClient.get
The text was updated successfully, but these errors were encountered:
Can you provide code that consistently reproduces this?
Sorry, something went wrong.
No branches or pull requests
Using BrowserClient instead of HttpRequest throws a spurious error: "Invalid status code 0" even when the http response code is 200
The text was updated successfully, but these errors were encountered: