To discover whether your Object Storage system supports this feature, see . Alternatively, check with your service provider. You can use your Object Storage account to create a static website. This mode is normally only active for anonymous requests, which provide no authentication token. To use it with authenticated requests, set the header X-Web-Mode to TRUE on the request. To determine whether the static website feature is enabled, contact your service provider. For example: Your publicly readable containers are checked for two headers, X-Container-Meta-Web-Index and X-Container-Meta-Web-Error. (The latter header is discussed below, under Set error pages for static website.) With X-Container-Meta-Web-Index, you determine the index file (or default page served, such as index.html) displays your website. When someone initially enters your site, they don't have to specify the index file; index.html file displays automatically. If you create sub-directories for your site by creating pseudo-directories in your container, the index page displays by default for each sub-directory. If your pseudo-directory does not have a file with the same name as your index file, visits to the sub-directory return a 404 error. You also have the option of displaying a list of files in your pseudo-directory instead of a web page. You do this by setting the X-Container-Meta-Web-Listings header to TRUE. You may add style to your file listing by setting X-Container-Meta-Web-Listings-CSS: to a style sheet (for example, lists.css).

Make the container publicly readable. Once the container is publicly readable, you may access your objects directly, but you must set the index file to browse the main site URL and its sub-directories. $ swift post -r '.r:*' container Set the index file. In this case, index.html is the default file displayed when the site displays. $ swift post -m 'web-index:index.html' container Turn on file listing. If you do not set the index file, list the objects in the container. Instructions on styling the list with the CSS follow. $ swift post -m 'web-listings: true' container Style the file listing.

You can create and set custom error pages for visitors to your website; currently, only 401 (Unauthorized) and 404 (Not Found) errors are supported. To do this, set the metadata header, X-Container-Meta-Web-Error. Error pages are served with the <status> code pre-pended to the name of the error page you set. For instance, if you set X-Container-Meta-Web-Error to error.html, 401 errors will display the page 401error.html. Similarly, 404 errors will display 404error.html. You must have both of these pages created in your container when you set the X-Container-Meta-Web-Error metadata, or your site will display generic error pages. Set the X-Container-Meta-Web-Error metadata once for your entire static website. Any 2nn response indicates success.