[9891] in www-talk@info.cern.ch
Re: authentication
daemon@ATHENA.MIT.EDU (Luke Gonze)
Thu Mar 28 12:28:00 1996
Date: Thu, 28 Mar 1996 11:31:25 -0500 (EST)
From: Luke Gonze <applix!luke@uunet.uu.net>
To: applix!uunet!w3.org!www-talk@uunet.uu.net
In-Reply-To: <199603281132.GAA14700@www19.w3.org>
Resent-From: www-talk@w3.org
although cgi scripts don't get the www-authenticate header, you can get this
information by hooking into the netscape server api. Overall I've
found nsapi pretty usable. Granted, getting married to netscape may be
a tragic fate. But you can handle the authentication yourself, and you
can arrange to pass authentication data to cgi scripts that need to be
informed.
>The real problem is that the CGI script doesn't get invoked > until *after*
the username and password are validated. If you want the CGI > script to do
the validation, you're out of luck.
>Your real problem is a DIFFERENT problem than not being able to get
the authentication headers. If you want your CGI script to do
authentication, you need to disable the server authentication. You'll
then have to get the authentication data from the server somehow.
--- Luke Gonze --- luke@applix.com ---
--- Software Engineer, Applix Espresso project ---
