[WebDNA] Downloadable file protection

This WebDNA talk-list message is from

2011


It keeps the original formatting.
numero = 106332
interpreted = N
texte = Has anyone here thought through the process involved with creating a protections of some type for a doanoadable file? I need to sell access to PDF and mp4 files from my site, but obviously I don't want to use the real file name because someone will just share them. What I'm looking for is something like Amazon S3 that provides authentication and prevents file access. My thoughts are that someone could be authenticated, and then a raw download could be sent with an encoded file name, but the header needs to correctly identify the file type so the browser knows how to handle it. Currently when I sell eBooks direct from my website I copy them to a doanload directory and rename them as the user. That way if someone ever shares the file we know who did it. I'd be grateful if anyone has through through this and wants to share their ideas. I'm not looking for exact code, just to be pointed in the right directions. Thanks! -- Matthew A Perosi Computer Engineer Senior Web Developer SEO Analyst& Educator Psi Prime, Inc. 323 Union Blvd. Totowa, NJ 07512 Service: 973.413.8211 Training: 973.413.8214 Fax: 973.413.8217 http://www.psiprime.com Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Downloadable file protection (Jym Duane 2011)
  2. Re: [WebDNA] Downloadable file protection (Tom Duke 2011)
  3. Re: [WebDNA] Downloadable file protection (Jym Duane 2011)
  4. Re: [WebDNA] Downloadable file protection (Tom Duke 2011)
  5. Re: [WebDNA] Downloadable file protection (Stuart Tremain 2011)
  6. Re: [WebDNA] Downloadable file protection (Govinda 2011)
  7. [WebDNA] Downloadable file protection ("Psi Prime Inc, Matthew A Perosi " 2011)
Has anyone here thought through the process involved with creating a protections of some type for a doanoadable file? I need to sell access to PDF and mp4 files from my site, but obviously I don't want to use the real file name because someone will just share them. What I'm looking for is something like Amazon S3 that provides authentication and prevents file access. My thoughts are that someone could be authenticated, and then a raw download could be sent with an encoded file name, but the header needs to correctly identify the file type so the browser knows how to handle it. Currently when I sell eBooks direct from my website I copy them to a doanload directory and rename them as the user. That way if someone ever shares the file we know who did it. I'd be grateful if anyone has through through this and wants to share their ideas. I'm not looking for exact code, just to be pointed in the right directions. Thanks! -- Matthew A Perosi Computer Engineer Senior Web Developer SEO Analyst& Educator Psi Prime, Inc. 323 Union Blvd. Totowa, NJ 07512 Service: 973.413.8211 Training: 973.413.8214 Fax: 973.413.8217 http://www.psiprime.com "Psi Prime Inc, Matthew A Perosi "

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

[WebDNA] My SQL will not Connect (2020) WC on Linux question (2001) Emailer setup (1997) RE: NewCart+Search with one click ? (1997) 'does not contain' operator needed ... (1997) WebCat2final1 crashes (1997) Preserving file creation dates on [copyfile] (2007) small hairball -- stuck on [showif] for related db (1998) wc 2 pro users - sites, quotes wanted (1997) [WebDNA] WebDNA slow processing (2011) b12 cannot limit records returned and more. (1997) Problems getting parameters passed into email. (1997) Group Updates (1998) [OT] .php3 extension (2000) Duplicates (1998) [WebDNA] listfiles weirdness? (2018) test (2000) problem: mail changed (1997) Problem upgrading from 3.0.8 to 4.0 on MS Windoze 98 / PWS (2000) PCS Frames (1997)