openstack-api-site

Create container in OpenStack Object Storage API v1 Reference - API v1

Bug #1302248 reported by piousbox on 2014-04-03

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	openstack-api-site	Fix Released	Medium	Unassigned

on successful PUT /v1/<account>/<container>, the response length is 0, but the content-type header is required. Shouldn't it be optional?

-----------------------------------
Built: 2014-03-24T16:06:13 00:00
git SHA: b8d1fc7e6f8f0c113ad618c8ffad3caa4a945ff6
URL: http://docs.openstack.org/api/openstack-object-storage/1.0/content/PUT_createContainer_v1__account___container__storage_container_services.html
source File: file:/home/jenkins/workspace/object-api-tox-doc-publishdocs/openstack-object-storage-dev/ch_object-api-operations.xml
xml:id: PUT_createContainer_v1__account___container__storage_container_services

Tags:

Tom Fifield (fifieldt) on 2014-04-07

affects:

openstack-manuals → openstack-api-site

Revision history for this message

Anne Gentle (annegentle) wrote on 2014-06-13:

Yes, the Content-Type header is optional. Needs changing in the referenced document to look like http://developer.openstack.org/api-ref-objectstorage-v1.html#storage_container_services where it is correctly marked optional.

Changed in openstack-api-site:
status:	New → Confirmed
importance:	Undecided → Medium

Atsushi SAKAI (sakaia) on 2015-09-02

tags:

added: swift

Revision history for this message

Anne Gentle (annegentle) wrote on 2015-09-06:

This is fixed already in the deliverable we're still producing -- the http://docs.openstack.org/api/openstack-object-storage/1.0 is obsolete.

Changed in openstack-api-site:
assignee:	nobody → Suzanna Schulze (suzannaschulze)
assignee:	Suzanna Schulze (suzannaschulze) → nobody
status:	Confirmed → Fix Released

This report contains Public information

Everyone can see this information.

You are

Subscribing...

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