Hi
OK, you've almost convinced me that it's not necessary :-)
FYI, what I was proposing was:
url_filters: ALLOW item.cgi?s= item.cgi?id= DISALLOW item.cgi ALLOW *
As in, one single configuration line rather than a set of attributes. When
checking to see whether a URL is allowed, it would check each filter *in
order* - the first match would dictate the behaviour, whether that was in
an 'allowed' section or 'disallowed'. You could put more specific rules at
the head of the list and more general rules near the end.
On Tue, 5 Jun 2001, Geoff Hutchison wrote:
> 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)]
But... you're assuming all I want to do is index item.cgi, with those
query strings. I actually want to index everything, except item.cgi,
unless it has those parameters. In order to do this, I would have to:
limit_urls_to: /cgi-bin/item.cgi(\?id=35\?s=356) /a /b /c /d /e....
I don't want to have to list every content directory in the limit_urls_to
attribute. That's not practical in our case, because we have teams of
editors constantly messing with these things :-| And I can't put /cgi-bin
into exclude_urls - because I have exceptions to that rule. (In fact we
have such an icky complicated legacy website there are lots of examples
like this).
Do you see the problem? The implementation may be the wrong way to solve
it, but that's another issue.
Thanks for responding to my various mails. I'll leave you alone if, in
your next reply, you convince me I really am wrong :-)
Thanks (praying he's RTFMed properly...)
Ade
_______________________________________________
htdig-dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/htdig-dev
