DELETE /v2/images/<image_id> should return 204 No Content

Bug #995224 reported by Eoghan Glynn on 2012-05-05
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Eoghan Glynn

Bug Description

DELETE /v2/images/<image_id> currently returns 200 OK, whereas both the API v2 design and normal RESTful idiom would suggest that a 204 No Content status would be more appropriate.

Eoghan Glynn (eglynn) on 2012-05-05
Changed in glance:
assignee: nobody → Eoghan Glynn (eglynn)
milestone: none → folsom-1
importance: Undecided → Low
status: New → In Progress

Submitter: Jenkins
Branch: master

commit f184a386271b8305023c90186244a370727b2535
Author: Eoghan Glynn <email address hidden>
Date: Sat May 5 19:59:05 2012 +0100

    Return 204 from DELETE /v2/images/<image_id>

    Fix bug 995224

    The v2 API design and normal RESTful idiom would suggest that a
    204 No Content status is more appropriate than 200 OK.

    Change-Id: Ic5ae3ffa22eafdec0f780d16cceb8ce45c84c854

Changed in glance:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2012-05-23
Changed in glance:
status: Fix Committed → Fix Released
Mark McLoughlin (markmc) wrote :

Eoghan's take on this for backporting:

  Not suitable for backporting as patch applies to v2 API, not supported on stable/essex

Thierry Carrez (ttx) on 2012-09-27
Changed in glance:
milestone: folsom-1 → 2012.2
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers