[Placement] Invalid query parameter could lead to HTTP 500
Invalid query parameter could lead to HTTP 500, although
Placement used JSON Schema verification to check input query
params, but query like: GET allocation_candidates?limit=%88
will still lead to HTTP 500, as it failed to parse at webob
which is pre JSON Schema check.
Reviewed: https:/ /review. openstack. org/539408 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=ea006b13a7a d5229a3dcdbba0e 7aef438e873b6c
Committed: https:/
Submitter: Zuul
Branch: master
commit ea006b13a7ad522 9a3dcdbba0e7aef 438e873b6c
Author: Yikun Jiang <email address hidden>
Date: Wed Jan 31 10:50:46 2018 +0800
[Placement] Invalid query parameter could lead to HTTP 500
Invalid query parameter could lead to HTTP 500, although candidates? limit=% 88
Placement used JSON Schema verification to check input query
params, but query like: GET allocation_
will still lead to HTTP 500, as it failed to parse at webob
which is pre JSON Schema check.
Change-Id: Iba8d29cb442c61 0de53e70c81533a 8e1243d12dc
Partial-bug: #1746202