Bad query params on /v2/events can throw a 500
Bug #1423634 reported by
jasonamyers
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceilometer |
Fix Released
|
Undecided
|
Chris Dent | ||
WSME |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I made a GET request with to the following:
/v2/events?
This was due to not understanding how to properly call the API; however, it resulted in a 500 instead of the expected 400
decoded that URL string contains [{"field": "event_type", "op": "eq", "type": "string", "value": "cookies_
Changed in ceilometer: | |
assignee: | nobody → Mehdi Abaakouk (sileht) |
status: | Incomplete → In Progress |
Changed in wsme: | |
milestone: | none → 0.8.0 |
status: | Fix Committed → Fix Released |
Changed in ceilometer: | |
assignee: | Mehdi Abaakouk (sileht) → Chris Dent (chdent) |
Changed in ceilometer: | |
milestone: | none → liberty-3 |
status: | Fix Committed → Fix Released |
Changed in ceilometer: | |
milestone: | liberty-3 → 5.0.0 |
To post a comment you must log in.
You can also do this by misforming the data sent with the get request. For example if you send just a list of query params not in the query object it also occurs.
Example: '["field": "bad_field", "op": "eq", "type": "string", "value": "cookies_ chocolate. chip"]' returns a 500 when the input is bad and should be '{"q": ["field": "bad_field", "op": "eq", "type": "string", "value": "cookies_ chocolate. chip"]} '