Thanks Curt.
I have some follow up questions:
If I used non-anonymous authentication wouldn't they have to enter a second
username and password set up on the server?
Can you explain what you mean by streaming the files in? I like this one
because the files cannot be seen using the website url.
DB is not really an option at this point. There are 1000's of files, and
they will be updated regularily.
Thanks!!
"Curt_C [MVP]" wrote:
put them in a "non-anonymous authentication" directory.
Either that or move them outside the wwwroot path and stream them to the
clients after authentiction.
Or store them in a DB and pull them on demand after authentication.
--
Curt Christianson
Owner/Lead Developer, DF-Software
www.Darkfalz.com
"Jennifer Smith" <je******@nospam.com> wrote in message
news:40***************@nospam.com... Here is the situation:
My client has purchased 'software' - it really is just a series of html
documents. I need to ensure that these pages are protected and only
those who log in can view them.
I am building an asp/db based login front end to ensure that users have
paid for the system. I just do not know how to protect the files from
there because they are html. Converting them to asp is not an option.
Any ideas??
Thanks in advance for your time.