2013-01-04 11:25:20 |
Unmesh Gurjar |
description |
Branch: master
Steps to repro:
1. Create a volume using the following POST body:
{
"volume": {
"display_name": "vol-001",
"display_description": "Another volume.",
"size": 1,
"metadata": {"ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss": "value1"}
}
}
2. Observe the API response.
Expected Behavior:
API should return a 413 RequestEntityTooLarge.
Actual Result:
API returns a 200 Ok, however, truncates the (large) metadata. |
Branch: master
Steps to repro:
1. Create a volume using the following POST body (containing a key which exceeds the database limit of 255 chars):
{
"volume": {
"display_name": "vol-001",
"display_description": "Another volume.",
"size": 1,
"metadata": {"ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss": "value1"}
}
}
2. Observe the API response.
Expected Behavior:
API should return a 413 RequestEntityTooLarge.
Actual Result:
API returns a 200 Ok, however, truncates the (large) metadata.
NOTE: similar behavior on defining metadata containing 0 sized key/value. |
|