diff --git a/api-ref/src/wadls/object-api/src/common.ent b/api-ref/src/wadls/object-api/src/common.ent
index ff03b7e87..49d2faebf 100644
--- a/api-ref/src/wadls/object-api/src/common.ent
+++ b/api-ref/src/wadls/object-api/src/common.ent
@@ -584,6 +584,25 @@ include them in this header.
string.
'>
+
+
+
+ Enables object creation that omits existing user metadata.
+
+
+ If set to True, the © request creates an object
+ without existing user metadata.
+
+
+ Default value is False.
+
+
+
+'>
diff --git a/api-ref/src/wadls/object-api/src/os-object-api-1.0.wadl b/api-ref/src/wadls/object-api/src/os-object-api-1.0.wadl
index 46880ca3e..99eb622ec 100644
--- a/api-ref/src/wadls/object-api/src/os-object-api-1.0.wadl
+++ b/api-ref/src/wadls/object-api/src/os-object-api-1.0.wadl
@@ -478,10 +478,12 @@ Date: Fri, 17 Jan 2014 16:09:56 GMT
Creates a container.
- You do not need to check if a container already
- exists before issuing a &PUT; operation because the
- operation is idempotent: It creates a container or
- updates an existing container, as appropriate.
+
+ You do not need to check whether a container already exists
+ before issuing a &PUT; operation because the operation is
+ idempotent: It creates a container or updates an existing
+ container, as appropriate.
+
Example requests and responses:
Create a container with no metadata:
curl -i $publicURL/steven -X PUT -H
@@ -779,15 +781,18 @@ Date: Thu, 16 Jan 2014 18:55:00 GMT
- Creates a new object with specified
- data content and metadata, or replaces an existing
- object with specified data content and
- metadata.
- The &PUT; operation always creates a new object. If
- you use this operation on an existing object, you
- replace the existing object and metadata rather than
- modifying the object. Consequently, this operation
- returns a 201 Created status code.
+
+ Creates an object with specified data content and metadata, or
+ replaces an existing object with specified data content and
+ metadata.
+
+
+ The &PUT; operation always creates an object. If you use this
+ operation on an existing object, you replace the existing
+ object and metadata rather than modifying the object.
+ Consequently, this operation returns a 201
+ Created status code.
+
If you use this operation to copy a manifest object,
the new object is a normal object and not a copy of
the manifest. Instead it is a concatenation of all the
@@ -859,33 +864,43 @@ Date: Fri, 17 Jan 2014 17:28:35 GMT
- Copies an object to another object
- in the object store.
- You can copy an object to a new object with the same
- name. Copying to the same name is an alternative to
- using &POST; to add metadata to an object. With
- &POST;, you must specify all the metadata. With
- ©, you can add additional metadata to the
- object.
- Alternatively, you can use &PUT; with the
- X-Copy-From request header to
- accomplish the same operation as the © object
- operation.
- The &PUT; operation always creates a new object. If
- you use this operation on an existing object, you
- replace the existing object and metadata rather than
- modifying the object. Consequently, this operation
- returns a 201 Created success
- node.
- If you use this operation to copy a manifest object,
- the new object is a normal object and not a copy of
- the manifest. Instead it is a concatenation of all the
- segment objects. This means that you cannot copy
- objects larger than 5 GB in size. All metadata is
- preserved during the object copy. If you specify
- metadata on the request to copy the object, either
- &PUT; or ©, the metadata overwrites any
- conflicting keys on the target (new) object.
+
+ Copies an object to another object in the object store.
+
+
+ You can copy an object to a new object with the same name.
+ Copying to the same name is an alternative to using &POST; to
+ add metadata to an object. With &POST;, you must specify all
+ the metadata. With ©, you can add additional metadata to
+ the object.
+
+
+ With ©, you can set the X-Fresh-Metadata
+ header to True to copy the object without any
+ existing metadata.
+
+
+ Alternatively, you can use &PUT; with the X-Copy-From
+ request header to accomplish the same operation as
+ the © object operation.
+
+
+ The &PUT; operation always creates an object. If you use this
+ operation on an existing object, you replace the existing
+ object and metadata rather than modifying the object.
+ Consequently, this operation returns a 201
+ Created success node.
+
+
+ If you use this operation to copy a manifest object, the new
+ object is a normal object and not a copy of the manifest.
+ Instead it is a concatenation of all the segment objects. This
+ means that you cannot copy objects larger than 5 GB in size.
+ All metadata is preserved during the object copy. If you
+ specify metadata on the request to copy the object, either
+ &PUT; or ©, the metadata overwrites any conflicting keys
+ on the target (new) object.
+
Example requests and responses:
Copy the goodbye object
@@ -935,7 +950,8 @@ Date: Fri, 17 Jan 2014 18:22:57 GMT
&destination-requestHeader; &content-type-requestHeader;
&content-encoding-requestHeader;
&content-disposition-requestHeader;
- &object-meta-name-requestHeader;
+ &object-meta-name-requestHeader;
+ &fresh-metadata-requestHeader;
&content-length-responseHeader-OP;
&copied-from-last-modified-responseHeader;
&copied-from-responseHeader;