On Mon, 20 May 2002, Harrell, Roger wrote:
> Is there a way to have a configuration file specified by domain rather than
> by the form variable being necessary. The reason is this. I've got several
No, not directly. However, it shouldn't be too hard to whip up a
"wrapper" for htsearch that sets the config variable based on the
domain. The CGI environment variable SERVER_NAME contains exactly that. If
you set up a directory for each domain's config files, you can do
something like this:
#!/bin/sh
CONFIG_DIR=/path/to/$SERVER_NAME/config /path/to/real/htsearch ${@+"$@"}
> know if there was a way to get htdig to use a certain config file if the
> query comes from domain1.com and a different one from domain2.com
If you're willing to do coding, you can also edit htsearch/htsearch.cc and
insert the appropriate logic to pick up the right config file.
--
-Geoff Hutchison
Williams Students Online
http://wso.williams.edu/
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
To unsubscribe, send a message to <[EMAIL PROTECTED]> with a
subject of unsubscribe
FAQ: http://htdig.sourceforge.net/FAQ.html
