How may I perform a rule if the URL is _NOT_ matching the path &quot;forums&quot;?

For example:

    RewriteCond IF URL IS NOT forums
    RewriteRule !\.(js|gif|css|jpg|png)$ %{DOCUMENT_ROOT}/index.php [L]



Rewrite rule if condition is not matched

I&#39;ve had to update my .htaccess from this:

    RewriteCond %{HTTPS} !=on
    RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

to this:

    RewriteCond %{HTTP:X-Forwarded-Proto} !https
    RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

to get it working behind an AWS Elasic Load Balancer. 

It all seems to work fine on AWS, but in my local environment I&#39;m stuck in a redirect loop. 

How I can get this setup to work correctly in both environments?

apache HTTP:X-Forwarded-Proto in .htaccess is causing redirect loop in dev environment

I have a problem whereby google has indexed some pages with the wrong url.

The url they are indexing is:

    http://www.example.com/index.php/section1/section2

I need it to redirect to:

    http://www.example.com/section1/section2

.htaccess isn&#39;t my forte, so any help would be much appreciated.

Thanks in advance.

htaccess remove index.php from url

We have some very basic mod_rewrite rules:

    RewriteRule ^something.swf$ http://www.newdomain.com/something.swf [R=302,L]

mod_rewrite seems to do its job, and if the user is accessing:

`something.swf?param=value`, it is redirected correctly to `http://www.newdomain.com/something.swf?param=value`

the problem is in this situation:

    www.olddomain.com/something.swf?param=URL_ENCODED_VALUE

what ends up happening is mod_rewrite takes it upon it self to re-urlencode the query string param

so what the user ends up with is:

    www.olddomain.com/something.swf?param=URL_ENCODED_VALUE

REDIRECTED TO

    www.newdomain.com/something.swf?param=URL_ENCODED_VALUE_OF_URL_ENCODED_VALUE

so we end up with a double-urlencoded value. boourns!

While I do understand we could make a `\?(.*)` ... `?$1` rule for this, I am thinking there must be a way to tell mod_rewrite NOT to urlencode the query string params... we would like to avoid using 2 rules since valid paths are:

    something.swf (no query string)

and

    something.swf?someparams...

so yea, ideally... just tell mod_rewrite: please, no urlencoding of query string params... just direct passthru to the new URL via `R=302`.

mod_rewrite urlencoding an already urlencoded query string parameter - any way to disable this?

Many posters have problems debugging their RewriteRule and RewriteCond statements within their **`.htaccess`** files.  Most of these are using a shared hosting service and therefore don&#39;t have access to the root server configuration. They cannot avoid using `.htaccess` files for rewriting and _cannot_ enable a RewriteLogLevel&quot; as many respondents suggest.  Also there are many `.htaccess`-specific pitfalls and constraints are aren&#39;t covered well.  Setting up a local test LAMP stack involves too much of a learning curve for most.   

