You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 12, 2024. It is now read-only.
By default, $http({...options...}) will issue GET requests. However, the requests are not cached (even when specifying a cache option) UNLESS the method: 'GET' key/value are included in the options passed to $http- it's not mixed into the configuration as a default value.
Should $http throw an exception without a specified method, or should ALL $http behavior work by assuming the method is GET unless otherwise specified?
I'm open to taking a stab at a pull request, but it'll be a few days and I wanted to get this in while I had time.
The text was updated successfully, but these errors were encountered:
I think if we are issuing the request as a GET request (and it's not the browser deciding to do that on its own) then this is a bug to be fixed, and most likely a trivial one to correct.
I'm not sure if this should be a documentation or code fix, but the problem is fairly simple- it's line 933 of https://github.com/angular/angular.js/blob/master/src/ng/http.js:
By default, $http({...options...}) will issue GET requests. However, the requests are not cached (even when specifying a cache option) UNLESS the method: 'GET' key/value are included in the options passed to $http- it's not mixed into the configuration as a default value.
Should $http throw an exception without a specified method, or should ALL $http behavior work by assuming the method is GET unless otherwise specified?
I'm open to taking a stab at a pull request, but it'll be a few days and I wanted to get this in while I had time.
The text was updated successfully, but these errors were encountered: