1

Closed

wfastcgi.py should exit when an invalid handler is specified

description

When a user specifies an invalid WSGI_HANDLER in the web.config file, it will cause python.exe to hang since it doesn’t properly end the request for FastCGI. Can we improve this in the next version so that when an invalid WSGI_HANDLER is specified (e.g. a non-callable is passed in), we’ll gracefully fail the request with a 500 (and perhaps an error)? We also need to make sure that the python.exe process will be terminated as well (which should happen if we properly end the request with an error).
Closed Oct 3, 2013 at 7:18 PM by huguesv

comments