For example, given a redirect from source-path to node?a=apples, if a user visits source-path?a=alligators&b=bananas they would be redirected to node?a=apples&b=bananas. The query strings in the redirection will always take precedence over the current query string.
You can find more information about HTTP redirect status codes at http://en.wikipedia.org/wiki/List_of_HTTP_status_codes#3xx_Redirection.
Global redirects
Enabling this will automatically redirect to the canonical URL of any page. That includes redirecting to an alias if existing, removing trailing slashes, ensure the language prefix is set and similar clean-up.
This helps to stop redirection on protected pages and avoids giving away secret URL's. By default this feature is disabled to avoid any unexpected behavior
(formerly Global Redirect features)
The maximum number of 404 error logs to keep in the database log. Requires a cron maintenance task.
Specify pages by using their paths. Enter one path per line. The '*' character is a wildcard. An example path is /user/* for every user page. <front> is the front page.
Prevents logging 'page not found' events. Can be safely enabled when redirect_404 module is used, which stores them separately, nothing else relies on those messages.