TooAngel / TooAngel/worlddriven
Fix secure cookie configuration
Open
Nobody has claimed this yet.
bug
security
- Dominant language
- JavaScript
- Stars
- 18
- Forks
- 15
- Avg merge
- 8d 14h
- Merged PRs (30d)
- 5
Description
Configure cookies to be set as secure in production environment.
Context:
- Cookies are currently not set to secure
- Production environment uses HTTPS with 2-level proxy setup
- Session security requires secure cookie configuration
Acceptance Criteria:
- Configure session cookies with secure flag
- Test cookie behavior with 2-level proxy setup
- Verify session persistence works correctly
- Ensure proper cookie configuration for HTTPS
- Update proxy trust settings if needed
Priority: Medium
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 locating the session-cookie and proxy-trust configuration, then reproduce the HTTPS two-level-proxy setup described in the issue. Verify secure cookies and session persistence in production-like conditions. Done means the secure flag and any required proxy settings work correctly without breaking sessions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authentication, backend, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100