[wp-hackers] So, this whole .htaccess thing...

Sam Angove sam at rephrase.net
Sat Aug 26 06:08:05 GMT 2006

On 8/26/06, Charles <lists06 at wiltgen.net> wrote:
> I had to modify several lines just to put WordPress in
> site.com/wp instead of site.com/wordpress, I had to add a few more lines to
> support FeedBurner, and I've had to add a few hundred lines to to support
> permalink changes.  It seems like losing the dependence on .htaccess would
> make it easier to run WordPress on non-Apache servers, would allow a new
> class of "router" plug-ins to be created, etc.

I'm not sure why you had to make manual edits, but WordPress certainly
isn't dependent on .htaccess or mod_rewrite.

The default, non-verbose rewrite rules[1] simply pass all requests to
index.php. WordPress looks up its internal store of rewrite rules
(i.e. routes) and maps the request URL on to the matching resource, or
serves a 404 if nothing matches. It's already very flexible with
regard to plugins modifying or extending those rules.

It's not .htaccess or mod_rewrite dependent because you can use any
other mechanism to pass the incoming URLs to WordPress. The "almost
pretty" (index.php-prefixed) URLs use PATH_INFO. You can set WordPress
as a 404 handler and map them that way.

I don't understand exactly what behaviour it is that you're hoping to
change. Can you provide more details?

[1]: e.g.

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /wordpress/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /wordpress/index.php [L]
# END WordPress

More information about the wp-hackers mailing list