Re: Script to change .htaccess password?
Doug MacEachern (dougm@osf.org)
Tue, 2 Jan 1996 19:39:32 -0500
[snip]
>Umm, how about a module called
>
> HTTPD::UserAdmin
>
>with subclasses as needed?
Sounds good.
>Ideally comp.infosystems.www.authoring.cgi but it looks hard to 'discuss'
>design issues there. The libwww-perl@ics.uci.edu might be happy to cover
>this even though it's not using the libwww-perl library (I've CC'd this
>to them for comment). Perhaps there are some other mailing lists that I
>don't know about. Comp.lang.perl.misc is always a good bet for perl issues.
It seems users on both the libwww-perl and CGI lists would have equal
interest, any objections to future disussion taking place on both lists?
>
>In the meantime I've added HTTPD::UserAdmin and HTTPD:Access to the Module
>List, let me know if you want any changes:
>
>HTTPD::
>::UserAdmin adpO Management of server user and group files DOUGM +
>::Access cdp Management of server access control files DOUGM +
Looks good. Do you want to include ::BasicAuth and ::Conf ? Those are both
further along than ::Access.
I'm confused now on where BasicAuth would fit in. Currently it's
functionality consists of:
- decode and parse the Authorization: header value
- look up the password in a text, DBM, or any database accessible via the
DBI switch.
- attempt to verify the password
- send a response with 401 status, WWW-Authenticate header, etc.
Seems like a mix between HTTP/HTTPD.
I'd like to keep that functionality in one place, along with keeping it free
from MIME::Base64 and HTTP::(Message/Response/Status/etc), as sort of a
"light-weight" version, but they certainly can all be used together. But,
I'm open to suggestions.
-Doug
>
>Tim.
>
>