Implement HTTP request acception / rejection as defined in RFC 2616 - 8.2.3
Open
@adiroiban is already working on this.
Since Jun 27, 2022.
enhancement
new
priority-normal
web
- Dominant language
- Python
- Stars
- 6k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 10
Description
 |
@adiroiban reported |
|---|---|
| Trac ID | trac#6928 |
| Type | enhancement |
| Created | 2014-01-22 19:24:00Z |
Right now HTTPRequest will accept all request asking for accept: 100-continue
In my view it would be nice to let the resource to decide whether or not it wants to accept the request.
This might be a step toward fixing #4688 as it define a way for resource to notify the resource before body is received.
Link to RFC
http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html#sec8.2.3
Error handling:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.20
Searchable metadata
trac-id__6928 6928
type__enhancement enhancement
reporter__adiroiban adiroiban
priority__normal normal
milestone__
branch__
branch_author__
status__new new
resolution__None None
component__web web
keywords__
time__1390418640000000 1390418640000000
changetime__1470994174862351 1470994174862351
version__None None
owner__adiroiban adiroiban
cc__jknight cc__lukasaoz@...
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.
Assessment
This issue has not been assessed yet.