Check if a request is passing more attributes for complex objects than
those defined in the API. WSME did not care if some unknown attribute
was passed to an API with a complex type, only checking the required
attributes. This is fixed raising a ValueError if more attributes are
given than expected, resulting in an HTTP response with a 400 status.
This helps check the validity of requests, which would otherwise
unexpectedly work with (partially) invalid data.
Reviewed: https:/ /review. openstack. org/182761 /git.openstack. org/cgit/ stackforge/ wsme/commit/ ?id=6461c1b8a1d cb8820eeb32bbfb e8e3f22b3fa7ce
Committed: https:/
Submitter: Jenkins
Branch: master
commit 6461c1b8a1dcb88 20eeb32bbfbe8e3 f22b3fa7ce
Author: Stéphane Bisinger <email address hidden>
Date: Wed May 13 19:08:56 2015 +0200
Complex types should check unexpected attributes
Check if a request is passing more attributes for complex objects than
those defined in the API. WSME did not care if some unknown attribute
was passed to an API with a complex type, only checking the required
attributes. This is fixed raising a ValueError if more attributes are
given than expected, resulting in an HTTP response with a 400 status.
This helps check the validity of requests, which would otherwise
unexpectedly work with (partially) invalid data.
Closes-Bug: #1277571 dc8dca21a1ccdb1 26110dae62e
Change-Id: Idf720a1c3fac8b