Feature #1567
Handle both 401 and 403 errors when authentication fails
| Status: | Closed | Start date: | 10/24/2011 | |
|---|---|---|---|---|
| Priority: | Medium | Due date: | ||
| Assignee: | Panagiotis Kanavos | % Done: | 0% |
|
| Category: | Networking | Spent time: | - | |
| Target version: | Alpha | Estimated time: | 2.00 hours |
Description
401 means the token is missing
403 means the user is not allowed to access a resource
Related issues
History
#1 Updated by Panagiotis Kanavos over 12 years ago
- Category set to Networking
- Assignee set to Panagiotis Kanavos
- Estimated time set to 2.00
#2 Updated by Panagiotis Kanavos over 12 years ago
- Target version set to Alpha
#3 Updated by Panagiotis Kanavos about 12 years ago
- Status changed from New to Closed
Solved by notifying the user and limiting the reauthentication functionality only to the Preferences page