No answers here, but an identical question with a different purpose: To allow the use of a webware-based login form to affect non-webware-served files, such as static .htaccess protected files or a legacy cgi-bin app, but to avoid the browser dialog box (since users have already 'authenticated').
Any thoughts are appreciated, - Luke ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
