maxking / maxking/docker-mailman
[BUG] Receiving Forbidden CSRF failure on password forgotten or password change
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 278
- Forks
- 121
- PR merge metrics
- No merged PRs in 30d
Description
Tag/version of Container Images
Version 0.4 and 0.5
I am receiving the error on first login.
environment variables set in docker compose:
- SERVE_FROM_DOMAIN=<mydomain.eu>
- MAILMAN_ADMIN_USER=postmaster
- MAILMAN_ADMIN_EMAIL=postmaster@<mydomain.eu>
Of course I am using mydomain.eu to access mailman.
Nginx configuration snippet:
location /static/ {
alias /opt/mailman/web/static/;
}
location / {
proxy_pass http://127.0.0.1:8000;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $remote_addr;
}
Contributor guide
No contributing guide indexed for this repository
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
Reproduce the password-forgotten or password-change flow using the listed Docker Compose variables and Nginx proxy configuration, starting with the first-login path. Check whether the proxy and configured domain preserve the request information needed for CSRF validation; done means those flows no longer return Forbidden CSRF failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, docker, nginx, python
- Domain
- authentication, backend, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100