So my Q here is how would we recommend that they ***debug*** their rules _themselves_.  I provide a few suggestions below.  Other suggestions would be appreciated.

 1. **Understand that the mod_rewrite engine cycles through `.htaccess` files**. The engine runs this loop:

        do
          execute server and vhost rewrites (in the Apache Virtual Host Config)
          find the lowest &quot;Per Dir&quot; .htaccess file on the file path with rewrites enabled
          if found(.htaccess)
             execute .htaccess rewrites (in the user&#39;s directory)
        while rewrite occurred

    So your rules will get executed repeatedly and if you change the URI path then it may end up executing other `.htaccess`files if they exist. So make sure that you terminate this loop, if necessary by adding extra `RewriteCond` to stop rules firing.  Also delete any lower level `.htaccess` rewrite rulesets unless explicitly intent to use multi-level rulesets.  

 2. **Make sure that the syntax of each Regexp is correct** by testing against a set of test patterns to make sure that is a valid syntax and does what you intend with a fully range of test URIs.  See [answer below][1] for more details.

 3. **Build up your rules incrementally in a test directory.**  You can make use of the &quot;execute the deepest `.htaccess` file on the path feature&quot; to set up a separate test directory (tree) and debug rulesets here without screwing up your main rules and stopping your site working.  You have to add them one at a time because this is the only way to localise failures to individual rules.

 4. **Use a dummy script stub to dump out server and environment variables**. (See **Listing 2**)If your app uses, say, `blog/index.php` then you can copy this into `test/blog/index.php` and use it to test out your blog rules in the `test` subdirectory.  You can also use environment variables to make sure that the rewrite engine in interpreting substitution strings correctly, e.g.

        RewriteRule ^(.*) - [E=TEST0:%{DOCUMENT_ROOT}/blog/html_cache/$1.html]

    and look for these **REDIRECT_\*** variables in the phpinfo dump.  BTW, I used this one and discovered on my site that I had to use `%{ENV:DOCUMENT_ROOT_REAL}` instead.  In the case of redirector looping  **REDIRECT_REDIRECT_\*** variables list the previous pass. Etc.. 

 5. **Make sure that you don&#39;t get bitten by your browser caching incorrect 301 redirects**.  See [answer below][2].  My thanks to [Ulrich Palha][3] for this.

 6. The rewrite engine seems sensitive to cascaded rules within an `.htaccess` context, (that is where a `RewriteRule` results in a substitution and this falls though to further rules), as I found bugs with internal sub-requests [(1)][4], and incorrect **PATH_INFO** processing which can often be prevents by use of the \[NS\], \[L\] and \[PT\] flags.

Any more comment or suggestions?

## Listing 1 -- phpinfo ##

    &lt;?php phpinfo(INFO_ENVIRONMENT|INFO_VARIABLES);

  [1]: https://stackoverflow.com/questions/9153262/tips-for-debugging-htaccess-rewrite-rules/9261963#9261963
  [2]: https://stackoverflow.com/questions/9153262/tips-for-debugging-htaccess-rewrite-rules/9261963#9204355 
  [3]: https://stackoverflow.com/users/499472/ulrich-palha
  [4]: http://httpd.apache.org/docs/2.2/rewrite/flags.html#flag_n

Tips for debugging .htaccess rewrite rules

I have following command in my .htaccess

        RewriteCond %{HTTP_HOST} ^(www\.)?([a-z0-9-]+)\.example\.com [NC]
        RewriteRule ^(.*?)-([a-z]+) %2/$1.$2 [L]
        RewriteRule ^(.*?)-([0-9]+)([a-z]) %2/$1$3.$2 [L]

%2 is not working in second and later lines.
Can I define any variable for %2 and use it in all RewriteRule commands?
Following command works   

         RewriteCond %{HTTP_HOST} ^(www\.)?([a-z0-9-]+)\.example\.com [NC]
         RewriteRule ^(.*?)-([a-z]+) %2/$1.$2 [L]
         RewriteCond %{HTTP_HOST} ^(www\.)?([a-z0-9-]+)\.example\.com [NC]
         RewriteRule ^(.*?)-([0-9]+)([a-z]) %2/$1$3.$2 [L]
But I want use %2 for multiple rule line without duplicating condition.


Multiple RewriteRules for single RewriteCond in .htaccess

Trying to get

    www.example.com

to go directly to

    www.example.com/store

I have tried multiple bits of code and none work.

What I&#39;ve tried:

    Options +FollowSymlinks
    RewriteEngine on
    
    RewriteCond %{HTTP_HOST} ^example.com$
    RewriteRule (.*) http://www.example.com/$1 [R=301,L]
    
    RewriteCond %{HTTP_HOST} ^(.+)\www.example\.com$
    RewriteRule ^/(.*)$ /samle/%1/$1 [L]

What am I doing wrong?

How can I use .htaccess rewrite to redirect root URL to subdirectory?

Which redirect rule would I use to redirect all pages under `olddomain.example` to be redirected to `newdomain.example`?

The site has a totally different structure, so I want **every page** under the old domain to be redirected to the new domain **index page**.

I thought this would do (under olddomain.example base directory):

    RewriteEngine On
    RewriteRule ^(.*)$ http://newdomain.example/ [R=301]

But if I navigate to `olddomain.example/somepage` I get redirected to `newdomain.example/somepage`. I am expecting a redirect only to `newdomain.example` without the page suffix.

How do I keep the last part out?



.htaccess redirect all pages to new domain

How can I force to SSL/https using .htaccess and mod_rewrite page specific in PHP.

Force SSL/https using .htaccess and mod_rewrite

I have seen this in a few `.htaccess` examples

    RewriteBase /

It appears to be somewhat similar in functionality to the `&lt;base href=&quot;&quot;&gt;` of HTML. 

I believe it may automatically prepend its value to the beginning of `RewriteRule` statements (possibly ones without a leading slash)?

I could not get it to work properly. I think it&#39;s use could come in very handy for site portability, as I often have a development server which is different to a production one. My current method leaves me deleting portions out of my `RewriteRule` statements.

Can anyone explain to me briefly how to implement it?

Thanks

How does RewriteBase work in .htaccess

I have a website that doesn&#39;t seem to redirect from non-www to www.
  
*My Apache configuration is as follows:*

    RewriteEngine On
    ### re-direct to www
    RewriteCond %{http_host} !^www.example.com [nc]
    RewriteRule ^(.*)$ http://www.example.com/$1 [r=301,nc] 

What am I missing?


apache redirect from non www to www

I have two main problems with mod_rewrite:

1) There is no meaningful error reported when I have an invalid rule

    ![Enter image description here][1]

