Programming Amazon Web Services
Programming Amazon Web Services S3, EC2, SQS, FPS, and SimpleDB By James Murty
March 2008
Pages: 600


Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
Aws::s3 Library, version
tenasakai
post Aug 1 2009, 09:14 PM
Post #1


New Member
*

Group: Members
Posts: 7
Joined: 1-July 09
Member No.: 18,967



Hi,

On page 143 of the book, it is stated:
"You may experience problems using 0.4.0 of the AWS::S3 library..."

Would you tell us which version(s) don't have problems?

FYI: I am using aws-s3-0.6.2 and I emulated the usage of s3backup.rb from the bottom of page 142 and didn't experience anything disagreeable.

Regards,

Tena Sakai
Go to the top of the page
 
+Quote Post
JamesMurty
post Aug 2 2009, 05:40 PM
Post #2


Active Member
**

Group: Members
Posts: 20
Joined: 20-March 08
Member No.: 161



The problem with the AWS::S3 library referred to on page 143 (Content-Length Workaround) only affected users who interact with S3 via web proxies that are fussy about the PUT requests they relay. Namely, proxies that do not accept PUT requests without a Content-Length header.

In my book, I propose a workaround for the issue that causes AWS::S3 to include this header with Bucket PUT requests.

I just checked the latest code for AWS::S3 on GitHub and it looks like this problem remains. However, it will not affect you unless you are accessing S3 from behind a troublesome proxy. If it does affect you, the 1-line fix mentioned in the book should fix it.

Regards,
James

This post has been edited by JamesMurty: Aug 2 2009, 05:41 PM
Go to the top of the page
 
+Quote Post
tenasakai
post Aug 3 2009, 08:47 AM
Post #3


New Member
*

Group: Members
Posts: 7
Joined: 1-July 09
Member No.: 18,967



Many thanks, James.

Regards,
Tena Sakai

QUOTE (JamesMurty @ Aug 2 2009, 05:40 PM) *
The problem with the AWS::S3 library referred to on page 143 (Content-Length Workaround) only affected users who interact with S3 via web proxies that are fussy about the PUT requests they relay. Namely, proxies that do not accept PUT requests without a Content-Length header.

In my book, I propose a workaround for the issue that causes AWS::S3 to include this header with Bucket PUT requests.

I just checked the latest code for AWS::S3 on GitHub and it looks like this problem remains. However, it will not affect you unless you are accessing S3 from behind a troublesome proxy. If it does affect you, the 1-line fix mentioned in the book should fix it.

Regards,
James

Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 

RSS Lo-Fi Version Time is now: 9th February 2010 - 06:57 PM