From: Gilles D. <gr...@sc...> - 2001-10-31 21:04:14
|
According to Geoff Hutchison: > At 9:22 AM +0200 10/25/01, Juergen Obermann wrote: > >It would be much better to have configuration directives > >'case_sensitive_urls' and 'case_insensitive_urls' in addition to the > >general boolean 'case_sensitive' to dig several servers in one run. > > No, not really. At the moment, there are already *way* too many > configuration attributes. > > However, in version 3.2, you can specify certain attributes as having > a per-server or per-URL context. At the moment, case_sensitive is not > one of these attributes, but it will probably become a per-server > attribute--the catch is fixing the places that deal with it. > > If someone would like to look at adding this functionality to 3.2, I > can point them in the right direction. One little wrinkle that might complicate moving the case_sensitive attribute into server blocks in 3.2 config files is the fact that this attribute also affects the handling of other global attributes. For instance, htdig makes regular expression patterns out of limit_urls_to, exclude_urls, and others, and compiles these patterns before starting to dig. When it compiles them, it uses the "ignore case" option if the case_sensitive attribute is false. Changing case_sensitive in a server block will have no effect on patterns already compiled, so the global setting will still matter. You don't want to start recompiling all your patterns on a document by document basis either, though! -- Gilles R. Detillieux E-mail: <gr...@sc...> 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 |