My application uses a 15-minute timeout interval, since it is a secure
application that contains PHI (protected health information). The default
behavior of this timeout was such that the user would attempt to navigate
after the interval had been exceeded and the response would simply come
back empty with no indication that they had timed-out. Recently we
implemented a feature that would redirect the user to the sign-in page if
the timeout had been exceeded. The way that we've done that is by reloading
the window if a 401 response is received.
qdw.config ($httpProvider, $location, $q) ->
$httpProvider.interceptors.push ($location, $q) ->
responseError: (response) ->
if response.status == 401
window.location.reload()
$q.reject response
This works great in Chrome, Firefox, and other modern browsers. However it
hangs IE9 even if the timeout interval has not been exceeded (e.g upon
initial login). We're relatively new to Angular so I suspect we've perhaps
misused interceptors here. Can anyone offer some guidance?
Thanks,
Josh
--
You received this message because you are subscribed to the Google Groups
"AngularJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.
