Better CSRF Handling. #115
Labels
No labels
Bug
Cleanup/Refactor
Core Feature
Documentation
Feature
Performance Improvement
Security Improvement
UX/Accessibility
Unreproducable Bug
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: rainbownapkin/canopy#115
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Current version of canopy throws a popup error when CSRF tokens are bad.
This is confusing and concerning to most users.
Preferably we could pull a new CSRF token in background, maybe even retry the last request auto-magically.
Otherwise, we could lazily refresh the page with a warning pop-up, but this is probably bad UX design.
Improved CSRF Handling:
1f00bacb6f