there has been a discussion in this group recently about URL re-writing (see URL rewriting...anybody done this? and replies)
That is a possibility, using a combination of URL Re-Writing PHP Sessions/Cookies And the Location: header So all requests go back to the index, then you decide from the index.php page if they have to be redirected, or if they are already logged in, or if they dont have permission That might work -- Luke "Scott Taylor" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > > Is there no other way to protect your (non PHP) files than through > authentication? I've been trying to set up a system that will protect > files. Those trying to access the files would only be able to do so > after entering their email address. So I set up a form that submits the > email to my database. But then the problem is: how to access the > files? I could just use http://username:password/test.com/test.jpg > method, but then what would be the point of trying to protect the files > in the first place? It would simply be the same as with holding the > link to begin with. So is there an alternative to using http basic > authentication to protect files? Or is there a simple way to > authenticate the pages themselves without using something like Manuel > Lemos' "PHP HTTP class"? > > Best Regards, > > Scott Taylor -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
