should `expires` be removed from set_cookie?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 443
- Forks
- 206
- PR merge metrics
- No merged PRs in 30d
Description
While dealing with some cookie issues and visiting the docs, I learned that expires is scheduled to be removed in v1.9. The most I could find on this is some mentions on #254;
Is there any chance this decision can be revisited?
While I'm not a fan of the confusion between expires and max-age, the active RFC lists both (https://datatracker.ietf.org/doc/html/rfc6265#section-5.2.1) and do the http guides from Mozilla and some other large projects. Depending on integration, we often have to set cookies with the Expires param.
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 reviewing the documentation references to expires, the discussion in issue #254, and the cited RFC 6265 section 5.2.1. Determine whether the planned removal from set_cookie should be revisited and document the project’s decision; the issue does not name an implementation file or test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100