Re: Download question

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: The Clansman (no_at_pls.com)
Date: 08/07/04 

Date: Sat, 7 Aug 2004 11:58:29 -0300

the problem is that is I use WriteFile, the file will be loaded into the
memory, and if I send chunks of data, the user won't be able to navigate
other pages.... the user will need to wait the download to complete.....

thanks anyway

"Chandra Sekhar" <Chandra.Shekhar@am.joneslanglasalle.com> wrote in message
news:Ob8zwxIfEHA.708@TK2MSFTNGP09.phx.gbl...
> My suggestion would be to binary read and render to client such that the
> users will never get to see the file url.
>
> Sekhar.
>
>
> "The Clansman" <no@pls.com> wrote in message
> news:ufK8ScIfEHA.720@TK2MSFTNGP11.phx.gbl...
> > thanks,
> > but I'm using a hosting service, the web server is not a server that I
> have
> > access....
> >
> > is it possible to configure this at the hosting server?
> >
> > thanks
> >
> > "Craig Deelsnyder" <cdeelsny@no_spam_4_meyahoo.com> wrote in message
> > news:opsccmo2w475dg5d@cowboy...
> > > On Sat, 7 Aug 2004 00:48:42 -0300, The Clansman <no@pls.com> wrote:
> > >
> > > > Hi,
> > > > I am developing a site for a company and this site will have files
> > > > available
> > > > for the customers to download, but only the customers loged in will
be
> > > > able
> > > > to download these files and the files availables for each customer
> will
> > > > depend on the type of the customer.
> > > >
> > > > so how can I prevent a user from downloading a file by typing the
full
> > > > url
> > > > (example, http://www.company.com/file.exe)
> > > >
> > > > if the user type the url of the file, I want the user to be
redirected
> > to
> > > > the login page.
> > > >
> > > > **some files are larger than 50MB
> > > >
> > > > Thanks
> > > >
> > > >
> > >
> > > The easiest way is to map all of the files' extensions to the aspnet
dll
> > > in IIS. So go into your web app in IIS and copy the dll setting for
> .aspx
> > > to each of the other ones (.exe, pdf, etc.). This will cause requests
> to
> > > be passed thru the aspnet process (which will then just serve up the
> > > file), enabling you to protect them via Forms Authentication.
> > >
> > > Note you'll want to test this a little, to make sure of no problems.
> > > Performance impact should be minimal as well.
> > >
> > > --
> > > Craig Deelsnyder
> > > Microsoft MVP - ASP/ASP.NET
> >
> >
>
>

Quantcast