2) To reliably test each modification, I have to erase Google Chrome&#39;s cache. This isn&#39;t rocket science, but I have to hit &lt;kbd&gt;Ctrl&lt;/kbd&gt; + &lt;kbd&gt;Shift&lt;/kbd&gt; + &lt;kbd&gt;Delete&lt;/kbd&gt;, click &lt;kbd&gt;OK&lt;/kbd&gt;, and close the window, and reload.

I&#39;d like to see if any of the gurus are willing to share their secrets to efficiently managing mod_rewrite code.

  [1]: http://i.stack.imgur.com/g3Jte.jpg


How to debug Apache mod_rewrite

How to remove `.html` from the URL of a static page? 

Also, I need to redirect any url with `.html` to the one without it. (i.e. `www.example.com/page.html` to `www.example.com/page` ).

How to remove .html from URL?

&quot;Pretty links&quot; is an often requested topic, but it is rarely fully explained. [mod_rewrite][1] is one way to make &quot;pretty links&quot;, but it&#39;s complex and its syntax is very terse, hard to grok, and the documentation assumes a certain level of proficiency in HTTP. Can someone explain in simple terms how &quot;pretty links&quot; work and how mod_rewrite can be used to create them?

Other common names, aliases, terms for clean URLs: [RESTful][2] URLs, user-friendly URLs, [SEO][3]-friendly URLs, [slugging][4], and MVC URLs (probably a misnomer)

  [1]: https://en.wikipedia.org/wiki/URL_redirection#Apache_HTTP_Server_mod_rewrite
  [2]: http://en.wikipedia.org/wiki/Representational_state_transfer#RESTful_web_services
  [3]: http://en.wikipedia.org/wiki/Search_engine_optimization
  [4]: https://en.wikipedia.org/wiki/Clean_URL#Slug


Reference: mod_rewrite, URL rewriting and &quot;pretty links&quot; explained

I have 8 lines of rewrite rules in my .htaccess file. I need to exclude two physical directories on my server from these rules, so they can become accessible. For now all requests are sent to index.php file. 

Directories to exclude: &quot;admin&quot; and &quot;user&quot;. 

So http requests: http://www.domain.com/admin/ should not be passed to index.php file.


    ErrorDocument 404 /index.php?mod=error404
    
    Options  FollowSymLinks
    RewriteEngine On
    RewriteBase /
    
    RewriteCond %{HTTP_HOST} !^www\.domain\.com$ [NC]
    RewriteRule ^(.*)$ http://www.domain.com/$1 [R=301,L]
    
    RewriteRule ^([^/] )/([^/] )\.html$ index.php?lang=$1&amp;mod=$2 [L]
    RewriteRule ^([^/] )/$ index.php?lang=$1&amp;mod=home [L]

.htaccess mod_rewrite - how to exclude directory from rewrite rule

I am writing a simple PHP-based MVC-ish framework. I want this framework to be able to be installed in any directory.

My PHP script grabs the request uri and breaks it off into segments. It makes segment 1 the controller and segment 2 the action. This goes all fine  when I do this:

    http://www.example.com/mvc/module/test/

It will go to the specific module controller and method. Now I have a default controller,  the home controller, which is in folder home.

Now when I access this folder directly  `http://www.example.com/mvc/home/`
It will display a `403 forbidden` , because this folder does exist, instead it should also go back to  `http://www.example.com/mvc/index.php`

If I would have installed the framework in a different folder, lets say folder framework it has to redirect back to `http://www.example.com/framework/index.php`

I would like to redirect every folder and php file back to the index.php, leaving everything else the way it is.

My first problem I encountered was it never redirects to the right folder, always to the domain root folder.

This is what I tried :

    RewriteEngine on
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteRule . index.php [L]



Redirect all to index.php using htaccess

