http.cookiejar.DefaultCookiePolicy should use current timestamp instead of last updated timestamp value for checking expiry
Open
Nobody has claimed this yet.
3.9 (EOL)
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 37246 |
|---|---|
| Nosy | @orsenthil, @vadmium, @serhiy-storchaka, @tirkarthi |
| PRs |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2019-06-12.11:59:44.793>
labels = ['type-bug', 'library', '3.9']
title = 'http.cookiejar.DefaultCookiePolicy should use current timestamp instead of last updated timestamp value for checking expiry'
updated_at = <Date 2019-07-30.14:43:51.805>
user = 'https://github.com/tirkarthi'
bugs.python.org fields:
activity = <Date 2019-07-30.14:43:51.805>
actor = 'nsiregar'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-06-12.11:59:44.793>
creator = 'xtreak'
dependencies = []
files = []
hgrepos = []
issue_num = 37246
keywords = ['patch']
message_count = 1.0
messages = ['345327']
nosy_count = 4.0
nosy_names = ['orsenthil', 'martin.panter', 'serhiy.storchaka', 'xtreak']
pr_nums = ['15023']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue37246'
versions = ['Python 3.9']
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 http.cookiejar.DefaultCookiePolicy in the Python standard-library source and inspect how expiry checks obtain their timestamp. Review python/cpython#15023 and the related issue history first; done means the policy checks expiry using the current timestamp and the relevant behavior is covered by tests identified while examining that area.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100