At 11:15 AM +0100 6/5/01, Adrian Taylor wrote:
>allow: /cgi-bin/item.cgi?id=35
>allow: /cgi-bin/item.cgi?s=356
>disallow: /cgi-bin/item.cgi?(anything else)
limit_urls_to: ... [/cgi-bin/item.cgi(\?id=35|\?s=356)]
(That's off the cuff, don't know if the regex is quite right.)
Anything that doesn't match a limit_urls_to pattern is excluded right
off.
>I can't see how these would be possible with a list of exclusion regexes,
>which is what I find in 3.1.5 and 3.2.0b3. At least, not without negative
>lookahead assertions and all the whizzy Perl stuff that the system
>routines don't provide.
I don't think this is necessary. Granted, you can make regexp more
easily with various Perl features, but you certainly can make
equivalent regexp using system routines AFAIK. (I'm thinking back to
my CS theory courses...)
I mean the "allow" and "disallow" attributes you mention sound a
*lot* like limit_urls_to and exclude_urls to me. What differences do
you see between these sets of attributes?
Also, many of your examples, you've given "allow" attributes multiple
times--unless you've patched the Configuration class, attributes
later in the file override earlier ones. This lets people use
"include" attributes to include a global config file and then
override in a different one.
-Geoff
_______________________________________________
htdig-dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/htdig-dev