I was wondering if it is possible to check if `mod_rewrite` is enabled on **Apache** AND **IIS** in **`PHP`**.

**ModRewrite** for IIS exists. Check it [`here`][1].

So, I&#39;m looking for a PHP script that checks for `mod_rewrite` on **Apache** and **IIS.**

Does anyone know such script or can write one?

Especially for Microsoft **IIS**.

Thanks!

  [1]: http://www.micronovae.com/ModRewrite/ModRewrite.html

How to check if mod_rewrite is enabled in php?

I have a URL that looks like:

    url.com/picture.php?id=51

How would I go about converting that URL to:

    picture.php/Some-text-goes-here/51

I think WordPress does the same.

How do I go about making friendly URLs in PHP?

URL rewriting with PHP

Here is the scenario:

 - There is a `index.php` file in root folder
 - some files are included in `index.php` which are in the `includes` folder.
 - 1 other file (`submit.php`) is in the root folder for form submit action.

I want to restrict direct user access to the files in `includes` folder by htaccess. also for `submit.php`. But include will work for `index.php` file. 
Like, if user types `www.domain.com/includes/somepage.php`, it will restrict it (may be redirect to a error page).



deny direct access to a folder and file by htaccess

Yes, I&#39;ve read the Apache manual and searched here. For some reason I simply cannot get this to work. The closest I&#39;ve come is having it remove the extension, but it points back to the root directory. I want this to just work in the directory that contains the `.htaccess` file. 

I need to do three things with the `.htaccess` file.

1. I need it to remove the `.php`

  a. I have several pages that use tabs and the [URL][1] looks like `page.php#tab` - is this possible?
  
  b. I have one page that uses a session ID appended to the URL to make sure you came from the right place, `www.domain.com/download-software.php?abcdefg`.

Is this possible? Also in doing this, do I need to remove `.php` from the links in my header nav include file? Should `IE &quot;&lt;a href=&quot;support.php&quot;&gt;support&lt;/a&gt;&quot; be &lt;a href=&quot;support&quot;&gt;support&lt;/a&gt;?`

2. I would like it to force `www` before every URL, so it&#39;s not `domain.com`, but `www.domain.com/page`.
3. I would like to remove all trailing slashes from pages.

I&#39;ll keep looking, trying, etc. Would being in a sub directory cause any issues?

  [1]: http://en.wikipedia.org/wiki/Uniform_Resource_Locator


Remove .php extension with .htaccess

Currently I am using the hosting with **lightspeed** server. Hosting says `mod_rewrite` is enabled but I can&#39;t get my script working there. Whenever I try to access the URL, it returns **404 - not found** page.

I put the same codes at another server which is running with Apache. It&#39;s working over there. So I guess, it&#39;s the `.htaccess` and `mod_rewrite` issue.

But Hosting support is still insisting with me that their mod_rewrite is on, so I would like to know how can I check whether it&#39;s actually enabled or not.

I tried to check with `phpinfo()`, but no luck, I can&#39;t find `mod_rewrite` there, is it because they are using `lightspeed`?

Is there any way to check? Please help me out. Thank you.

**FYI:** my `.htaccess` code is

    Options -Indexes
    
    &lt;IfModule mod_rewrite.c&gt;
    DirectoryIndex index.php
    RewriteEngine on
    
    RewriteCond $1 !^(index\.php|assets|robots\.txt|favicon\.ico)
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule ^(.*)$ ./index.php/$1 [L,QSA]
    &lt;/IfModule&gt;

I tried like this also


    DirectoryIndex index.php
    RewriteEngine on
    
    RewriteCond $1 !^(index\.php|assets|robots\.txt|favicon\.ico)
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule ^(.*)$ ./index.php/$1 [L,QSA]

But same result.

How to check whether mod_rewrite is enable on server?

Is this how to use AND, OR for `RewriteCond` on Apache?

    rewritecond A [or]
    rewritecond B
    rewritecond C [or]
    rewritecond D
    RewriteRule ... something

becomes `if ( (A or B) and (C or D) ) rewrite_it`.

So it seems like &quot;OR&quot; is higher precedence than &quot;AND&quot;?  Is there a way to easily tell, like in the  `(A or B) and (C or D)` syntax?

how to use &quot;AND&quot;, &quot;OR&quot; for RewriteCond on Apache?

I have a `RewriteRule` in a `.htaccess` file that isn&#39;t doing anything. How do I troubleshoot this?

