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
The current $http cache takes only the url as key. Consider the case where a call to the API uses the 'Range' header for pagination and cache is set to true. All requests to the same url with different pagination will return the first cached response to the inital page. IMHO headers are a defining part of the request, just like the url, and should therefore be included in the cache key.
Are there plans to include this? Would you accept a pull request?
The text was updated successfully, but these errors were encountered:
The current $http cache takes only the url as key. Consider the case where a call to the API uses the 'Range' header for pagination and cache is set to true. All requests to the same url with different pagination will return the first cached response to the inital page. IMHO headers are a defining part of the request, just like the url, and should therefore be included in the cache key.
Are there plans to include this? Would you accept a pull request?
The text was updated successfully, but these errors were encountered: