On 2011-02-05 11:54, Roberto De Ioris wrote: >> PEP 3333 specifies that the python app "should" be able to call read() > > "should" is the key ;) > Indeed. It's only a recommendation. >> What do you think? Is this something uWSGI should do differently? Some >> python libraries seem to clash with the current behavior. >> >> > Which python library ? WebOb tries to read the whole input, i.e. input.read(), when you copy a Request object. Pyramid in turn copies a WebOb request object, so it's also affected (in some cases). I should probably send a bug report to WebOb about this. > By the way, > > --post-buffering <n> > > solves the "problem" (you will get the same result suggested by PEP3333) > > This is not the default as it will break feature like 'upload progress' > managed by the app itself Hmm... That doesn't work for me, for some reason. It still blocks. I think the documentation is a bit unclear here too. Will adding --post-buffering <n> only activate it for requests larger than <n> bytes? I suppose not, but what does --post-buffering-bufsize do then?
Thanks, Hampus Wessman _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
