Release: Amazon S3 on 2006-03-27

Overly restrictive ISO8601 Timestamp parsing

Relaxed ISO8601 format requirements for the Timestamp parameter in SOAP so that queries that use sub-millisecond precision formats will not be rejected. Due to differences in how libraries drop this precision, .NET SOAP users are free to send timestamps with a high precision format, but should avoid setting those high precision digits (i.e., .NET timestamps should look like this on the wire: 2006-03-27T10:46:42.1230000-08:00, which would be canonicalized into the canonical string as 2006-03-27T18:46:42.123Z). See the provided .NET SOAP library for an example of how to do this.

Confusion over header canonicalization in signing

Upon authentication failure, the error message will now include the canonicalized string that the user should have signed.

Sample code fixes

• Fixed minor error in the PHP demo that would cause the page to fail to render in some browsers.
• Fixed putACL and putBucketACL in the Java REST example library. Added a test program.
• Fixed documentation for the Perl REST example library for OS X users.
• Fixed documentation in the S3 Curl example as to how to create a bucket.
• Fix for C# SOAP example library so that time precision is restricted to milliseconds.
• Fix for .NET 1.x C# SOAP (requires source tweak).
• Internationalization update for dates in C# SOAP and Java REST libraries.
• Updated signature encoding to UTF-8 in C# SOAP and REST libraries.
• Updated dependency documentation for the Java SOAP example library.
• Added key-management library to more securely handle AWSSecretAccessKeys.
• Fixed metadata whitespace issue in Java, Perl, Python and Ruby REST libraries

Documentation fixes

Updated SOAP authentication section to describe how to deal with high-precision Timestamp formats.

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

S3 does not support the HTTP 100-Continue status as described in RFC 2616, section 8.2.3.

ETags

S3 ETags calculate an MD5 hash on 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

S3 allows SOAP authentication to be performed over non-SSL connections. SOAP authentication should only be accepted over SSL.