Creating order with oversized payload fails with 413 instead of 400
Bug #1211929 reported by
Melissa Kam
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Barbican |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Steps to Reproduce:
{
"secret": {
"name": "secretname",
"algorithm": "AES",
"bit_length": 256,
"cypher_type": "CBC",
"payload_
"payload_
"payload": [payload greater than 10,000 bytes]
}
}
Response:
413 Payload Too Large
{
"title": "The request returned a 413 Request Entity Too Large. This generally means that rate limiting or a quota threshold was breached.\n\nThe response body:\n%(body)s"
}
Expected Response:
400 Bad Request
{
"title": "Provided object does not match schema 'Order': 'payload' not allowed for secret generation"
}
Changed in cloudkeep: | |
milestone: | none → havana-3 |
To post a comment you must log in.
Verified as of 44fcce118d1d711 5c8dfbdc1629b29 cfb63c4027