Home/ Questions/Q 7706285
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-01T00:05:14+00:00

I’m running into a problem with large POST data (>16384 bytes) when using Django

  • 0

I’m running into a problem with large POST data (>16384 bytes) when using Django 1.2.3, PyISAPIe v1.1.0-rc4, and IIS 7.5.

For example, when submitting approx. 60kB of form data using POST, the following happens:

  • The first 16kB block of POST data are correct
  • The next 16kB block is a repeat of the first block
  • The next 16kB is another repeat of the first block
  • The rest (<16kB) is correct again

The interesting part is that when using content-type="multipart/form-data", it works fine.

Using this information I tracked down the likely location of the bug to WSGIRequest._get_raw_post_data in django\core\handlers\wsgi.py, which handles the content-type="multipart/form-data" separately from the default (no content-type) case.

Both cases read from self.environ['wsgi.input'], which is set to the PyISAPIe object. The difference is that the default case seems to read in chunks of 16kB, whereas the multipart handler seems to read in chunks of just under 2GB.

I don’t know enough about C and the Python interface for C to dig in further, but I’m guessing the bug is somewhere in PyISAPIe in the ReadClient function in ReadWrite.cpp.

My current workaround is to add content-type="multipart/form-data" to forms that may product more than 16kB of data.

Has anybody run into this as well, or does anybody know how to determine if the bug is in fact in PyISAPIe?

Thank you!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    PyISAPIe author here.

    This was fixed in revision 184 in the repository but not in the downloadable release, as discussed on the mailing list.

    It addressed a previously documented bug that apparently hasn’t received much attention because many users are checking out the source rather than downloading the package. Or, that’s my best guess anyway; regardless, I plan to provide a downloadable version of the fixed code.

    Thanks for bringing this to my attention so I can be reminded to keep this project’s releases in a functioning state.

    • 0