1 / 13
Apr 2011

Are there any tutorials floating around for Amazon S3 or using Online File Folder from Godaddy for bigger download files? I have tried both with e-junkie and cannot get either to work.

  • created

    Apr '11
  • last reply

    Dec '11
  • 12

    replies

  • 1.8k

    views

  • 6

    users

  • 5

    links

Every time I try to download through e-junkie I only get a binary/octet-stream file?

Well, I figured out that the online file folder is a no-go because you have to add an email every time. S3 probably didn't work because I didn't make it public. If it is public, doesn't that mean anyone can find it and download it freely? Because if so, it defeats the purpose. This is the reason I quit using mediafire last year. People were downloading my files for free and I couldn't prevent it. So I am just afraid that the S3 is the same. I just made it public and will shoot you a free link shortly.

I just sent you a file from Vendera Publishing for Extreme Scream. This is hosted on S3. Now that I have made it public, it does the exact same thing as it did with godaddy. I am in a real pickle as I have to get this fixed this weekend. Any advice you have I'd appreciate. Cannot store them on Squarespace anymore. Cannot use Godaddy apparently and Yousendit doesnt work half the time.

I'm no expert on Amazon S3 file security but I don't know how someone would determine the full URL for your files in order to access them without paying, particularly the "bucket" name part of the URL. See also...



3http://www.e-junkie.com/ej/tips.downloads.security.htm3



I haven't tried it, but Amazon S3 has a feature (ACL setting) that allows you to restrict access to particular users (ie, E-Junkie in this case) by specifying their ID or email address. Dunno that it's necessary. Perhaps E-Junkie folks can clarify.



I use Cloudberry S3 Explorer (pro version) to access Amazon S3. It makes it very easy to upload and manage files and settings. There are other similar programs out there as well.



1http://cloudberrylab.com/?page=cloudberry-explorer-amazon-s31



Not sure if it's related to your problem but I had problems when uploading .ogg files. They wouldn't play. Turns out the "Content-Type" was being set to "binary/octet-stream" instead of "audio/ogg". To fix it with Cloudberry, I right-clicked on the uploaded .ogg file, selected "Set HTTP Headers" and changed the Content-Type to "audio/ogg" and it worked after that.



http://supergeekery.com/geekblog/comments/whyisnt_ogg_video_playing_in_firefox_from_amazon_s3



Other than that .ogg problem, Amazon S3 has been working fine for me.

WNWI haven't tried it, but Amazon S3 has a feature (ACL setting) that allows you to restrict access to particular users (ie, E-Junkie in this case) by specifying their ID or email address. Dunno that it's necessary. Perhaps E-Junkie folks can clarify.





We won't be accessing files stored on Amazon S3 with any ID or email related login but all of our connections will come from the e-junkie.com domain. I believe Amazon can limit access to the files based on that information but you'd have to check their documentation for the exact means of doing so.



But it's not -necessary- to do something like that. Buyers will have no way to see any given file's original location because we serve the download from our own Amazon S3 cache. The buyer never gets any connection to the original location.

Hey E-junkie Monster. I thought I had it all worked out and I know you were able to download the program earlier, but I've changed my links to other products, but here is an email I keep getting from e-junkie:



--------------------------------------------------------------

Notification sent to Vendera Publishing

--------------------------------------------------------------



This is a notification that the remote download link provided by you for A Lecture with Elizabeth Sabine is not accessible and user(venderaj@msn.com) was served the file from our cache for transaction ID j-lk4j873f8ad66ca.

That indicates the Remote Product File URL you have configured in that product's settings failed to respond when we contacted it, so we simply served a copy we retained of the last file downloaded for that product. This help page section explains more about how our Remotely Hosted Downloads feature works, to give you a clearer idea of what's going on there:

http://www.e-junkie.com/ej/help.file-downloads.htm#remote



If you're getting that notification for every download link issued for that product, there may be a problem with the URL itself. To test it, copy that URL out of the product's settings, and paste it directly into your browser's address bar to see if that will start a download.



If you only get that notification once for a product, but subsequent links issued for the same product did not also generate the notification, then there was probably just a temporary connectivity glitch that prevented our server from being able to contact your file hosting server at that moment, which has since cleared up.

4 months later

In order to download from godaddy, you have to go into the online ftp manager and individually mark each file you want to have downloadable, then click the permissions button and make sure "web visible" is checked. Then click ok. Your files should now be downloadable.

2 months later
E-JunkieMonster
WNWI haven't tried it, but Amazon S3 has a feature (ACL setting) that allows you to restrict access to particular users (ie, E-Junkie in this case) by specifying their ID or email address. Dunno that it's necessary. Perhaps E-Junkie folks can clarify.





We won't be accessing files stored on Amazon S3 with any ID or email related login but all of our connections will come from the e-junkie.com domain. I believe Amazon can limit access to the files based on that information but you'd have to check their documentation for the exact means of doing so.



But it's not -necessary- to do something like that. Buyers will have no way to see any given file's original location because we serve the download from our own Amazon S3 cache. The buyer never gets any connection to the original location.





Thank you for the above. I'm using S3 as well... The files I have on S3 have to public in order for e-junkie to have access, correct? For some reason this bothers me given that I'm selling downloads. I saw the tip recommending vague file names which I have done. I also saw in the above post that specific links and detailed file locations are not provided to my customers, protecting the public file location. Thanks for any clarification and/or validation. Want to keep the system as tight and controlled yet as practical as possible. Thanks again.

Your files on S3 should be "public" only in the sense that they can be accessed without restriction IF the exact URL to each file is known, although those URLs are never exposed for the public to discover, and E-junkie buyers would never know nor access your remote file URLs directly.



It's rather like having an unlisted phone number; anyone who already knows your number can call you, but nobody else has any way of finding your number, or even knowing that you have a phone at all, if you don't tell them -- in this analogy, you would be giving your number only to us, and we don't share it with anybody else.



You may be interested in this help page subsection which explains how our Remotely Rosted Download feature works to cloak your remote file URLs and enforce your products' link-expiration settings:

2http://www.e-junkie.com/ej/help.file-downloads.htm#remote2

E-junkieGuruYour files on S3 should be "public" only in the sense that they can be accessed without restriction IF the exact URL to each file is known, although those URLs are never exposed for the public to discover, and E-junkie buyers would never know nor access your remote file URLs directly.



It's rather like having an unlisted phone number; anyone who already knows your number can call you, but nobody else has any way of finding your number, or even knowing that you have a phone at all, if you don't tell them -- in this analogy, you would be giving your number only to us, and we don't share it with anybody else.



You may be interested in this help page subsection which explains how our Remotely Rosted Download feature works to cloak your remote file URLs and enforce your products' link-expiration settings:

http://www.e-junkie.com/ej/help.file-downloads.htm#remote





Thank you :slight_smile: Exactly what I needed to know and feeling very content with the process, security, etc.