I think it would help if the examples in the documentation had explanations as to what the examples are trying to accomplish.
From the url_part_aliases doc it says "A list of translations pairs from and to, used when accessing the database. If a part of an URL matches with the from-string of each pair, it will be translated into the to-string just before writing the URL to the database, and translated back just after reading it from the database." url_part_aliases: http://mgate/ http://balius.com/ I indexed using no url_part_aliases and put the above in the htdig.conf file for the search to read. I got back URLs that begin with http://mgate/ What am I not understanding here? I can architect a mail system to support 1M users easily and yet this stupid thing has me stumped. :) -Chad- At 11:12 AM 2/5/2002 -0600, Gilles Detillieux wrote: >According to Chad M. Stewart: > > Gilles, > > > > I hope you don't mind me contacting you directly, but from my searching > of the > > archives indicates that you know htdig well. If you ever have a question > > about iPlanet Messaging Server I can return the favor. :) > >I don't mind, but I do generally put htdig-related mail that's off-list >at the back of the queue. If you'd prefer a faster response, the mailing >list is a better option. > > > I found your note here, > > http://www.geocrawler.com/archives/3/8825/2001/3/0/5440702/ and read it > and I > > agree with you that newbies have a hard time understanding > > url_part_aliases. I understand that it is a compression algorithm. What I > > don't understand is the syntax of such. The way I understand it during > index > > A-->B and then during search B-->A. If that is right then I don't think it > > will help my situation. I'd be happy to take a crack at writing a newbie > > understandable example of it, if I only understood the syntax. > >I wrote that note back in March of last year. Since then, there has >been a lot more discussion, and I've made changes to the documentation >for url_part_aliases in the new 3.1.6 release, as well as substantial >additions to http://www.htdig.org/FAQ.html#q4.17 to explain the common >pitfalls when people ignore the documentation's recommendations. >Please have another look and see if that doesn't help you understand >how to use this attribute. > > > Here is what I want to do and I can not figure out how to do it. > > > > I indexed files using 'http://mgate/ims/' as the start_url. When I do a > > search I get 'http://mgate/ims' back as the start of the url, > expected. The > > problem is that the host, mgate, is not accessible from everywhere. If > I do > > the search from my LAN the resulting http://mgate/... is valid. If you > were > > to do the search http://mgate/... would be invalid. If I made the URL > valid > > for you, then it would be invalid for my LAN. > > > > From the LAN the hostnames mgate and mgate.amotken.com are valid and > > reachable. From the Internet those hostnames are invalid. People on the > > Internet can reach the exact same content by using www.balius.com. I > can not > > use www.balius.com while on my LAN that would be invalid. > > > > Thus my quandry of how to have the host part of the URL changed. I > don't mind > > having two different search pages, one for LAN one for WAN. If that is the > > way to solve my quandry then how to I get the search from the Internet > side to > > be changed to say www.balius.com when the data was indexed using mgate? > >That's a pretty simple application of url_part_aliases. This would >only need one pair of strings in the definition, with the left-hand-side >changing in the search config file used on the Internet side. > >-- >Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]> >Spinal Cord Research >Centre WWW: http://www.scrc.umanitoba.ca/~grdetil >Dept. Physiology, U. of Manitoba Phone: (204)789-3766 >Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930 _______________________________________________ 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
