urllib.request.Request accepts but doesn't check bytes headers
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 | 29891 |
|---|---|
| Nosy | @orsenthil, @ezio-melotti, @vadmium, @soltysh |
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 2017-03-23.22:03:56.696>
labels = ['3.7', 'type-bug', 'library']
title = "urllib.request.Request accepts but doesn't check bytes headers"
updated_at = <Date 2017-03-25.01:01:46.654>
user = 'https://github.com/ezio-melotti'
bugs.python.org fields:
activity = <Date 2017-03-25.01:01:46.654>
actor = 'martin.panter'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-03-23.22:03:56.696>
creator = 'ezio.melotti'
dependencies = []
files = []
hgrepos = []
issue_num = 29891
keywords = []
message_count = 2.0
messages = ['290063', '290457']
nosy_count = 4.0
nosy_names = ['orsenthil', 'ezio.melotti', 'martin.panter', 'maciej.szulik']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'test needed'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue29891'
versions = ['Python 3.5', 'Python 3.6', '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
Start with the urllib.request.Request entry point and read the linked BPO issue 29891 for the intended handling of bytes headers. Clarify whether bytes headers should be rejected or validated, then identify the relevant regression coverage; done means the behavior is explicit and covered by a test.
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
- Needs clarification
- Newbie friendliness
- 35/100