On Fri, 28 Sep 2001 12:30:49 -0500 (CDT), Gilles Detillieux <[EMAIL PROTECTED]> wrote:
>According to Nick Boyce: [...] >> ... If my original htdig indexing run stores URLs beginning >> http://123.123.123.123 in the database, then surely >> >> in a single shared htdig.conf: >> url_part_aliases: / http://123.123.123.123/ >> >> should be enough to get the required relative URL generated by >> htsearch ? > >Surely not! If you put that line into a shared htdig.conf, >then htdig will try to encode each and every slash in a URL as >"http://123.123.123.123/"; before putting the URL in the database. >Then, htsearch reverses the encoding to get back the original slashes >in the URL. All you've accomplished is to waste a lot of space in the >database. Definitely not what you want. [...] >I think you're mistakenly assuming that only htsearch uses >url_part_aliases, when in fact both htdig and htsearch use it (as do the >other ht://Dig programs for that matter). Doh. Thanks. I was tired ... [blush] I was completely forgetting that htdig would use it as well. Thanks for taking the time with this idiot. Nick Boyce Bristol, UK -- carpe jugulum - go for the throat ! _______________________________________________ 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