* How can I verify if the `.htaccess` file is even being read and obeyed by Apache? Can I write an echo &quot;it is working&quot; message, if I do write it, where would that line be echoed out?
* If the `.htaccess` file isn&#39;t being used, how can I make Apache use it?
* If the `.htaccess` is being used but my `RewriteRule` still isn&#39;t having an effect, what more can I do to debug?

How to debug .htaccess RewriteRule not working

There seem to be a decent number of `mod_rewrite` threads floating around lately with a bit of confusion over how certain aspects of it work. As a result I&#39;ve compiled a few notes on common functionality, and perhaps a few annoying nuances.

What other features / common issues have you run across using `mod_rewrite`?

Hidden features of mod_rewrite

How do I remove the &lt;code&gt;&quot;index.php&quot;&lt;/code&gt; sticking out in every path in codeigniter somewhere in the center?
I want clean non &lt;code&gt;index.php-fied URLs&lt;/code&gt;?

How to remove &quot;index.php&quot; in codeigniter&#39;s path

I have installed Laravel many times on Windows OS but never had this problem.

However, on Ubuntu 14.04 I am getting a 500 Internal Server Error, and messages like this in my logs:

&gt; [Wed Jul 22 10:20:19.569063 2015] [:error] [pid 1376] [client 127.0.0.1:52636] PHP Fatal error: require(): Failed opening required &#39;/var/www/html/laravel_blog/../bootstrap/autoload.php&#39; (include_path=&#39;.:/usr/share/php:/usr/share/pear&#39;) in /var/www/html/laravel_blog/index.php on line 22

Previously I&#39;ve had problems when mod_rewrite was not installed or set up properly, but I have installed it and it is not working. Changed .htaccess as well from original to this.

        +FollowSymLinks
    RewriteEngine On
    
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteRule ^ index.php [L]

I&#39;ve given access to all my folders and files inside i.e.

&gt; /var/www/html/laravel_project

I have all the necessary extensions needed for Laravel 5+ as well. Is there something left that I didn&#39;t do? 

Getting a 500 Internal Server Error (require() failed opening required path) on Laravel 5+ Ubuntu 14.04

This will change `domain.com` to `www.domain.com`:

	# Force the &quot;www.&quot;
	RewriteCond %{HTTP_HOST} !^www\.domain\.com$ [NC]
	RewriteRule ^(.*)$ http://www.domain.com/$1 [R=301,L]

How do I replace the &quot;domain&quot; part so that this works on *any* domain?

.htaccess - how to force &quot;www.&quot; in a generic way?

I would like to redirect `www.example.com` to `example.com`. The following htaccess code makes this happen:

    RewriteCond %{HTTP_HOST} ^www\.example\.com [NC]
    RewriteRule ^(.*)$ http://example.com/$1 [L,R=301]

But, is there a way to do this in a generic fashion without hardcoding the domain name?

Generic htaccess redirect www to non-www

I&#39;ve got fresh install of Apache 2.2 on my Vista machine, everything works fine, except mod rewrite.

I&#39;ve uncommented 

    LoadModule rewrite_module modules/mod_rewrite.s

but none of my rewrite rules works, even simple ones like 

    RewriteRule not_found %{DOCUMENT_ROOT}/index.php?page=404

All the rules I&#39;m using are working on my hosting, so they should be ok, so my question is, is there any hidden thing in apache configuration, that could block mod rewrite?

How to enable mod_rewrite for Apache 2.2

I have pushed my .htaccess files to the production severs, but they don&#39;t work. Would a restart be the next step, or should I check something else.

Do you have to restart apache to make re-write rules in the .htaccess take effect?

I can&#39;t figure out why my `.htaccess` header settings doesn&#39;t work.

My `.htaccess` file content:


    Header set Access-Control-Allow-Origin *
    Header always set Access-Control-Allow-Methods &quot;POST, GET, OPTIONS, DELETE, PUT&quot;
    Header always set Access-Control-Allow-Headers &quot;*&quot;
    RewriteEngine On
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteRule ^(.*)$ index.php [QSA,L]

But when I remove `Header`&#39;s and add them in `index.php` then everything works fine. 

    header(&quot;Access-Control-Allow-Origin: *&quot;);
    header(&quot;Access-Control-Allow-Methods: PUT, GET, POST, DELETE, OPTIONS&quot;);
    header(&quot;Access-Control-Allow-Headers: *&quot;);

What am i missing?

Header set Access-Control-Allow-Origin in .htaccess doesn&#39;t work

