Flawed handling of URL redirect
Open
Nobody has claimed this yet.
3.7 (EOL)
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 36372 |
|---|---|
| Nosy | @orsenthil, @websurfer5 |
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-03-19.19:48:59.138>
labels = ['3.7', 'type-bug', 'library']
title = 'Flawed handling of URL redirect'
updated_at = <Date 2019-05-22.09:47:27.610>
user = 'https://bugs.python.org/bugburger'
bugs.python.org fields:
activity = <Date 2019-05-22.09:47:27.610>
actor = 'Jeffrey.Kintscher'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-03-19.19:48:59.138>
creator = 'bugburger'
dependencies = []
files = []
hgrepos = []
issue_num = 36372
keywords = []
message_count = 5.0
messages = ['338404', '338405', '338408', '338409', '338423']
nosy_count = 3.0
nosy_names = ['orsenthil', 'bugburger', 'Jeffrey.Kintscher']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue36372'
versions = ['Python 3.7']
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
The payload names no files or tests; begin by reading the migrated BPO issue 36372 and its five-message discussion, then locate the Python library code responsible for URL redirects. Done means the flawed redirect behavior is corrected and verified with coverage for the reported case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100