Document how to forward POST data on redirects

Open
#58,546 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

No documentation file or test is named in the issue. Start by locating the Python documentation for HTTP redirects and POST requests, then document how POST data is forwarded on redirects. Done means the relevant redirect behavior and guidance are clearly described; check linked PR gh-121681 first.

Written by the indexing model from the issue text.

Description

docs easy type-feature
BPO 14338
Nosy @orsenthil, @merwok

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 2012-03-16.20:25:01.281>
labels = ['easy', '3.8', '3.9', '3.10', 'type-feature', 'docs']
title = 'Document how to forward POST data on redirects'
updated_at = <Date 2020-11-16.00:01:26.251>
user = 'https://bugs.python.org/beerNuts'

bugs.python.org fields:

activity = <Date 2020-11-16.00:01:26.251>
actor = 'iritkatriel'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2012-03-16.20:25:01.281>
creator = 'beerNuts'
dependencies = []
files = []
hgrepos = []
issue_num = 14338
keywords = ['easy (C)']
message_count = 3.0
messages = ['156080', '156108', '156346']
nosy_count = 5.0
nosy_names = ['orsenthil', 'eric.araujo', 'docs@python', 'crustymonkey', 'beerNuts']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue14338'
versions = ['Python 3.8', 'Python 3.9', 'Python 3.10']

Linked PRs
  • gh-121681
Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.