In WordPress, I've got a page known as Experiments having a slug of experiments. That page should have the ability to be utilized at http://site.com/experiments.

Issue is, I should also possess a folder on my small server with this title to ensure that http://site.com/experiments/thing/ loads the index.html file from the folder (if there's one).

I figured I'd found an ideal rewrite structure (from this blog post):

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

# BEGIN WordPress
# END WordPress

It appears enjoy it rewrites sites using WordPress unless of course your directory comes with an index.html or index.php file by which situation it loads it disregarding WordPress. And delay pills work perfectly for subdirectories, but http://site.com/experiments/ attempts to redirect to http://site.com/experiments backwards and forwards forever.

Anybody understand what I am doing wrong?

Figured it. Wordpress wasn't adding trailing slashes to products, therefore it was delivering me to /experiments after which Apache desired to send me to /experiments/ producing a loop.

Did a lot of reading through on Web addresses (that was quite interestingOrenjoyable) and today have made the decision to include trailing slashes to any or all my Web addresses. And things are working perfectly.

Edit: A fascinating side note is the fact that Wordpress decides whether or not to use trailings slashes everywhere according to whether there's one out of your custom permalink structure (ie. /%postname%/). Wasted enough time searching regarding where I set that, also it was immediately all along.