According to Jim Cole: > On Saturday, October 19, 2002, at 01:43 PM, Karsten Werner wrote: > > Thanks to IP forwarding on the router the server can be accessed via > > FQDN from the internet. > > What we would like to do is: using htdig to index all the docs and > > manpages, HOWTOs, etc. on this machine and make them search and > > readable > >> from the internet. I managed to index these files locally > > (http://localhost/), and I can access www.mydomain.org/search and I > > can even search and find, but results refer to localhost and so cannot > > be displayed. > > You might want to take a look at the search_rewrite_rules attribute. > This allows you to rewrite the URL's in search results. > > http://www.htdig.org/attrs.html#search_rewrite_rules
Which, I will add, is only in version 3.1.6. You can also do this with url_part_aliases, as described in http://www.htdig.org/FAQ.html#q4.17 > > htsearch, but I can only find htdig.conf in my /etc/htdig directory. > > (I am running Debian woody 2.2.20 and installed htdig via dselect). > > Though I am not familiar with this particular distribution, > /etc/htdig.conf is most likely the file you need to edit. I believe /etc/htdig.conf is what Red Hat's RPM of htdig uses. More sane packages would use /etc/htdig/htdig.conf, recognizing that you can have more than one config file in CONFIG_DIR, accessible by htsearch, so it doesn't make sense to set CONFIG_DIR to /etc. > > Do I have to recompile htdig myself, or do have to write my own > > htsearch.conf and if so, where do I put it and how does htdig find it > > (via "include: htsearch.conf" in htdig.conf ?) ? > > If something older than 3.1.6 is installed, you should upgrade. > Otherwise, you should be OK with what is currently installed. While > there is nothing wrong with creating additional config files, I would > suggest sticking with /etc/htdig.conf for the time being; saving a copy > of the original before you start editing would of course be a good idea > :) Yes, saving original configs is always a good idea. If indeed Debian uses /etc/htdig/*.conf for ht://Dig config files, then you can put any number of *.conf files in there. If you're using search_rewrite_rules, you can get by with just one config file. If you're using url_part_aliases, then you need two different config files, but you must set them up such that htsearch sees a different setting of url_part_aliases than htdig does. So, if you stick to the default htdig.conf for htdig and htmerge, you should use something else, like htsearch.conf, for htsearch. Then, you must change the "config" input parameter in your search form to something other than "htdig", e.g. set it to "htsearch", so it uses your new config file. This htsearch.conf file could be as simple as an "include: htdig.conf" followed by the new definition of url_part_aliases, which will override the earlier one in htdig.conf. -- Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada) ------------------------------------------------------- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en _______________________________________________ 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
