Cloudfiles - standard Metadata headers not recognized
29 views
Skip to first unread message
Marcus Rowell
unread,
May 1, 2013, 3:41:14 AM5/1/13
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to cybe...@googlegroups.com
My understanding is that some standard HTTP-specific header names such as "content-type", "content-disposition" etc should not have "X-Object-Meta-" added to the header elements when using Cloudfiles.
With 4.3 and 4.3.1, "content-disposition" headers are having "X-Object-Meta-" added to the header on editing and existing values, which were created in 4.2.1 and are visible in that version are not being displayed in the Metadata tab of the info window.
This was tested on Mac OS X 10.8.3 and 10.7.5 with existing bookmarks to Cloudfiles, as well as new connections using the Rackspace US.cyberduckprofile and a new Swift connection.
Is this expected behaviour?
Thanks,
Marcus.
David Kocher
unread,
May 2, 2013, 12:42:54 PM5/2/13
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to cybe...@googlegroups.com
Yes, currently only metadata can be edited but no standard HTTP headers. Please open an enhancement request at http://trac.cyberduck.ch/newticket and we will see if the Cloudfiles/Openstack API does support this.