openlibhums / openlibhums/janeway
403 error - safari setting
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 238
- Forks
- 97
- Avg merge
- 9d 1h
- Merged PRs (30d)
- 8
Description
Describe the bug
A user has reported consistently seeing a 403 error and has been seeing it for a while. We suspect it's CSRF token issue, where the cross site tracking setting in safari is not playing nice with Django. We've asked the user to check if changing the setting resolves the issue. If so, we'll need to find a way to work around this as it's suboptimal. (Whilst this specific user has been fine working around this, it may present an issue for less technical users and seems to have already done for one.)
Reported on: I am using Safari 18.5 (20621.2.5.11.8).
Janeway version
1.7.4.
BRF
We havent had any reports of this since, we need to investigate if this is a Django/Safari CSRF issue.
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 403 with Safari 18.5 and its cross-site tracking setting, using the reported Janeway 1.7.4 context. Investigate whether Django's CSRF handling causes the failure; done means establishing the cause and identifying or implementing a workable resolution for affected Safari users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100