#17360: Documenting differences between Client.post et Client.put
-------------------------------+--------------------------------
Reporter: thibaultj | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version: SVN
Severity: Normal | Keywords: rest, put, testing
Triage Stage: Unreviewed | Has patch: 1
Easy pickings: 1 | UI/UX: 0
-------------------------------+--------------------------------
The [https://docs.djangoproject.com/en/dev/topics/testing/ testing
documentation] asserts that « Client.put() […] Acts just like
Client.post() except with the PUT request method. ». However, there's a
subtle difference in the manner django handles both methods.
When a requests comes with a PUT method, django won't process the
`request.POST` variable, even if the content is url encoded.
This issue was [https://code.djangoproject.com/ticket/12635 already
reported], but the decision was taken to leave things as this
([http://groups.google.com/group/django-
developers/browse_thread/thread/86838c8ac035d488 That was confirmed after
this discussion]).
However, I think there is a gap in documentation, since a user testing a
RESTful web service will meet a WTF!? effect when using a PUT request.
So I tried to make the documentation clearer, by explaining this
difference, and explaining the way to overcome the issue.
[https://github.com/django/django/pull/87 There is a pull request], but
the patch is attached.
--
Ticket URL: <https://code.djangoproject.com/ticket/17360>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
