Comment 3 for bug 1210623

Debugging this. It looks like eventlet.wsgi's default behavior is to show traceback to the client on any unhandled exceptions in WSGI apps.

There are two things that need to happen I think then.

1) We need to handle HeatException in the WSGI middleware so it never bubbles up to eventlet, but so that the message is displayed to the user as intended.
2) We need to apply the server's debug flag to eventlet.wsgi.Server, as passing debug=False to eventlet.wsgi.Server's constructor will suppress any unhandled tracebacks being sent to the user (they will just get a blank 500 error). Indescriminate Exception's are already logged, so deployers can still have a chance at reporting deep unhandled exceptions without exposing tracebacks to users.

Part 1 is this bug. Part 2 is bug #1222008