lucy24 - 2:13 am on Aug 19, 2011 (gmt 0)
Last two rules, as translated into English:
#1: If a request comes in for any nonexistent file anywhere within the /test/ directory, send them to example.com/test/rewrite.php, making "url" + the original request into a new query string (and deleting any previous query).
#2: If a request comes in for any nonexistent file anywhere, send them to example.com/rewrite.php, with the same query-string business.
Whether this works or not will depend entirely on whether the /rewrite.php and /test/rewrite.php files actually exist and that they do what they are intended to do, presumably ending with a true redirect.
You don't want users to type in any old garbage, or click on a hopelessly mangled link, and end up in the right place. (You may think you do, because it's a human-friendly approach, but go look up the phrase Duplicate Content.) Hence the final redirect.
If both types of queries are being shipped off to a rewrite function accompanied by their original request in the form of a query string, why do there need to be two separate rewrite.php files? Can't the same file deal with both? If you're trying to avoid / in the query string, you need to take a few more steps to make sure the request doesn't include one. It isn't enough to say that your site simply doesn't have deeper nests of directories-- because these rewrites are by definition only applied to files that don't exist.