Perhaps this would work, since you are passing the lgn/pswd in the clear.. why not send it as a GET param?
http://www.thisdomain.com/page.php?lg=login&pw=password Block all requests that don't come from known IP addresses with your cgi. Would a user cookie be out of bounds? The user could stop at a public page containing a <form> that would submit a POST with a security string You could send them a file named safeDirectory.html that would be stored on their hard drive, then they bookmark it, and it contains a <form> that would do the POST to your server using any browser. ------------------- Being inexperienced at this, I would be curious to see if any of the above would be a good solution. Certificates, etc are a mystery for me. Jim Ault Las Vegas On 1/30/09 7:12 PM, "Richard Gaskin" <[email protected]> wrote: > Bob Sneidar wrote: >> Just an FYI there are content filters that react to redirects as well. >> In this often cruel and unforgiving world it seems the use of >> redirects and proxies can wreak havoc with the things we use to >> protect ourselves. I am not sure what the solution is, but I can think >> of who to blame. ;-) > > Good reminder, Bob. Thanks. > > I'm not necessarily set on using redirects. Really, any method by which > I can protect a directory from most users while granting access to some > would work for me, provided that whatever means I use can pass the login > into in the URL. I'm even good with doing this in a CGI if only I could > figure out the trick to protecting the directory.... > > -- > Richard Gaskin _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
