Release: Amazon S3 on 2006-06-14

Release Notes>Release: Amazon S3 on 2006 06 14
Virtual hosting of buckets, hierarchical listing of keys, andUnicode fixes.

Details

Submitted By: Craig@AWS
Created On: June 13, 2006 11:00 PM GMT
Last Updated: June 15, 2006 12:49 AM GMT

Release Date: 2006-06-14
Latest WSDL/API Version: 2006-03-01 (updated)

New Features

Feature Description
Virtual hosting of buckets for anonymous, non-SSL, REST requests
Using the Virtual Hosting feature, you can now address a bucket in a REST API call using the HTTP Host header. Because of the way Amazon S3 interprets the Host header, most buckets are now automatically accessible (for anonymous, non-SSL requests) at http://[bucketname].s3.amazonaws.com. Furthermore, by naming your bucket after your registered domain name and by making that name a DNS alias for Amazon S3, you can completely customize the URL of your Amazon S3 resources, for example: http://my.bucketname.com/

Virtual hosting allows you to publish to the 'root directory' of your bucket's virtual server, which may address the issue raised by the Flash, cross-domain file forum thread.

See the new Virtual Hosting Buckets section of the documentation for more details.

(Previous versions of Amazon S3 incorrectly ignored the HTTP Host header. Applications that depend on this undocumented behavior must be updated to set the Host header correctly. Because Amazon S3 determines the bucket name from Host when present, the most likely symptom of this problem is to receive an unexpected NoSuchBucket error result code.)
New "delimiter" parameter  enables hierarchical listing of keys
Groups of keys that share a common prefix terminated by a special delimiter can now be rolled-up by that prefix for the purposes of listing. This allows applications to browse their keys hierarchically, much like how you would navigate through directories in a filesystem.

For example, if you had a bucket that contained the following keys (named with embedded slash delimiters to simulate directories)
  • photos/2006/index.html
  • photos/2006/January/img0001.jpg
  • ...
  • photos/2006/January/img0999.jpg
  • photos/2006/February/img1000.jpg
  • ...
A list query with Prefix="photos/2006/" and Delimiter="/" would return the keys and "subdirectories" at the photos/2006 level (index.html, January, February, ...) but would not include any of the .jpg keys at deeper levels.

This feature addresses the many requests to enable queries for keys by their structure (directory structure possible? for example).

See the new Listing Keys section of the documentation for details.
Content-Encoding HTTP header now configurable
Addresses the issue raised by this forum thread. All reasonable HTTP entity headers are now configurable.

Resolved Issues

Issue Description
Unicode keys appear corrupted in List response
Fixes the problem described in this forum thread. Keys containing unicode characters were not stored correctly prior to this update -- they will only appear correctly in list once re-put.
Documentation fixes
Improved discussion of buckets and listing keys.

Known Issues

Issue Description
Latent buckets Sometimes after you delete a bucket, the operation to list all your buckets will continue returning the bucket you deleted, even though it no longer exists.
100-Continue
The HTTP 100-Continue reply sent by S3 (as described in RFC 2616, section 8.2.3.) is unconditional, and therefore not very useful.
ETags
S3 ETags are currently derived from a hash of the object data. According to section 13.3.3 of RFC 2616, this is a weak reference. To be a strong reference, S3 would also have to consider metadata and other headers in the ETag.
SOAP SSL authentication
SOAP authentication should only be accepted over SSL but S3 allows SOAP authentication to be performed over non-SSL connections.
Uploads between 2 GB and 4 GB in size fail
A load balancer bug causes the connection to close whenever an upload request with content-length between 2 GB and 4 GB is received. Amazon is engaged with the load balancer vendor, has identified the issue, and is in the process of resolving the issue.
©2014, Amazon Web Services, Inc. or its affiliates. All rights reserved.