Do not allow redirects using <front> as the source

Yeah you shouldn't ever be redirecting just with <front>. It's not something I can support. You should likely enable some kind of .htaccess redirection instead.

We should really add the validation (unless it's + query parameters)

hey to any one else that finds this..

I had the same issue, trying to redirect users to the front page without the real path in the url if they ended up on the real path page..

you can accomplish this like so:

	if(drupal_is_front_page()){
		if(request_uri()==base_path().$_GET['q']){
			drupal_goto("<front>");
		}
	}

Using <front> as the From path also seems to break drush's cron command. That's some serious borkage going on. Enough so the help text in the Add Redirect page should call out <front> and the form verify should reject attempts to redirect <front>.

Here's what worked for me. I added a line to .htaccess in the Rewrite rules section:

RewriteRule ^/*$ /redirected/home/path [L,R=307]

This works for any hostname, any port, and even if they stick extra slashes in the address bar (e.g., http://example.org// ).

(edit: added RewriteRule flags)

As per comment #4, here is a patch against version 6.x-1.x-dev.

1.) It updates the helper text below Front: to: "Enter an internal Drupal path or path alias to redirect (e.g. node/123 or taxonomy/term/123). Fragment anchors (e.g. #anchor) and <front> are not allowed."

2.) It fires form_error in the case that the input for From: is <front>. The user receives the following message: "The source path cannot be set to <front>" in an attempt to maintain consistency with the other error messages in the module.

This has been tested locally on a clean install of Drupal 6.26.

Sorry - trying new patch.