Disallow does not work (on certain paths)

Same happens to me with
node
node/
node/*

Please try the dev build from August 2007 and let me know if this works for you guys.

Subscribing.

Is this still an issue?
Just release 1.2 - let me know if you still experience bad behavior.

I tired both builds and it doesnt work for me either on Drupal 5.

+1.

This doesn't work for me.

I am trying to restrict access to node/* for anonymous users without success (i only want them to access the alias). The module had no effect.

Restricting "front" worked though.

The module takes any paths provided and converts them to their alias. If the alias is not listed, it wont protect visitors from that page.

Ok.

I hacked the "globalredirect" module to accomplish what i needed, i e denying access to node/* and only allow aliases.

( in globalredirect.module change line 103 drupal_goto('$alias', $query_string, NULL, 301); to drupal_goto('', $query_string, NULL, 301); )

@budda:
Please explain the rationale behind the disallow feature in regards to your comment in #7 here.

If I should guess, you are saying that first one has to create an alias, and only then can you get disallow to work towards that alias.

Does that mean that it only works with aliases you create yourself and which does not take part in existing paths that drupal core or other modules are implementing themselves? That paths such as "node" or "group" is not possible to "disallow"?

If so, I suggest adding such a statement to the readme and the project page, for clarification.

Maybe this is not a bug, but by design?

@DanielTheViking The module attemps to convert any path to an alias if available.

$path = drupal_get_path_alias(check_plain($_GET['q']));

If no alias is found, the same path is returned as per the API docs.

So node* would work as a path to restrict.

The pattern matching code used is taken from Drupal cores block.module