Why dont you use an .htaccess

RewriteRule .* - [E=MODULES_PATH:application/modules/]
RewriteRule css\/(.+)\/(.+)\.css$ %{ENV:MODULES_PATH}$1/public/css/$2.css [NC] 

Just when you thought you’d seen all the cool features of HTML5, I’m here to bring you yet another one. The internet is no longer about just websites; it’s about web applications. Often, our users are on portable or mobile devices, and they won’t always have access to a network. With HTML5’s Application Cache, you can provide them with all or some of the functionality they would have online, no matter where they go.

<?php
02
03 $config['admin_username'] = "demo";
04 $config['admin_password'] = "demo";
05
06 if (!($_SERVER['PHP_AUTH_USER'] == $config['admin_username'] && $_SERVER['PHP_AUTH_PW'] == $config['admin_password'])) {
07 header("WWW-Authenticate: Basic realm=\"Papermashup.com Demo Admin\"");
08 header("HTTP/1.0 401 Unauthorized");
09 echo 'This is what happens if you press cancel';
10 ?>
11 <?php
12 exit;
13 }

RedirectMatch 403 /\.git.*$

21
CodeIgniter htaccess
CodeIgniter

This is the CI .htaccess file that I use for my CodeIgniter PHP projects (some of these CodeIgniter htaccess rules can be used for any project, keep reading). CodeIgniter uses mod_rewrite to route all requests to the CI front controller. I’ve made some additions in an attempt to canocalize some of the CodeIgniter URL end points. The key benefit of a canocalized URL is that your search engine page ranking (page juice) is not spread across several pages, but instead, targeted to a single page.
htaccess Rule Breakdown

In your CodeIgniter project you will typically have a default controller and you will be able to access this controller at the following URLs:

This article shows 2 awesome ways to implement caching on your website using Apache .htaccess (httpd.conf) files on the Apache Web Server. Both methods are extremely simple to set up and will dramatically speed up your site!

This is not an introduction to .htaccess… This is the evolution of the best of the best .htaccess on the planet. Its changed over the years with more and better .htaccess tricks using real .htaccess example code. I add my favorite htaccess-related links and sites, results from my htaccess research, and frequently update this article.

You’ve come to the right place if you are looking to acquire mad skills for using .htaccess files.

Originally (2003) this guide was known in certain hacker circles as the Ultimate .htaccess due to the high number of powerful htaccess tricks and tips to bypass security, and the fact that many of the rewrite tricks and htaccess code examples were easy to use.

It’s very important to speed up your web sites so you don’t loose the users.

That being said, many tasks in the checklists from Yahoo or Google are quite complex and are hard to grasp for people who didn’t work all their life configuring Apache or digging deep into the depths of HTTP.

To help this, I created a drop-in .htaccess file that will enable gzipping and long term expiration (helping with unique URLs for your assets).

I recently gave a presentation at WordCamp Montreal on WordPress Security. While doing research for my presentation I came across a bunch of great WordPress Security tips that all WordPress users should use. Surprisingly, a good majority of these tips are not usually followed. Below is a list of the top 5 tips that most WordPress administrators do not do, but should:

This is not an introduction to .htaccess… This is the evolution of .htaccess… The best of the best .htaccess info I can find.

Originally known as the Ultimate .htaccess Guide, its changed over the years with more and better .htaccess tricks using real .htaccess example code. I add my favorite htaccess-related links and sites, results from my best .htaccess experiments, and frequently update this article.

You’ve come to the right place if you are looking to acquire mad skills for using .htaccess files.

RT: @envatowebdev: "An In Depth Guide to mod_rewrite for Apache" - new on Nettuts+ http://t.co/pdM8hoK