Hi
I'm starting to think about applying my patch to 3.2 - so I have to ask --
On Wed, 30 May 2001, Geoff Hutchison wrote:
> On Tue, 29 May 2001, Adrian Taylor wrote:
>
> > Secondly, it gives a more flexible URL filtering scheme, where you can put
> > something like this in the config file:
> > url_filters: ALLOW item.cgi jobs.cgi FORBID cgi templates
> > You can have any number of ALLOW/FORBID blocks for fairly fine-grained
> > control. The first match, whether it's ALLOW or FORBID, controls what
> > happens to the URL.
>
> I guess I don't see how this is more fine-grained or flexible than the
> regex limits in the 3.2 code, though I can see how it might be a bit
> easier to use than the 3.1.5 controls.
Here is a situation which doesn't /seem/ to be covered by the existing
Ht://Dig controls - please tell me if I am wrong.
We want to:
allow: /cgi-bin/item.cgi?id=35
allow: /cgi-bin/item.cgi?s=356
disallow: /cgi-bin/item.cgi?(anything else)
A similar example:
allow: /cgi-site/(anything).cgi?action=detail
disallow: /cgi-site/(anything).cgi?(anything else)
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.
Is there a way of doing it? If not, what is your advice about the best way
of patching ht://Dig to add this functionality? Can you think of a better
way than the way I describe (which is how certain other big commercial
search engines do it, so was the obvious solution...) I would now use
regexes rather than StringMatches.
Cheers
Ade
_______________________________________________
htdig-dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/htdig-dev
