Successful delete operations return a 204 No Content "error"
Bug #486363 reported by
Duncan McGreggor
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| txAWS |
Fix Released
|
Medium
|
Duncan McGreggor | ||
Bug Description
Deleteing buckets and objects returns a (sensible) status (204 No Content) but this is reported as an error in txAWS, and that's not correct.
Related branches
lp:~oubiwann/txaws/486363-no-content-fix
- Duncan McGreggor: Approve
-
Diff: 2499 lines (+1095/-453)26 files modifiedLICENSE (+10/-5)
README (+6/-0)
bin/txaws-create-bucket (+42/-0)
bin/txaws-delete-bucket (+42/-0)
bin/txaws-delete-object (+46/-0)
bin/txaws-get-object (+46/-0)
bin/txaws-head-object (+47/-0)
bin/txaws-list-buckets (+43/-0)
bin/txaws-put-object (+56/-0)
txaws/client/base.py (+41/-0)
txaws/client/tests/test_client.py (+41/-2)
txaws/ec2/client.py (+70/-85)
txaws/ec2/exception.py (+4/-108)
txaws/ec2/tests/test_client.py (+132/-87)
txaws/ec2/tests/test_exception.py (+2/-129)
txaws/exception.py (+113/-0)
txaws/meta.py (+10/-0)
txaws/s3/client.py (+25/-7)
txaws/s3/exception.py (+21/-0)
txaws/s3/tests/test_exception.py (+62/-0)
txaws/script.py (+42/-0)
txaws/service.py (+12/-9)
txaws/testing/payload.py (+31/-19)
txaws/tests/test_exception.py (+114/-0)
txaws/tests/test_service.py (+7/-2)
txaws/util.py (+30/-0)
| Changed in txaws: | |
| importance: | Undecided → Medium |
| milestone: | none → 0.1 |
| summary: |
- Successfully deleting a bucket returns a 204 No Content "error" + Successful delete operations return a 204 No Content "error" |
| description: | updated |
| Changed in txaws: | |
| status: | New → In Progress |
| assignee: | nobody → Duncan McGreggor (oubiwann) |
| description: | updated |
Revision history for this message
| Duncan McGreggor (oubiwann) wrote | #1 |
Revision history for this message
| Duncan McGreggor (oubiwann) wrote | #2 |
| Changed in txaws: | |
| status: | In Progress → Fix Committed |
| Changed in txaws: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This has been fixed in the branch... submitting for review...