Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

If an api call is un authorized, what should be done? #100

Closed
tareq89 opened this issue Jul 16, 2016 · 2 comments
Closed

If an api call is un authorized, what should be done? #100

tareq89 opened this issue Jul 16, 2016 · 2 comments

Comments

@tareq89
Copy link
Member

tareq89 commented Jul 16, 2016

_Background_
Sometimes, after opening the webcat, it is found that the access token is saved on the browser's local storage, but its validity has ended. In that case, the authorized api calls return unauthorized 401 error.
How that should be handled in the WebCat?

Even after login out and in once more, the api calls returns unauthorized until a full page refresh!

@tareq89
Copy link
Member Author

tareq89 commented Jul 21, 2016

#105

@ahmdfsl
Copy link

ahmdfsl commented Jul 21, 2016

#34

@tareq89 tareq89 closed this as completed Jul 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants