Thank You, finally i found out root cause. we are using ACS login that is causing cors issue because it's other domain and that session is 10 mins.
On Thursday, November 5, 2015 at 9:25:59 PM UTC-8, Vaibhav Gupta wrote: > > Hi, > > I am not sure about your use case but this is what we follow in our > product: > > 1. For a user who has not logged in, we maintain a heart beat which > revives the session on server by sending a dummy request. > 2. For a user who is not logged in, we show him/her a warning message that > session is about to timeout. If no action is taken then we logout the user. > > I hope this gives you a direction. > > On Wednesday, 4 November 2015 05:24:50 UTC+5:30, DASA ANUDEEP wrote: >> >> Hi Team, >> >> I am facing one weird issue for my project. >> After going through so many links for session i went with ngIdle >> provider, below is config code. >> >> IdleProvider.idle(900); >> IdleProvider.timeout(300); >> KeepaliveProvider.interval(300); >> >> Idle.watch(); >> >> Webapi's resides in same domain and if i was idle for 10mins and then if >> i make any calls to webapi then i get aborted status. >> >> when i investigate further and found some info: >> session alive is not happening at client side and server is waiting for >> 10 mins, after that it aborted and not even calling webapi. >> >> please suggest me what is best way to handle session for angualrjs with >> webapi's. >> > -- 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.
