{"push_id":1240078660,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"fdf8e0f9889c4ee55c055f09aab57030314c6fde","before":"ec565ddd9c536aa7f7441e89f03ea08e23de1a42","commits":[{"sha":"fdf8e0f9889c4ee55c055f09aab57030314c6fde","author":{"name":"Georgios Kalpakas","email":"9d5e538cb1776bf4a0dbe71079c797bb723aaf7d@gmail.com"},"message":"fix($httpBackend): complete the request on timeout\n\nWhen using the [timeout attribute](https://xhr.spec.whatwg.org/#the-timeout-attribute) and an XHR\nrequest times out, browsers trigger the `timeout` event (and execute the XHR's `ontimeout`\ncallback). Additionally, Safari 9 handles timed-out requests in the same way, even if no `timeout`\nhas been explicitly set on the XHR.\nIn the above cases, `$httpBackend` would fail to capture the XHR's completing (with an error), so\nthe corresponding `$http` promise would never get fulfilled.\n\nNote that using `$http`'s `timeout` configuration option does **not** rely on the XHR's `timeout`\nproperty (or its `ontimeout` callback).\n\nFixes #14969\nCloses #14972","distinct":true,"url":"https://api.github.com/repos/angular/angular.js/commits/fdf8e0f9889c4ee55c055f09aab57030314c6fde"}]}
{"actor":{"display_login":"gkalpak"}}