On Fri, Oct 22, 2010 at 2:34 PM, Adrien <[email protected]> wrote: > Hi, > > I found a workaround by creating a wsgi middleware that stores > wsgi.input before it gets altered by one of the Pylons components. > It works for me but does not solve the real problem. > > For what I understand when a http client sends a post request that > pretends to be x-www-form-encoded but in fact is octet/stream one > component encodes environ['wsgi.input'] in a way that can't be > reversed. >
This occurs when you are trying to acces request.POST AFAIK. You should avoid this and use if request.method == 'POST' instead Don't know if it's the real issue though. > Cheers, > Adrien > > On Oct 21, 10:40 am, Adrien <[email protected]> wrote: >> I realize that tcp dumps are almost unreadable on google groups >> webpages without a fixed font. Here is a web-readable version of the >> http dumps: >> >> http://pylonshq.com/pasties/eb5a1799ff9786f8cf643069fb08552a >> >> I hope that someone can help me. I suspect a Pylons bug somewhere. >> Cheers, >> > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/pylons-discuss?hl=en. > > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
