ed4f3c4db9
Point to WADL files that generate the API Reference
page so that the method descriptions and request
and response parameters are consistent between
these two docs:
http://api.openstack.org/api-ref-objectstorage.html
(API Reference page for Object Storage)
http://docs.openstack.org/api/openstack-object-storage/1.0/
(API Reference (or spec) for Object Storage)
Add descriptions of ACLs, FormPOST, TempURLs,
StaticWeb, Bulk Upload, Bulk Delete, the OPTIONS operation
(though this is implicit in CORS support)
Validate all code examples
Remove duplication.
Co-Author: Donagh McCabe
Closes-Bug: #1187119
Closes-Bug: #1214139
Closes-Bug: #1074198
Partial-Bug: #1255770
Change-Id: I94054b046a94260ba8825bdb42439adfcaf9fdce
author: diane fleming
21 lines
1.0 KiB
XML
21 lines
1.0 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<section xmlns="http://docbook.org/ns/docbook"
|
|
xmlns:xi="http://www.w3.org/2001/XInclude"
|
|
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
|
|
xml:id="file-compression">
|
|
<title>Use Content-Encoding metadata</title>
|
|
<para>When you create an object or update its metadata, you can
|
|
optionally set the <literal>Content-Encoding</literal>
|
|
metadata. This metadata enables you to indicate that the
|
|
object content is compressed without losing the identity of
|
|
the underlying media type (<literal>Content-Type</literal>) of
|
|
the file, such as a video.</para>
|
|
<example>
|
|
<title>Content-Encoding header request: HTTP</title>
|
|
<para>This example assigns an attachment type to the
|
|
<literal>Content-Encoding</literal> header that
|
|
indicates how the file is downloaded:</para>
|
|
<programlisting><xi:include href="samples/content-encoding-header-req.txt" parse="text"/></programlisting>
|
|
</example>
|
|
</section>
|