Htaccess redirect on empty directories

.htaccessmod-rewriteredirectweb

My website is built up like the following

www.domain.com/products/catname/myproduct.php

www.domain.com/products/myproduct.php

Some files are in deeper directories. I am wanting to redirect www.domain.com/products/catname/ (for example) to a certain page. My directories do not include index files.

How do I do this using htaccess?

I have tried

Options +FollowSymLinks
RewriteEngine On
RedirectMatch permanent ^/products http://domain.co.uk/
RedirectMatch permanent ^/products/productname http://domain.co.uk/

But this redirect any file in the /products directory (domain.co.uk/products/prod1.php for example will redirect to domain.co.uk)

Best Answer

Using mod_alias:

Options +FollowSymLinks
RewriteEngine On
RedirectMatch permanent ^/products/?(productname)?$ http://domain.co.uk/

Using mod_rewrite:

Options +FollowSymLinks
RewriteEngine On
RewriteRule ^/?products/?(productname)?$ http://domain.co.uk/ [L,R=301]

Related Solutions

Vanity URL manager for Apache Web Server

I don't know what exactly defines a "maintenance nightmare" in your book, but you could try to go with a dynamic rewriting map in apache:

RewriteEngine on
RewriteMap    vanity-map       prg:/path/to/vanity.pl
RewriteRule   ^/(.*)/(.*)$  /${vanity-map:$1}/$2

vanity.pl could could be a simple perl script (don't forget to set $| = 1;) which gets the first part of the request URL (as outlined above) on STDIN and is supposed to rewrite that - e.g. by querying a database.

Now, that just leaves the frontend. I'm an inexperienced Ruby on Rails programmer (it's just a spare time activity), but I think, if it doesn't need to look pretty, even I could write an application that authenticates a user, lets him create a rewriting and shows that up for approval to some IT guys/$WHATEVER in much less than a week, so I don't think any real programmer would have a problem doing that in a few hours. Depending on the database, there might even be frontends readily available which will do the job with only a little customization (php*admin comes to my mind).

This way, you get all the flexibility of a database approach paired with a central source for all redirections. As long as the database's index on the URL part fits in your servers memory, you won't even have to worry about performance.

Apache: How to redirect OPTIONS request with .htaccess

RewriteCond %{REMOTE_HOST} ^::1$
RewriteRule  ^OPTIONS  http://www.google.com/  [L]

that's my best guess, i'm certain of the RewriteCond, but not quite with the RewriteRule

it will match on the REMOTE_HOST being ::1 and then rewrite a request for any URL starting with OPTIONS to www.google.com

Best Answer

Related Solutions

Vanity URL manager for Apache Web Server

Apache: How to redirect OPTIONS request with .htaccess

Related Topic