MainelyDesign.com Blog

Network Solutions' Flawed .htaccess and Mod_Rewrite Rules Implementation

Posted on 08/06/2009 at 02:38 pm by Kevin Wentworth
Viewed 34,551 times | 7 comments

I can't believe it!  I spent hours trying to get the mod_rewrite rules working in .htaccess on Network Solutions' servers.  Everything I tried didn't work.  Using the default .htaccess (from Cake distribution) failed.  I've used the distribution on several servers and never had any issue with the rewrite rules.  However, Network Solutions's mod_rewrite works differently than [all] other servers.

The target and destination file have to exist

Wait, the target file has to exist?  That's right.  You actually need to have a target file, specifically each url being requested, in place for each rewrite rule (even if it's a dummy or 0kb file).  This is straight from Network Solutions' server admin. In order for mod_rewrite rules to work on their servers, you need a target file.

That is completely ridiculous! I use .htaccess so I can have 1 file that "routes" all requests.  Why would I ever want to make dummy/placeholder files? The answer- never!  Just look at Drupal, Cake, Joomla, any CMS uses .htaccess this way, at least if you want SEO friendly links.

Solved by Using a 404 ErrorDocument handler

The tech at Network Solutions said he ran into this the other day (I'm surprised it doesn't come up more...).  He fixed it by using an ErrorDocument handler in the .htaccess file.  Wouldn't you know it worked!  Instead of the Cake default, use this as the .htaccess in your web root:

UPDATE: It's not REALLY working (8/11/2009)

I knew it was too good to be true.  I accessed the web site from my BlackBerry and I got a 404 error.  When I got home, I tried it out and Firebug was reporting 404 error headers for all requests.  Although the web site appears to work on the surface, the 404 errors will be detrimental to search engine rankings (SERPs). Not good!

Symptons that this could be happening to you

On all IE browsers I was getting a generic error message at the bottom of each page:

In FireFox most pages would load OK, but every few page loads FF would prompt me to Save or Open the file, or, it would show a white screen with black text source code. WTF?  It almost looks like an extra request for each file and some HTTP headers are getting jammed into your file.  No wonder FF wouldn't render it.  Here's what one of those files looked like:

Network Solutions' Implementation of .htaccess Sucks

I hope this helps all the people struggling to get .htaccess, mod_rewrite, and RewriteRule working on Network Solutions.  If it doesn't work, try some of the other suggestions I read:

• Try removing the <IfModule mod_rewrite.c> and </IfModule> tags (Network Solutions apparently runs their PHP as CGI not an apache module)
• Try setting RewriteBase /  (this helped make the rewrite rule work, but didn't eliminate those garbage requests)
• Or, you can set your RewriteRule ^(.*)$ /index.php?url=$1 (see that slash in front of index.php?)
• Or, you can completely remove all files and just have the most simple rewrite rule and you'll still get the freaking phantom error message

Network Solutions only saw the error ONCE

No kidding, they couldn't ever see this error.  I figured they'd send back a 'It's your code' response, but actually gave me the courtesy of a call back.  What's weird is that EVERY time I would load the page in IE I'd see the error (except going to the webroot: / or index.php) and now I know why- the target and destination file existed.  Oh man!

Cheers, (and boy do I need a beer after that one)

-Kevin Wentworth