echonest / remix

Echo Nest Remix: The Internet Synthesizer
http://echonest.github.com/remix
414 stars 90 forks source link

Invalid key in online demo #28

Closed fidergo-stephane-gourichon closed 10 years ago

fidergo-stephane-gourichon commented 10 years ago

Context

Visit http://echonest.github.io/remix/js/examples/graph and press "Upload MP3".

Expected

No error, showing some graph on data, etc.

Observed

With or without a file to upload it goes to URL https://s3.amazonaws.com/static.echonest.com with error

The AWS Access Key Id you provided does not exist in our records.

Thank you for your attention.

tkell commented 10 years ago

Hmmm. Just tried it and it worked for me. What sort of MP3 were you uploading?

Thanks! Thor

fidergo-stephane-gourichon commented 10 years ago

Hum, thanks for testing.

I tried with an old MP3 but the problem happens even without selecting a MP3, just pressing "upload".

Looking at the request details it looks like the string sent as a key is "YOUR_AWS_ACCESS_KEY".

If I deploy my own copy of the source code on my server, I understand I have to have my own AWS key, but the URL I mention above is a public demo site supposed to work with any vanilla borwser, right ?

Does it mean that the demo site happens to be now running with vanilla source code instead of a real Amazon key (assuming it had a real key in the past) ?

How do you have it work

How do you test ? Do you just go to the URL mentioned in the report using a vanilla browser as I did ?

Tech details

Obtained with Firefox integrated debug facility (Ctrl-Shift-C then network tab).

Request:

Host: s3.amazonaws.com User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x8664; rv:29.0) Gecko/20100101 Firefox/29.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,/_;q=0.8 Accept-Language: en-US,en;q=0.5 Accept-Encoding: gzip, deflate Referer: http://echonest.github.io/remix/js/examples/graph Connection: keep-alive Cache-Control: max-age=0

Content-Type: multipart/form-data; boundary=---------------------------82512145415075726641937536627 Content-Length: 1160

-----------------------------82512145415075726641937536627 Content-Disposition: form-data; name="key"

remix_audio/${filename} -----------------------------82512145415075726641937536627 Content-Disposition: form-data; name="AWSAccessKeyId"

YOUR_AWS_ACCESS_KEY -----------------------------82512145415075726641937536627 Content-Disposition: form-data; name="acl"

public-read -----------------------------82512145415075726641937536627 Content-Disposition: form-data; name="success_action_redirect"

YOUR_URL -----------------------------82512145415075726641937536627 Content-Disposition: form-data; name="policy"

YOUR_POLICY_DOCUMENT_BASE64_ENCODED -----------------------------82512145415075726641937536627 Content-Disposition: form-data; name="signature"

YOUR_CALCULATED_SIGNATURE -----------------------------82512145415075726641937536627 Content-Disposition: form-data; name="Content-Type"

audio/mpeg -----------------------------82512145415075726641937536627 Content-Disposition: form-data; name="file"; filename="" Content-Type: application/octet-stream

-----------------------------82512145415075726641937536627--

Response:

<Error>
<Code>
InvalidAccessKeyId</Code>
<Message>
The AWS Access Key Id you provided does not exist in our records.</Message>
<RequestId>
4183F2B4C6596C1E</RequestId>
<HostId>
m2WyLeuzlWm0YngsEYkDO0FUf5V+Et/B7k8inEdvQhseUzCzeLUFSTT0KymcwccQ</HostId>
<AWSAccessKeyId>
YOUR_AWS_ACCESS_KEY</AWSAccessKeyId>
</Error>
tkell commented 10 years ago

Hmmm. I am using Chrome, which may be the problem.

I know that Firefox now supports Web Audio, but that page says "window.webkitAudioContext", which will, I think break Firefox. Do you get results in Chrome? If so, I will find time to fix Web Audio things for Firefox, but probably not until next week.

Thanks! Thor

tkell commented 10 years ago

Update: I've done a bunch of digging, and yeah, FireFox needs to use "window.AudioContext". I will update the various demo files with this soon.

Thanks! Thor

tkell commented 10 years ago

Fixed: I've updated the various examples to pick AudioContext or webkitAudioContext, as needed.

fidergo-stephane-gourichon commented 10 years ago

Tested, I no longer see the error. If observed again, will reopen (I guess it'll never happen). On other problem, will open a new bug. Thanks.