|
|
(2 intermediate revisions by one other user not shown) |
Line 34: |
Line 34: |
| | Request with zero value for limit || 400 || | | | Request with zero value for limit || 400 || |
| |- | | |- |
− | | Request with non existing value of marker || 204 || What does Swift do? | + | | Request with non existing value of marker || 200 or 204 || A marker always "exists" in the sense that we can always perform a range comparison with it. In other words, if you pass 'g' for the marker, Marconi will return all queue's whose names sort after 'g', lexicographically. If you pass a marker that sorts after all existing queues, you will receive "204 No Content" in response. |
| |- | | |- |
| | Request with non boolean value for metadata || 400 || lowercase true/false? | | | Request with non boolean value for metadata || 400 || lowercase true/false? |
Scenario |
HTTP Response Code |
Notes
|
Success |
200 |
|
Request a non existing queue |
404 |
|
URL has invalid param (something other than limit,marker,metadata) |
200 |
Extra params are ignored.
|
Request with negative value for limit |
400 |
|
Request with zero value for limit |
400 |
|
Request with non existing value of marker |
200 or 204 |
A marker always "exists" in the sense that we can always perform a range comparison with it. In other words, if you pass 'g' for the marker, Marconi will return all queue's whose names sort after 'g', lexicographically. If you pass a marker that sorts after all existing queues, you will receive "204 No Content" in response.
|
Request with non boolean value for metadata |
400 |
lowercase true/false?
|
Header has Accept != "application/json" |
406 |
|
Header has missing fields |
400 |
|
Header has invalid auth token |
401 |
|
Scenario |
HTTP Response Code
|
Success (query matched 1 or more messages) |
200
|
Success (query has no match) |
204
|
Request message from a non existing queue |
404
|
Request message with invalid param (something other than marker,limit,echo) |
200
|
Request message with limit >100 |
400
|
Request message with limit <= 0 |
400
|
Request message with non existing marker |
204
|
Request message with non boolean value for echo |
400
|
Header has Accept != "application/json" |
406
|
Header has missing fields |
400
|
Header has invalid auth token |
401
|
Scenario |
HTTP Response Code
|
Success |
201
|
Post multiple messages in a single request , all of them fails |
503
|
Post multiple messages in a single request , few of them succeed |
201 (with "partial": true) [2]
|
Post message to a non existing queue |
404
|
Post > 100 messages with a single request |
400
|
Post with request body > 4KB |
400
|
Post with invalid JSON request body |
400
|
Post with non-JSON request body |
400
|
Post with non-JSON message |
400
|
Post with TTL < 60 |
400
|
Post with TTL > 1209600 |
400
|
Post with non int value of TTL |
400
|
Post with negative value of TTL |
400
|
Post without TTL in request body |
400
|
Post without "body" in request body |
400
|
Post with no request body |
400
|
Post with messages encapsulated in multiple arrays |
400
|
Header has Accept != "application/json" |
406
|
Header has missing fields |
400
|
Header has invalid auth token |
401
|
URL has invalid params |
200
|
Scenario |
HTTP Response Code
|
Success |
200
|
Success (empty queue with no messages to claim) |
204
|
Claim message from a non existing queue |
204
|
Claim message with invalid value for limit (nonint, <=0) |
400
|
Claim message with limit >100) |
400
|
Claim message with no request body |
400
|
Claim message with no TTL field |
400
|
Claim message with invalid TTL value (non int, <=0) |
400
|
Claim message with invalid JSON |
400
|
Claim message with non JSON request body |
400
|
Claim message with invalid auth token |
401
|
Claim message with missing header fields |
400
|
Header has Accept != "application/json" |
406
|
Scenario |
HTTP Response Code
|
Success |
204
|
Update Expired Claim |
404
|
Update Claim on a non existing queue |
404
|
Update a non existing claim |
404
|
Update claim with invalid URL params |
200
|
Update claim with content-type != application/json-patch |
406
|
Update claim with no request body |
400
|
Update claim with invalid JSON in request body |
400
|
Update claim with non JSON request body |
400
|
Update Claim with invalid auth token |
401
|
Update Claim with missing header fields |
400
|