#20478 closed New feature (fixed)
Add basic support for HTTP PATCH method in generic views
| Reported by: | Krzysztof Jurewicz | Owned by: | Krzysztof Jurewicz |
|---|---|---|---|
| Component: | Generic views | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | yes | UI/UX: | no |
Description
There is a RFC describing HTTP method named PATCH:
http://tools.ietf.org/html/rfc5789
Quoting that RFC:
The difference between the PUT and PATCH requests is reflected in the
way the server processes the enclosed entity to modify the resource
identified by the Request-URI. In a PUT request, the enclosed entity
is considered to be a modified version of the resource stored on the
origin server, and the client is requesting that the stored version
be replaced. With PATCH, however, the enclosed entity contains a set
of instructions describing how a resource currently residing on the
origin server should be modified to produce a new version.”
Basic PATCH method support can be added to django.views.generic.base.View and django.views.generic.base.RedirectView. Further details and discussion are available on django-developers.
Change History (4)
comment:1 by , 12 years ago
| Has patch: | set |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
comment:3 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
I’ve created a pull request: https://github.com/django/django/pull/1198. Changing triage stage to “accepted” based on discussion on django-developers.