Successful delete operations return a 204 No Content "error"

Bug #486363 reported by Duncan McGreggor
6
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

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 :

This has been fixed in the branch... submitting for review...

Revision history for this message
Duncan McGreggor (oubiwann) wrote :

  Merged 486363-no-content-fix [r=lifeless] [f=486363]

  This change fixes the problem of 204 HTTP responses being raised as an error.

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 report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.