Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
qpid-java-broker-9.0.0
-
None
Description
When POSTing an ACL rule with unknown attributes to the Qpid HTTP management API, the server responds with HTTP 422, Unprocessable Entity. This is somewhat OK, however, I think maybe a 400 Bad Request would be more appropriate.
But after the post, the broker is somehow left in a bad internal state, as the returned Json is incomplete and unparseable.
Example POST in aclRequest.json
Qpid log from the incident qpidErrorLog.txt
Returned Json from subsequent GET resultingAcl.json