Opened 14 years ago
Closed 14 years ago
#15262 closed (duplicate)
generic views don't populate request.POST when handling PUT
| Reported by: | kenth | Owned by: | nobody |
|---|---|---|---|
| Component: | Core (Other) | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The new CBVs handle PUT as a synonym for POST, but django.http doesn't populate the request.POST & request.FILES for any verb except POST. I believe that PUT is being translated as an empty POST, which is not what I would have expected.
The CBV handling of PUT is in several places in django/views/generic/edit.py both in redirecting the put method definition and the get_form_kwargs() method.
Change History (2)
comment:1 by , 14 years ago
| Version: | 1.2 → SVN |
|---|
comment:2 by , 14 years ago
| Component: | Generic views → Core framework |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
This isn't a generic view problem -- it's more fundamental than that. Django's HTTP handler doesn't contain good support for HTTP verbs that aren't GET or PUT.
This has been reported in the past as #12635.