Re: run arbitrary wsgi application as Pylons controller - no form data available

[Ben Bangert]

On Aug 9, 2007, at 8:24 AM, Ian Bicking wrote:

Seems I found the problem with running wsgi application as Pylons
controller: posted form data not available in wsgi application trough
environ['wsgi.input']. This happens because at point, where wsgi
application called, request input stream was already readed ( when
PylonsBaseWSGIApp create WSGIRequest).
Possible fix is to check controller's class before call setup_app_env

an ancestor of WSGIController.

in PylonsBaseWSGIApp, and don't call this method, if controller is not

Yes; this is a problem where the form data gets put in
environ['paste.parsed_formvars'], but is lost from wsgi.input.  I
thought the values were lazily parsed -- that is, unless you access

might be something in Pylons that is looking at that.

pylons.request.POST (or .params) it won't consume wsgi.input. But there

easy_install -U Routes



HTH,
Ben

Routes, before 1.7 or so, would always check the form params causing parsing. Upgrade routes: To see if you had a prior version, upgrading should fix the parsing issue so that wsgi.input will be untouched.

smime.p7s
Description: S/MIME cryptographic signature