dash-update-component 305 error when Dash App embedded in Flask server is launched with both csrf protection and dash_auth
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 135
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
There appears to be a conflict between flash csrf tokens and dash apps protected with dash_auth.
If the CSRF token is left enabled, Dash App callbacks will not render.
If the CSRF token is disabled OR if dash_auth is disabled, the callbacks work.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the embedded Flask server with both CSRF protection and dash_auth enabled, then compare it with each protection disabled. Investigate why Dash callbacks return the reported 305 error and verify that callbacks render while both protections remain enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flask, python
- Domain
- authentication, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100