no, it does not make sence, but it was the default form that came with htdig, it worked and hense I used it :)
If that is the case, then perhaps you should be suspicious about where your install came from and/or who has modified it. The default that comes with 3.1.6 is as shown below. As you can see, all three value attributes do in fact have a value assigned, even if in two cases that value is an empty string.
<input type="hidden" name="config" value="htdig"> <input type="hidden" name="restrict" value=""> <input type="hidden" name="exclude" value="">
all urls in the DB should start with http://www.jbase.com but in order to index the site I had to index each dir independantly so search string has a whole bunch of different dirs each starting with www.jbase.com.
I am not entirely certain that I understand how you have things setup, but in general an exclude will cause any URL that contains a string specified in the exclude attribute to be removed from the search results. A restrict on the other hand requires that a string specified in the restrict attribute be present in the URL in order to prevent it from being removed from the search results. The behavior of exclude and restrict are discussed in the configuration file documentation.
http://www.htdig.org/attrs.html#exclude http://www.htdig.org/attrs.html#restrict
Jim
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ ht://Dig general mailing list: <[EMAIL PROTECTED]> ht://Dig FAQ: http://htdig.sourceforge.net/FAQ.html List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-general
