PriMoThemes — now s2Member® (official notice)
This is now a very OLD forum system. It's in READ-ONLY mode.
All community interaction now occurs at WP Sharks™. See: new forums @ WP Sharks™
* **(s2Member). Amazon® S3 bug fix.** s2Member has been updated to support all regions, and not just the `US Standard`. If you were getting errors in the previous release, related to Amazon® S3 storage locations being accessed improperly, this release of s2Member v110606 should resolve the issue for you. To put it simply, s2Member now connects to your S3 Bucket using `[bucket].s3.amazonaws.com`, instead of `s3.amazonaws.com/[bucket]`, making s2Member more compatible in this regard; and as suggested by this documentation. This also improves the User experience, since your Bucket name will appear in the host name of the download, instead of just `s3.amazonaws.com`. For further discussion, please check [this thread](http://www.primothemes.com/forums/viewtopic.php?f=4&t=10054).
<Error>
<Code>AccessDenied</Code>
<Message>Request has expired</Message>
<RequestId>9C88278B3B32DE86</RequestId>
<Expires>2011-06-10T05:03:40Z</Expires>
<HostId>
xZmgzlDVd7GDoHU+q7bt9Q/c9Z5B/zQ9CzyelSnCUfLMauzcPHMSXn9l0xl9hdTV
</HostId>
<ServerTime>2011-06-10T05:04:35Z</ServerTime>
</Error>
Changelog wrote:(s2Member) Compatibility. In cases where a site owner integrates Amazon® S3 file storage for protected File Downloads, with an invalid Bucket name which contains mixed caSe ( that's a no-no anyway ), s2Member will now convert the Amazon® S3 connection URL to s3.amazonaws.com/[BUCKET], instead of the default [bucket].s3.amazonaws.com. This is required for invalid Bucket names which use mixed caSe. The only way for Amazon® S3 communication to work with these invalid Bucket names, is with a sub-folder URL. See docs on Bucket names.
<Error>
<Code>AccessDenied</Code>
<Message>Access Denied</Message>
<RequestId>C02D810644E351C4</RequestId>
<HostId>
7ErUJHPHu5lee8BrX9FCbEAUMsFcmMBkbYb6e2hB6rSbJSYnNZNdPviSTvoia1t
</HostId>
</Error>
* **(s2Member) Compatibility.** In cases where a site owner integrates Amazon® S3 file storage for protected File Downloads, with an invalid Bucket name which contains mixed caSe ( that's a no-no anyway ), s2Member will now convert the Amazon® S3 connection URL to `s3.amazonaws.com/[BUCKET]`, instead of the default `[bucket].s3.amazonaws.com`. This is required for invalid Bucket names which use mixed caSe. The only way for Amazon® S3 communication to work with these invalid Bucket names, is with a sub-folder URL. See docs on [Bucket names](http://docs.amazonwebservices.com/AmazonS3/latest/dev/index.html?BucketRestrictions.html).
OK. In your case, you simply have a configuration problem.keywordcentrics wrote:Thanks for getting back with me so soon. I know it's a Saturday. I emailed the information you need.
Appreciated!
Gary
http://xxxxxx... .cloudfront.net/kcengineeringprt1.mp4
http://xxxxx... /?s2member_file_download=kcengineeringprt1.mp4
keywordcentrics wrote:I didn't know that 'Cloudfront' was bad to use.
I guess I was just looking for a way to distribute it,
as well as stream it.
Users browsing this forum: Bing [Bot] and 2 guests