According to Matthew Boeckman:
> I need to index roughly 30 some odd different (mostly) internal sites 
> for a corporate search page. HTdig rocks and I love it. However I have a 
>   problem. A majority of these sites are password protected (standard 
> http auth), and each have unique user/pass combo's. I have tried (both 
> in the htdig.conf and the 'start.url' files) to specify 
> http://user:[EMAIL PROTECTED], which fails utterly. Of course if I run 
> the htdig command with -u everything is peachy. Is there some way that I 
> have not found to specify u/p in conf file, or do I need to write a 
> shell script to loop htdig through appropriate u/p combo's? I'm hoping 
> not, as it seems like it would be easier to be able to specify that in 
> the conf file. I just can't find any documentation on the htdig.conf 
> that addresses this.

See http://www.htdig.org/attrs.html#authorization

However, in 3.1.x this attribute only takes one username and password,
so to index multiple restricted areas with different usernames and
passwords, you still need to index each one separately and merge the
databases.  Yuck!

In 3.2.0b4, htdig does seem to allow multiple authorization attributes
in separate URL blocks, so you can probably use that if you're using
3.2.0b4.  E.g.:

<url: http://www.this.site.com/>
authorization: joe:joespw
</url>
<url: http://www.that.site.com/jim/>
authorization: jim:jimspw
</url>
<url: http://www.that.site.com/bill/>
authorization: bill:billspw
</url>

I don't know that this has been tested before, so some feedback would
be appreciated.

-- 
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

Reply via email to