Unicode chars in invalid database user passwords leads to 500 error codes instead of 400
Bug #1241877 reported by
Tim Simpson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Confirmed
|
Low
|
Unassigned |
Bug Description
If the call to create a database user is made with an invalid password that also contains unicode, such as the pound sign ("£"), the status code returned is 500 rather than 400.
This is because internally, a BadRequest exception is constructed by taking another exception and wrapping it in "str()". Because unicode errors aren't allowed this ends up leading to a different raised exception, thus the 500 error.
Changed in trove: | |
importance: | Undecided → Low |
Changed in trove: | |
assignee: | Tim Simpson (tim-simpson) → nobody |
status: | In Progress → Confirmed |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/52726
Review: https:/