Comments on: Generate expiring urls for Amazon S3 via a Wordpress Plugin

By: S3 Protection

S3 Protection — Thu, 15 Oct 2009 08:33:26 +0000

Another option to consider is S3FlowShield. It is a commercial plugin that does what is described in this post and more. The developer is continually adding features and is very responsive to support requests and questions.

http://www.s3flowshield.com

Wes

By: Ola

Ola — Wed, 08 Jul 2009 10:29:11 +0000

I’m sorry but i don’t know why it doesn’t work for you guys. It works fine for me ..

I really do not have any time to fix this but would love if some skilled PHP developer could make a new and improved version of this.

By: WongWay

WongWay — Wed, 08 Jul 2009 08:16:51 +0000

I am looking for a solution to deliver content and avoid hotlinking to S3. I was really hoping this is working but it is not for me. Has anyone been successful or found other solutions that don’t cost developer time and money?

By: swattewrodo

swattewrodo — Wed, 20 May 2009 21:11:34 +0000

Wonderful site. hope to come back again soon,,

By: RaiulBaztepo

RaiulBaztepo — Sat, 28 Mar 2009 21:41:42 +0000

Hello!
Very Interesting post! Thank you for such interesting resource!
PS: Sorry for my bad english, I’v just started to learn this language
See you!
Your, Raiul Baztepo

By: ecz

ecz — Tue, 24 Mar 2009 09:27:44 +0000

How can this script even work?
You just sign the simple request “GET\n\n\n{$expires}\n/{$bucket}/{$resource}”
But when you click on a link in e.g. FireFox the GET request will have lots of other information like Host, User-Agent, Accept-* etc.
The signed request will not be near the same as the actual request sent.

Has anyone got it working with private files?

By: Ola

Ola — Wed, 04 Mar 2009 21:30:45 +0000

Hmm .. i guess i have to take a look at that. I think it is because i use custom urls. Will test it without custom url and see if i get the same error later.

By: jason

jason — Wed, 04 Mar 2009 20:11:05 +0000

im getting the same error as mark s….

SignatureDoesNotMatch

−

The request signature we calculated does not match the signature you provided. Check your key and signing method.

−

By: Mark S. Meritt

Mark S. Meritt — Fri, 23 Jan 2009 19:16:03 +0000

Thanks for helping out, whenever your can

I quickly realized that just putting in the bucket name alone where your code asks for it was not enough for a proper URL, so I put the whole root address. For a file called test.txt in a bucket called theoffhandband I put in the following code in my post:

[S3 bucket=theoffhandband.s3.amazonaws.com text=Test]test.txt[/S3]

There’s nothing wrong with the URL. I temporarily set the file to be Readable by everyone, and I was able to access it no problem with http://theoffhandband.s3.amazonaws.com/test.txt in my browser, and then when I set the permissions back, it went Access Denied again.

So it appears there’s something wrong with the query-string-authentication URL only, and in particular according to that error something wrong with the calculation of the signature.

Thanks again for your help!

By: Ola

Ola — Fri, 23 Jan 2009 18:15:39 +0000

Hmm, don’t know really. What URL did you use on the bucket attribute? I use my dns names and it works fine for me. I maybe can have a look on it tommorow and see what i can find.

I’m drinking beer right now and is going to Thailand on Sunday, but will have a quick look tommorow!