Feature #1511

Merge new Openstack Object Store changes (September 2011)

Added by Antony Chazapis almost 13 years ago. Updated over 11 years ago.

Status:Closed Start date:10/18/2011
Priority:Medium Due date:
Assignee:Antony Chazapis % Done:

0%

Category:Pithos Spent time: -
Target version:-

Description

A new version of the OOS API has been released (dated 22/9/2011). Read and discuss any changes needed.

http://docs.openstack.org/api/openstack-object-storage/1.0/os-objectstorage-devguide-1.0.pdf

os-objectstorage-devguide-1.0.pdf (214.8 kB) Antony Chazapis, 11/29/2011 11:45 am

Associated revisions

Revision a53ef24e
Added by Antony Chazapis over 12 years ago

Process incoming headers. URL-decode if necessary.

Refs #1511

Revision a53ef24e
Added by Antony Chazapis over 12 years ago

Process incoming headers. URL-decode if necessary.

Refs #1511

Revision 9fefc052
Added by Antony Chazapis over 12 years ago

Restrict header count and size. URL-encode/decode specific headers that may contain unicode characters.

Refs #1511

Revision 9fefc052
Added by Antony Chazapis over 12 years ago

Restrict header count and size. URL-encode/decode specific headers that may contain unicode characters.

Refs #1511

Revision 88283e9e
Added by Antony Chazapis over 12 years ago

Use URL-encoding/decoding for all headers.

Refs #1511

Revision 88283e9e
Added by Antony Chazapis over 12 years ago

Use URL-encoding/decoding for all headers.

Refs #1511

History

#1 Updated by Antony Chazapis almost 13 years ago

Most of the spec is already implemented.

Points that must be addressed:
  • Check for maximum number of HTTP headers and maximum length.
  • Container GET should return 204 if the container is empty or does not exist.
  • Directory markers do not end in '/'.
  • Metadata can have a maximum of 128 chars for name and 256 for value. Unicode chars are allowed, but it is recommended that they are URL-encoded.
  • Added CORS headers (section 3.3.3).

Implementing URL-encoded metadata handling should also fix #1534.

#2 Updated by Antony Chazapis over 12 years ago

  • Target version changed from 0.8.1 to 0.8.0

#3 Updated by Antony Chazapis over 12 years ago

  • Assignee changed from Antony Chazapis to Giorgos Verigakis

#4 Updated by Antony Chazapis over 12 years ago

  • Assignee changed from Giorgos Verigakis to Antony Chazapis

#5 Updated by Antony Chazapis over 12 years ago

  • Target version changed from 0.8.0 to 0.8.1

#6 Updated by Antony Chazapis over 12 years ago

The developer guide has been attached.

#7 Updated by Antony Chazapis over 12 years ago

  • Subject changed from Merge new Openstack Object Store changes to Merge new Openstack Object Store changes (September 2011)

#8 Updated by Antony Chazapis over 12 years ago

  • Status changed from New to Assigned

Header limits and encoding have been implemented.

The container response of 204 if the container does not exist may be a guide error, so I suggest we wait for a future version to see, or contact OOS API developers. Containers are created with specific actions, so how can client software know whether to create a container if the response for non-existent is the same as existent (but empty)? What should an object create action in a non-existent container result to?

CORS headers will be implemented in #1717.

#9 Updated by Antony Chazapis over 12 years ago

  • Status changed from Assigned to Closed

#10 Updated by Vangelis Koukis over 11 years ago

  • Tracker changed from Support to Feature
  • Project changed from Pithos to Synnefo
  • Target version deleted (0.8.1)

#11 Updated by Vangelis Koukis over 11 years ago

  • Category set to Pithos

Also available in: Atom PDF