There should be documentation that cautions about using request.raw_post_data and request.POST together

[lie.1296@…]

Currently, if you're accessing request.raw_post_data, then request.POST will become empty; there should be a note in the docs about that and telling that if you need to access both, then you should access request.POST first then request.raw_post_data.

Either that, or this bug should be fixed and it should be safe to read request.raw_post_data and request.POST in any order.

[Aymeric Augustin]

I'm sorry, but I'm unable to confirm this bug. Could you provide some evidence that it exists?

---

There are several test cases in the test suite that guarantee that it's possible to read request.POST after accessing request.raw_post_data:

https://code.djangoproject.com/browser/django/trunk/tests/regressiontests/requests/tests.py#L279

---

I attempted to reproduce the issue anyway.

I wrote this view:

from django.http import HttpResponse
from django.views.decorators.csrf import csrf_exempt

@csrf_exempt
def post_data(request):
    raw_post_data = request.raw_post_data
    post_data = request.POST
    return HttpResponse('%(raw_post_data)r\n%(post_data)r\n' % locals(), content_type='text/plain')

Here is the result:

% curl --data foo=bar http://localhost:8000/                                                                                                                                       ~
'foo=bar'
<QueryDict: {u'foo': [u'bar']}>

[lie.1296@…]

This issue exists in django-1.3, sorry for not noticing that this is already fixed in #15679.