MaggsWeb:7 » htaccess

URL rewriting – WordPress style

chris — Mon, 07 Dec 2009 13:17:40 +0000

Add this into your .htaccess file…

RewriteEngine On
RewriteCond %{SCRIPT_FILENAME} !-f
RewriteCond %{SCRIPT_FILENAME} !-d
RewriteRule ^(.*)$ index.php/$1

The first RewriteCond checks if the requested URL exists as a file on the filesystem. In mod_rewrite, -f refers to a file, while the bang is the “not” operator. Therefore, !-f means “if the request script filename does not exist as a file”.

If the first rewrite_cond succeeds (that is, the requested file wasn’t found), then Apache moves on to the next condition. The !-d directive means it the condition succeeds if the requested script does correspond to an existing directory on the server.

Finally, if both conditions succeed, the request is forwarded to the index.php file, as specified in the RewriteRule directive.

You can now access request POST data.

MySQL Authentication in .htaccess

chris — Fri, 27 Nov 2009 08:25:24 +0000

Not tried and tested by me (yet) but I am assured that this is the way to do do this…

^?View Code APACHE

 
AuthName "MySQL Authentication"
AuthType Basic
 
AuthMySQLHost localhost
AuthMySQLUser accesssecurity
AuthMySQLPassword DBPWD
AuthMySQLDB accesssecurity
 
AuthMySQLUserTable users
AuthMySQLNameField username
AuthMySQLPasswordField password
AuthMySQLPwEncryption none
 
AuthMySQLUserCondition "user_status=1"
AuthMySQLAuthoritative On
AuthMySQLEnable On
 
require valid-user
 
DirectoryIndex index.html
 
ErrorDocument 401 /errors/error_not_authenticated.html
ErrorDocument 403 /errors/error_forbidden.html
ErrorDocument 404 /errors/error_not_found.html
ErrorDocument 500 /errors/error_oops.html

Flickering images inside ’s

chris — Fri, 24 Jul 2009 15:18:48 +0000

In IE6 and sometimes in IE7 the background images flicker if they’re also an . A small edition to .htaccess overrides the browsers default to load the backgrounds every time.

ExpiresActive On
ExpiresByType image/gif A2592000
ExpiresByType image/jpeg A2592000
ExpiresByType image/png A2592000

Reqires mod_expire on an Apache server (most have it).

Custom Error redirects with .htaccess

chris — Thu, 07 May 2009 12:37:55 +0000

Cold hard website errors are horrible and unnecessary. All you need is a few nice looking .html files in your directory somewhere, then use .htaccess to reditrect to these when there is an error. Obviously, no errors at all would be better….

The format for the .htaccess is :

ErrorDocument errornumber /file.html

For example, if the file notfound.html was in the root directory of my site and I wanted to use it for a 404 error I would use:

ErrorDocument 404 /notfound.html

If the file is not in the root directory of your site, you just need to put the path to it:

ErrorDocument 500 /errorpages/500.html

These are some of the most common errors:

?View Code APACHE

401 - Authorization Required
400 - Bad request
403 - Forbidden
500 - Internal Server Error
404 - Wrong page

and they can all be redirected to the same page, different pages, or even a dynamic page….