Handling 401 on GET and/or manually re-queueing

[pullaf]

I'm trying to handle login timeouts (and idling) by prompting an unlock screen overlaid to the page that's shown through an HttpInterceptor on 401 requests
I've also queued the failed requests to send them again manually since your plugin doesn't do that for GET but I must've missed something cause the resent request doesn't seem to trigger the plugin to update the data/promise/whatever I've linked to it... how can I handle this?

[felippenardi]

Hi @TheMdk!

I have not contributed at to this repository, but I'd like to try to help. Can you recreate this problem in a jsfiddle (or any other service) so we can see how you are hooking up angular-cached-resource with a manual queue for failed requests to be sent as soon as the user re-logins?