python-oops-wsgi's proxy start_response callback does not handle a third argument.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-oops-wsgi |
Invalid
|
Undecided
|
Unassigned |
Bug Description
According to the WSGI spec, the start_response callback should accept three arguments:
"""
The second parameter passed to the application object is a callable of the form start_response(
"""
This means that if a WSGI application tries to report an error to its container (rather than just erroring out completely), that error gets lost and replaced with "TypeError: oops_start_
Instead, I would expect oops-wsgi to publish an OOPS report based on exc_info and let the application display its error page.
wgrant pointed out to me that r9 fixes this bug.