admin amazon appear avoid browser browsers current customers don downloading error exact expect experiencing failed figured file files folder followup general happening help hosted hosting issue later names numbers path produce respond rule run seller server similar spaces started stick suggestions testing try url urls video

We've recently started hosting our video files at Amazon S3 instead of with e-junkie. Most of the files appear to work fine, but we're experiencing some inconsistencies. About 1 out of 3 video files (all hosted in the exact same way on S3) produce this error for our customers:

"This file is served directly by the seller. At this moment seller's server has failed to respond. Please try again later."

I saw this discussion about a similar issue: http://www.e-junkie.com/bb/topic/239 and the suggestions were to:

NatashaSenPlease check the following:

1. Try the link (which you have entered in E-junkie admin) in a browser and see if it works.
2. Make sure you don't have an .htaccess file blocking us in your remote folder where you have the files stored.
3. Make sure that the link to the file you entered in E-junkie admin is to a regular website and not to file hosting service as we can't read files from those links.
4. If that all is fine, ping our server from your server. If you are unable to reach our server from yours, it means there is an issue in the backbone somewhere which is beyond our control.

What's strange is that *all* the S3 URLs work in browsers, but a subset of the same URLs don't work when run through the e-junkie admin. I could understand if all the URLs worked the same away, but it's 3 of 9 (in our current testing) that are having an issue.

All the files in question have the exact same permissions and file naming conventions on S3. Do you have any ideas about why this may be happening? Any help is appreciated.

Nevermind. We figured it out. Here's what we discovered...

You CANNOT have spaces in Bucket names on Amazon S3. If you do, the URL will work in a browser for downloading, but will not work in e-junkie.

Changing Bucket names can be accomplished with http://www.bucketexplorer.com/.

Aha, thanks for the followup tip!

As a general rule, it's best to avoid using spaces in any folder path or file name that you'd expect to use in a URL, and just stick to using only letters, numbers, dashes-and_underscores.