Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#17259 closed Bug (needsinfo)

error in http post data parser

Reported by: bayazee@… Owned by: nobody
Component: HTTP handling Version:
Severity: Normal 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 (last modified by Karen Tracey) 

Traceback (most recent call last):

  File "/usr/local/lib/python2.6/site-packages/django/core/handlers/base.py", line 95, in get_response
    response = middleware_method(request, callback, callback_args, callback_kwargs)

  File "/usr/local/lib/python2.6/site-packages/django/middleware/csrf.py", line 164, in process_view
    request_csrf_token = request.POST.get('csrfmiddlewaretoken', "")

  File "/usr/local/lib/python2.6/site-packages/django/core/handlers/wsgi.py", line 171, in _get_post
    self._load_post_and_files()

  File "/usr/local/lib/python2.6/site-packages/django/core/handlers/wsgi.py", line 137, in _load_post_and_files
    self._post, self._files = self.parse_file_upload(self.META, self.environ['wsgi.input'])

  File "/usr/local/lib/python2.6/site-packages/django/http/__init__.py", line 123, in parse_file_upload
    parser = MultiPartParser(META, post_data, self.upload_handlers, self.encoding)

  File "/usr/local/lib/python2.6/site-packages/django/http/multipartparser.py", line 80, in __init__
    raise MultiPartParserError("Invalid content length: %r" % content_length)

MultiPartParserError: Invalid content length: 0

Change History (2)

comment:1 by Russell Keith-Magee, 13 years ago

Resolution: → needsinfo
Status: new → closed

A stack trace isn't a bug report.

If you care to provide instructions detailing how you generated this stack trace, feel free to reopen.

comment:2 by Karen Tracey, 13 years ago

Description: modified (diff)

Also if you search trac (https://code.djangoproject.com/search?q=MultiPartParserError+%22Invalid+content+length%22&noquickjump=1&ticket=on) you will find at least one similar report that may help you in isolating the cause of this problem. When it has been reported before the cause was found to be outside of Django itself.

Note: See TracTickets for help on using tickets.
Back to Top