It's hard to provide useful help when we see only part of the story, and that story changes over time (e.g. the line of code you identify in the dpaste posting as being where the error occurs does not match the line of code seen in the first traceback you posted).
Since you are dealing with a 3rd party system that is calling you, your method should be coded defensively in order to make sure it doesn't blow up if called incorrectly. Your method assumes that the caller is always going to call it properly and supply every bit of post data you are looking for. One possibility here is that the 3rd party is misbehaving and that is what is causing the error. Another possibility is that something your code is doing is causing the 3rd party to misbehave and sometimes POST with no data to your view. What's not really a possibility (I would be astonished to hear this resolution) is that something in Django is taking a single client-generated POST request and turning it into two: one with the client-provided post data and one without. That's just not likely to be what's happening here. I do recall people posting similar problems where their single page fetch was somehow morphing into multiple calls to their view. One way this can happen is if there is something (e.g. embedded image with incorrect src spec) in the HTML that is returned that would cause a client to fetch the same page again. I notice you are not using RequestContexts when you render the response, so if there is anything in your templates that relies on variables set by context processors, that might be causing a problem. Karen -- http://tracey.org/kmt/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
