Hi again,
I was thinking about stuffing the htsearch program into a module
suitable for Apache. This should allow for some more security
in configuring ht://Dig for different secured areas in intranet
or internet webs. However, I'm not too familiar with Apache
module writing (might change in the near future) and would like
to know if there's anyone out here who already got some experience.
It would also be good to discuss the features and configurability
of mod_htsearch (sound like a proper name for it, no?) in advance.
My ideas up to now:
Module Name: mod_htsearch
Content Handlers: application/x-htdig-query
Configuration Phase: Create Directory Config,
Merge Directory Configs
Request Phase: none
Module Directives: htsearch_Active (bool)
htsearch_AllowConfigOverride (bool)
htsearch_AllowExcludeOverride (bool)
htsearch_AllowRestrictOverride (bool)
htsearch_config (string)
htsearch_exclude (string)
htsearch_format (string)
htsearch_keywords (string)
htsearch_matchesperpage (positive)
htsearch_method (string)
htsearch_restrict (string)
htsearch_sort (string)
The default behaviour of the module should be identical to the
CGI version of htsearch. Module directives correspond to their
CGI version parameter equivalents and can be overridden by them
unless forbidden.
Wrappers cannot benefit much from this module however, since they
must call it via a virtual HTTP request which might slow things
down significantly (some benchmarking required).
Any comments?
Torsten
--
InWise - Wirtschaftlich-Wissenschaftlicher Internet Service GmbH
Waldhofstra�e 14 Tel: +49-4101-403605
D-25474 Ellerbek Fax: +49-4101-403606
E-Mail: [EMAIL PROTECTED] Internet: http://www.inwise.de
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.
