Release: Amazon S3 on 2008-12-31

Release Notes>Amazon S3>Release: Amazon S3 on 2008 12 31
This release of Amazon S3 introduces the Requester Pays Bucket, which enables the bucket owner to share the cost of data download and request fees with the requester.

Details

Submitted By: GeorgeNickels@AWS
Release Date: December 31, 2008 12:00 AM GMT
Latest Version: 2006-03-01
Latest WSDL: 2006-03-01
Created On: December 31, 2008 10:52 PM GMT
Last Updated: December 31, 2008 11:10 PM GMT

These release notes provide a summary of all New Features, Resolved Issues, and Known Issues in this version of the Amazon Simple Storage Service. For changes made in previous versions, go to hhttp://developer.amazonwebservices.com/connect/kbcategory.jspa?categoryID=49.

New Features

The following table describes the new features found in this release.

Feature
Description
Date Introduced
New Feature: Requester Pays bucket A bucket configured as a Requester Pays bucket charges requesters for data transfer and request fees when they download content from the bucket. The bucket owner still pays for the data storage fee. Two new elements support this new feature: RequestPaymentConfiguration and Payer.
12/31/2008
New Resources Two new operations, PUT requestPayment and GET requestPayment, support the new Requester Pays bucket configuration.
12/31/2008
New error The new error code, MissingRequestBodyError, occurs when the user sends an empty XML document as a request when Amazon S3 expects a request body. The error message is, "Request body is empty."
12/31/2008

 

Resolved Issues

There are no resolved issues in this release.

 

Known Issues

The following table describes irregular behavior seen in this release of Amazon S3.

Issue Description Impact

Browser might override encoding

POST forms must be UTF-8 encoded. If a user’s browser overrides the encoding, this might cause some characters to become scrambled and result in the uploaded data being corrupted.

 

Configuring HTTP headers using SOAP

With the exception of the Content-Type header, you cannot add HTTP headers to objects using the SOAP API.

 
ETag

Amazon 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, Amazon 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 Amazon S3 allows SOAP authentication to be performed over non-SSL connections.

 

Use of Amazon S3's BitTorrent interface from Amazon EC2 results in data transfer charges

While regular data transfer between Amazon S3 and Amazon EC2 is free, there is a known issue with the Amazon S3 BitTorrent seeder that results in data transfer charges when accessed from Amazon EC2. The Amazon Web Services team is aware of this issue and will work to address it. In the interim, please be advised that using the Amazon S3 BitTorrent interface from Amazon EC2 will result in data transfer charges.

.

Related Documents

©2014, Amazon Web Services, Inc. or its affiliates. All rights reserved.