Better CSRF Handling. #115

Closed
opened 2025-04-26 08:45:00 -04:00 by rainbownapkin · 1 comment
rainbownapkin commented 2025-04-26 08:45:00 -04:00 (Migrated from gitlab.com)

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.

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.
rainbownapkin (Migrated from gitlab.com) closed this issue 2025-05-04 18:03:59 -04:00
rainbownapkin commented 2025-05-04 18:04:00 -04:00 (Migrated from gitlab.com)

Improved CSRF Handling: 1f00bacb6f

Improved CSRF Handling: 1f00bacb6fd6fe28e33a2a985dceb9d8c4e762f4
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: rainbownapkin/canopy#115
No description provided.