My website runs a script called -&gt; WSS wallpaper script

**My Problem** -&gt; I have been trying to force remove or add trailing slash to the end of my URL to prevent duplicated content and also to clean up my URLs.

I have tried all sorts and tried everything I could think of and loads from the interwebs but no such luck yet! It might be a quick fix but I have looked at it so much I am probably blind to something dead obvious.

So I present you with all my `.htaccess` code:

    DirectoryIndex index.php

    RewriteEngine on
    RewriteRule ^download/([0-9]+)?/([0-9]+)x([0-9]+)/([^/\.]+) image.php?id=$1&amp;width=$2&amp;height=$3&amp;cropratio=$4&amp;download=1 [L]
    RewriteRule ^file/([0-9]+)?/([0-9]+)x([0-9]+)/([^/\.]+) image.php?id=$1&amp;width=$2&amp;height=$3&amp;cropratio=$4 [L]
    RewriteRule ^preview/([0-9]+)?/([0-9]+)x([0-9]+)/([^/\.]+) wallpaper_preview.php?id=$1&amp;width=$2&amp;height=$3&amp;name=$4 [L]
    RewriteRule ^thumbnail/([0-9]+)?/([0-9]+)x([0-9]+)/([^/\.]+)/([^/\.]+)/([^/\.]+)/([^/]+) image.php?wallpaper_id=$1&amp;width=$2&amp;height=$3&amp;cropratio=$4&amp;align=$5&amp;valign=$6&amp;file=$7 [L]
    RewriteRule ^cat/([0-9]+)?/([^/\.]+)/p([0-9]+) index.php?task=category&amp;id=$1&amp;name=$2&amp;page=$3 [L]
    RewriteRule ^cat/([0-9]+)?/([^/\.]+)/([0-9a-zA-Z?-]+)/p([0-9]+) index.php?task=category&amp;id=$1&amp;name=$2&amp;sortby=$3&amp;page=$4 [L]
    RewriteRule ^cat/([0-9]+)?/([^/\.]+)/([0-9a-zA-Z?-]+)-([0-9]+) index.php?task=category&amp;id=$1&amp;sortby=$3&amp;page=$4 [L]
    RewriteRule ^cat/([0-9]+)?/([^/\.]+) index.php?task=category&amp;id=$1&amp;name=$2 [L]
    RewriteRule ^tag/([^/\.]+)/([0-9a-zA-Z?-]+)/([0-9]+) index.php?task=tag&amp;t=$1&amp;sortby=$2&amp;page=$3 [L]
    RewriteRule ^tag/([^/\.]+) index.php?task=tag&amp;t=$1 [L]
    RewriteRule ^profile/([0-9]+)?/([^/\.]+) index.php?task=profile&amp;id=$1&amp;name=$2 [L]
    RewriteRule ^profile/comments/([0-9]+)?/([^/\.]+) index.php?task=users_comments&amp;id=$1&amp;name=$2 [L]
    RewriteRule ^page/([0-9]+) index.php?task=view_page&amp;id=$1 [L]  
    RewriteRule ^register index.php?task=register [L] 
    RewriteRule ^lost-password index.php?task=lost_pass [L] 
    RewriteRule ^links index.php?task=links [L]
    RewriteRule ^news/item/([0-9]+)/([^/\.]+) index.php?task=news&amp;id=$1 [L]
    RewriteRule ^news/page([0-9]+) index.php?task=news&amp;page=$1 [L]
    RewriteRule ^members/([^/\.]+)-([^/\.]+)/page([0-9]+)? index.php?task=member_list&amp;sort=$1&amp;order=$2&amp;page=$3 [L]
    RewriteRule ^members index.php?task=member_list [L]
    RewriteRule ^messages index.php?task=messages [L]
    RewriteRule ^submit index.php?task=submit [L]
    RewriteRule ^search/([^/\.]+) index.php?task=search&amp;q=$1 [L]
    RewriteRule ^search index.php?task=search [L]
    RewriteRule ^submit index.php?task=submit [L]
    RewriteRule ^r-([0-9]+)?-([0-9]+)? go.php?id=$1&amp;ref=$2 [L]
    RewriteRule ^r-([0-9]+)? go.php?id=$1 [L]
    RewriteRule ^([^/\.]+)/([0-9]+)/([^/\.]+) index.php?task=view&amp;id=$2&amp;name=$3 [L]
    RewriteRule ^news/([^/\.]+) index.php?task=news&amp;name=$1 [L]
    RewriteRule ^profile/([^/\.]+) index.php?task=profile&amp;name=$1 [L]
    RewriteRule ^news index.php?task=news [L]
    RewriteRule ^page/([^/\.]+) index.php?task=view_page&amp;name=$1 [L]  
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule ^([^/\.]+)/([0-9a-zA-Z&#39;?-]+)/([0-9]+) index.php?task=category&amp;name=$1&amp;sortby=$2&amp;page=$3 [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule ^([^/\.]+)/([^/\.]+) index.php?task=view&amp;name=$2 [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule ^([^/\.]+) index.php?task=category&amp;name=$1 [L]
    
    
    ## www reslove ##
    RewriteCond %{HTTP_HOST} !^www\.
    RewriteRule ^(.*)$ http://www.%{HTTP_HOST}/$1 [R=301,L]
    ## www reslove ##
    
    ## index reslove ##
    Options +FollowSymLinks
    RewriteCond %{THE_REQUEST} ^.*/index\.php
    RewriteRule ^(.*)index.php$ http://www.epicwallpaper.net/$1 [R=301,L]
    ## index reslove ##

Htaccess: add/remove trailing slash from URL

I can&#39;t seem to force https on the free usage tier of elastic beanstalk.

I have tried the following suggestion at https://stackoverflow.com/questions/6858492/how-to-force-https-on-amazon-elastic-beanstalk-without-failing-the-health-check

Using this Apache rewrite rule

    RewriteEngine On
    RewriteCond %{HTTP:X-Forwarded-Proto} !https
    RewriteCond %{REQUEST_URI} !^/status$ 
    RewriteCond %{REQUEST_URI} !^/version$ 
    RewriteCond %{REQUEST_URI} !^/_hostmanager/ 
    RewriteRule . https://%{SERVER_NAME}%{REQUEST_URI} [L,R]

When I try that, http requests do not get redirected to https as I would like. Instead, the http page loads normally. I&#39;ve also tried to use the X-Forwarded-Port header with the same result. 

I&#39;ve also tried the following rewrite rule

    RewriteCond %{SERVER_PORT} 80
    RewriteRule . https://%{SERVER_NAME}%{REQUEST_URI} [L,R]

And this rule causes a redirect loop. So it would seem that the apache rewrite rules don&#39;t pick up the Elastic Load Balancer headers X-Forwarded-Port and  X-Forwarded-Proto, but also a redirect loop isn&#39;t what I am going for either.

Please help. I am new to AWS, Elastic Beanstalk, and not very familiar with Apache rules. I am not too sure where to go from here. Thanks.

How to force https on elastic beanstalk?

I am trying to set Apache environment variables (for use in PHP) with the `[E=VAR:VAL]` flag on RewriteRule rules in an .htaccess file.

I have already discovered the variables are accessed in PHP as server variables `$_SERVER` rather than `$_ENV` (which makes a certain amount of sense). However, my problem is for some rules the `[E=VAR:VAL]` flag works as expected and I end up with a variable `$_SERVER[&#39;VAR&#39;]` but for other rules I end with a variable `$_SERVER[&#39;REDIRECT_VAR&#39;]` or `$_SERVER[&#39;REDIRECT_REDIRECT_VAR&#39;]`, etc

A. What causes an environment variable set in Apache using the `[E=VAR:VAL]` flag to get renamed by having &quot;REDIRECT_&quot; prepended to the variable name?

B. What can I do to make sure I end up with an Environment Variable with an unchanged name so I can access it in PHP as `$_SERVER[&#39;VAR&#39;]` without having to resort to checking for variations of the variable name having one of more instances of &quot;REDIRECT_&quot; prepended to it?

*Partial solution found*. Adding the following to the start of the rewrite rules recreates the original ENV:VAR on each redirect (as well as leaving the REDIRECT_VAR versions there) if they&#39;re needed:
 
    RewriteCond %{ENV:REDIRECT_VAR} !^$
    RewriteRule .* - [E=VAR:%{ENV:REDIRECT_VAR}]



When setting environment variables in Apache RewriteRule directives, what causes the variable name to be prefixed with &quot;REDIRECT_&quot;?

I&#39;m trying to have the modrewrite rules skip the directory `vip`. I&#39;ve tried a number of things as you can see below, but to no avail. 

    # BEGIN WordPress
    &lt;IfModule mod_rewrite.c&gt;
    RewriteEngine On
    RewriteBase /
    #RewriteRule ^vip$ - [PT]
    RewriteRule ^vip/.$ - [PT]
    #RewriteCond %{REQUEST_URI} !/vip 
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    &lt;/IfModule&gt;
    # END WordPress

How do I get modrewrite to entirely ignore the `/vip/` directory so that all requests pass directly to the folder?

### Update:

As points of clarity: 

  - It&#39;s hosted on Dreamhost
  - The folders are within a wordpress directory
  - the /vip/ folder contains a webdav .htaccess etc (though I dont think this is important

How do I ignore a directory in mod_rewrite?

I&#39;m using Apache and I have a sample web folder on my **Local Host**, like:   

          http://localhost/test/

---
Files in the `test` folder:   
  
         index.html  
         sample.jpg  
         .htaccess  

---
Sample source of `index.html`:

    &lt;html&gt;
      &lt;body&gt;
        &lt;img src=&quot;sample.jpg&quot; /&gt;
      &lt;/body&gt;
    &lt;/html&gt;

When I run the website at `http://localhost/test/`, it will simply show the image `sample.jpg&#39; on the page.

---
**Problem:**

- I want to prevent the image showing as `http://localhost/test/sample.jpg` directly in the url bar.

**Note:** *I found that the solutions below work when tested on every browser **except Firefox**.*

How to prevent a file from direct URL Access?

All I wanted to do today was to write a redirect rule to a subfolder, e.g.:
You enter the URL: **example.com** and you get redirected to **example.com/subfolder**

Such a simple wish. I tried to find a solution on the internet. The internet told me to add an **.htaccess** file in the htdocs root with:

    RewriteEngine on
    RewriteCond %{HTTP_HOST} ^example\.com$
    RewriteRule (.*) http://www.example.com/$1 [R=301,L]
    RewriteRule ^$ subfolder [L]

I did this. But no success obviously, they didn&#39;t told me I had to uncomment the module in **httpd.conf**:

    LoadModule rewrite_module modules/mod_rewrite.so

So I did this too. No success again. They didn&#39;t told me I had to change my **httpd.conf** so that the **.htaccess** file would be enabled:

    &lt;Directory /&gt;
        Options FollowSymLinks
        AllowOverride None
        Order deny,allow
        Deny from all
    &lt;/Directory&gt;
    
    DocumentRoot &quot;c:/Apache24/htdocs&quot;
    &lt;Directory &quot;c:/Apache24/htdocs&quot;&gt;
        Options Indexes FollowSymLinks
        AllowOverride All
        Require all granted
    &lt;/Directory&gt;

Again no success, because I get this error when entering the URL:

&gt; Forbidden You don&#39;t have permission to access / on this server.

Now I&#39;m stuck and I couldn&#39;t find any more solutions on the internet. I&#39;m just running Apache 2.4 on my Windows 7 machine, for private reasons.

Forbidden You don&#39;t have permission to access / on this server

This seems to be a non-issue for many people (read: I can&#39;t find an answer), but I would like to update the following htaccess code to not only remove the &#39;www&#39; from the URL, but also any sub-directories that are accessed.

    RewriteEngine on
    RewriteCond %{HTTP_HOST} ^www\.(.+)$ [NC]
    RewriteRule ^(.*)$ http://%1/$1 [R=301,L]

With this, http://www.example.com/any/ resolves fine, but I want it to redirect to http://example.com/any/ as with the root.

.htaccess Remove WWW from URL + Directories

I am trying to learn some `.htaccess` tricks. I came across the `RewriteBase` directive but could not get it to work properly. 

I wonder what this directive does specifically and how to use it. There have been some discussions about `RewriteBase` in StackOverflow and the Apache documentation but still, I could not get a clear answer to my question.

Could someone show me a simple but effective example where `RewriteBase` can be used?

What does RewriteBase do and how to use it?

I have the following htaccess code:

    &lt;IfModule mod_rewrite.c&gt;
    
    RewriteEngine On
    RewriteCond !{HTTPS} off
    RewriteRule ^(.*)$ https://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
    RewriteCond %{HTTP_HOST} !^www\.
    RewriteRule ^(.*)$ https://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
    
    &lt;/IfModule&gt;

I want my site to be redirected to `https://www.` with HTTPS, and enforcing the `www.` subdomain,
but when I access `http://www.` (without HTTPS), it does not redirect me to `https://www` with HTTPS.


All Mod Rewrite Solutions on Gang of Coders

Total of 40 Mod Rewrite Solutions