> You can already do things like:
> 
> +www.foo.com/bar/*
> +*.zip
> -*.exe
> -www.foo.com/bar/*.zip
> +www.foo.com/bar/*.exe

One more clarification using your example:

You cannot do that, if the original path looks the same, because of an ASP/CGI
etc script which only calls for numerical values! ie the "security via
obscurity" approach.
 
In case lake this only a nested scan rule would provide the correct files;
first looks what kind of page was resulted from the cgi script, and then
applies the ++nested scan rule for these results only.

I hope this clarified the issue, I find it difficult to explain, but have run
into this problem a few times, and expect this to be an increasing trend.