Hi, I tried to post earlier, but the link to my post did not go to my post!
Anyway, now I have a more precise question.
I am able to use the standalone player to play publicly accessible MP3 files in one of my S3 buckets, for example:
Failed to load resource: the server responded with a status of 403 (Forbidden) (test2.mp3)
An example of a signed URL is the following:
This URL will not work–I’ve changed it, plus it has expired–but I provide it as an example of what these signed URLS are supposed to look like.
I think that the standalone player may be changing the URL a bit. Signed URLs have to be used exactly as they are, letter for letter. The signature is a cryptographic hash of certain parts of the URL along with my Amazon Web Services secret key, so if the URL is changed at all, it won’t work.
This could include, for example, changing the representation of a space from + to %20.
Or any other changes to the encoding of the URL.
BTW, I do have a crossdomain.xml file (publicly accessible) in my s3 bucket, although the standalone player doesn’t seem to care if I have it or not.
To recap: I *can* play publicly accessible mp3s from my S3 bucket in the standalone player.
I cannot play a protected mp3 that I have a signed URL for.
I *can* use this URL to download or play the mp3 in any other player.
So although I see a “Forbidden” error, I know that permissions are not the issue–I think that the standalone player is somehow changing the URL.
Is there a way to see exactly what URL it is trying to load? If I install the debug flash player and enable logging, will that do it?
Thanks in advance,
- The topic ‘[Plugin: Audio Player] trouble with S3 signed URLs in standalone player’ is closed to new replies.