Use of CsrfError is inconsistent #13

New issue

Closed

opened 2025-07-20 22:19:49 +00:00 by BlakeRain · 0 comments

BlakeRain commented

2025-07-20 22:19:49 +00:00

(Migrated from github.com)

There is a specific CsrfError that was defined to allow special handling of a CSRF token error. This is not being used consistently, and also needs some work:

The CsrfError type uses an error page that does not exist.
Various handlers are not using CsrfError but poem::Error::from_status() (for a variety of StatusCode values).

There is a specific `CsrfError` that was defined to allow special handling of a CSRF token error. This is not being used consistently, and also needs some work: - [x] The `CsrfError` type uses an error page that does not exist. - [x] Various handlers are not using `CsrfError` but `poem::Error::from_status()` (for a variety of `StatusCode` values).

No milestone

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

BlakeRain/parcel#13

No description provided.

Rows
Columns