request.content_type is not set to None for form_encoded data

Issue #46 open
theatilla
created an issue

The documentation shows how to use request.content_type to detect whether the data is available in the django QueryDicts - POST/PUT or in request.data according to the reqyest.content_type.

While it should be set to None, for most form submissions there is a content-type set - application/x-www-form-urlencoded, which results into request.content_type not being set to None.

Attached is a patch that takes care of setting the value to None correctly.

Comments (9)

  1. Anonymous

    I also ran into this issue today and came to supply a patch but it appears someone has already beat me to it. :)

  2. Log in to comment