Zaqar wsgi transport doesn't have a default error handler

Bug #1493823 reported by Thomas Herve
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
zaqar
Fix Released
High
Thomas Herve

Bug Description

When some unexpected error happens, zaqar doesn't return anything to the caller, not even a valid http response. We should add a default error handler and return a 500.

Thomas Herve (therve)
Changed in zaqar:
assignee: nobody → Thomas Herve (therve)
Changed in zaqar:
importance: Undecided → High
status: New → Triaged
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to zaqar (master)

Fix proposed to branch: master
Review: https://review.openstack.org/221744

Changed in zaqar:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to zaqar (master)

Reviewed: https://review.openstack.org/221744
Committed: https://git.openstack.org/cgit/openstack/zaqar/commit/?id=c154d6b5b2d16734f70cf24ffbe9f6ea1ea03699
Submitter: Jenkins
Branch: master

commit c154d6b5b2d16734f70cf24ffbe9f6ea1ea03699
Author: Thomas Herve <email address hidden>
Date: Wed Sep 9 15:00:36 2015 +0200

    Add a global error handler for wsgi

    This adds a default error handler for wsgi transport so that unexpected
    exceptions return a responder to the caller, instead of just closing the
    connection.

    Change-Id: I9ad6c06d9922237f66110b3c045fc299ca385bbc
    Closes-Bug: #1493823

Changed in zaqar:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in zaqar:
milestone: none → liberty-rc1
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in zaqar:
milestone: liberty-rc1 → 1.0.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.