[
https://issues.apache.org/jira/browse/JCLOUDS-680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14104860#comment-14104860
]
Zack Shoylev commented on JCLOUDS-680:
--------------------------------------
In https://github.com/jclouds/jclouds-labs-openstack/pull/130
I could expand it to not escape any of these headers. My question is whether
the approach makes sense.
> OpenStack Swift: Improve Object update behavior
> -----------------------------------------------
>
> Key: JCLOUDS-680
> URL: https://issues.apache.org/jira/browse/JCLOUDS-680
> Project: jclouds
> Issue Type: Improvement
> Components: jclouds-labs-openstack
> Reporter: Jeremy Daggett
> Assignee: Jeremy Daggett
> Labels: api, openstack-swift
> Fix For: 2.0.0
>
>
> The Swift
> [documentation|http://docs.openstack.org/api/openstack-object-storage/1.0/content/POST_updateObjectMeta__v1__account___container___object__storage_object_services.html#POST_updateObjectMeta__v1__account___container___object__storage_object_services-Request]
> notes that the following Object metadata may also be updated:
> * Content-Type
> * Content-Encoding
> * Content-Disposition
> * X-Delete-At
> The {{openstack-swift}} API will need to reflect these Object updates.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
