ansaurus

Question

Answer 1

+1 A:

How about this rewrite rule?

RewriteEngine On 
RewriteCond %{HTTP_HOST} ^www.site.com$ [NC]
RewriteRule ^(.*)$ http://site.com/$1 [R=301,L]

Colin Pickard 2009-06-03 15:00:04

this would not work for me, as I use SSL also.

Mike Curry 2009-06-03 15:05:40

In fact the reason I want this to work is so that https://www.site.com gets changed to https://site.com

Mike Curry 2009-06-03 15:06:16

Answer 2

A:

Try this little trick:

RewriteEngine on
RewriteCond %{HTTPS}s/%{HTTP_HOST} ^(on(s)|[^/]+)/www\.(.+) [NC]
RewriteRule ^ http%2://%3%{REQUEST_URI} [L,R=301]

Gumbo 2009-06-03 15:08:04

Answer 3

A:

Or this:

RewriteEngine on
RewriteCond %{HTTP_HOST} ^www\.(.*) [NC]
RewriteCond %{HTTP_PORT} =443
RewriteRule (.*) https://%1/$1 [L,R=301]
RewriteCond %{HTTP_HOST} ^www\.(.*) [NC]
RewriteRule (.*) http://%1/$1 [L,R=301]

chaos 2009-06-03 15:54:09

Answer 4

+5 A:

RewriteEngine on
RewriteCond %{HTTPS} =on
RewriteCond %{HTTP_HOST} ^www\.(.*) [NC]
RewriteRule ^(.*)$ https://%1$1 [L,R=301]
RewriteCond %{HTTP_HOST} ^www\.(.*) [NC]
RewriteRule ^(.*)$ http://%1$1 [L,R=301]

Two slight changes from other answers:

The %1 backreference in the RewriteRule takes from the last matched RewriteCond, so the check for HTTPS must come before the check for www in the host name.

%1$1 doesn't need a slash in the middle, because you'll get that from the path match in the RewriteRule.

One final piece of advice: since you have control over the VirtualHost sections in the main Apache configuration, it would be faster to put these rules there. Additionally, you'd split them, putting the plain HTTP one in *:80 and HTTPS in *:443, meaning you can remove the RewriteCond %{HTTPS} =on entirely, since it would only apply to requests intended for that virtual host.

Steve Madsen 2009-06-05 19:47:58

My rewrite engine doesn't seem to work, thats what my problem is. :(

Mike Curry 2009-06-06 01:57:57

anyway to test if rewrite is working what so ever with a simple test, or even see if my .htaccess is being picked up?

Mike Curry 2009-06-06 01:58:36

Vinko is right; this isn't the best way to debug. I'm willing to spend a bit of time debugging this with you over IM. Contact me via my web site (check my profile) if you're interested.

Steve Madsen 2009-06-08 14:21:07

sounds good, thanks steve.

Mike Curry 2009-06-08 20:21:28

Answer 5

+2 A:

It sounds like you are saying your mod_rewrite isn't working at all. Here's a few things to try:

You said it was enabled, but the provided info:

root@s15348441:/etc/apache2/mods-available# more rewrite.load
LoadModule rewrite_module /usr/lib/apache2/modules/mod_rewrite.so

Just shows it under the "mods-available" folder, which means it is installed, but not necessarily turned on. If it is enabled, it should be symlinked under the "mods-enabled" folder (you'll need to a2enmod it if it isn't there)

If it is enabled, and has been restarted, the next step would be to enable the logging feature of mod rewrite; this is an excellent tool for debugging.

Edited to add: You could move the mod rewrite to the base config. If you have access to it, it's recommended to put your config in the base section anyway (see here). It's also easier to determine if it has anything to do with mod_rewrite (like your allowoverrides are getting confused) or it's purely an htaccess problem.

Keeping on: (@Vinko Vrsalovic is right about this being a hard debugging medium) If you moved it to your base config and it still didn't work, then we're onto something, you've eliminated .htaccess portion. You should post the new config, along with the rewrite logs. If you didn't get a rewrite log, then 1) your config hasn't been loaded (need to restart apache) or 2) you aren't hitting the config section you think you are

Todd Gardner 2009-06-07 03:05:10

I don't think my .htaccess is being read at all ...

Mike Curry 2009-06-07 11:59:52

I'll give it a shot today, thanks :D

Mike Curry 2009-06-07 17:32:24

Never worked. I am stumped

Mike Curry 2009-06-08 12:30:05

Answer 6

+4 A:

You can easily test if your htaccess is being read or not:

Put garbage in it, like:
```
Options +FollowSymLinks
This is garbage
RewriteEngine on
RewriteCond %{HTTP_HOST} ^www\.(.*) [NC]
RewriteRule (.*) //%1/$1 [L,R=301]
```
If you get a 500 error (Internal Server Error) then it IS being read.

If it is, you should enable the RewriteLog in the main server configuration (not in .htaccess) like this:
```
RewriteLog "/tmp/rewrite.log"
RewriteLogLevel 9
```

And then check the file /tmp/rewrite.log to see what's happening. Report back with results.

(Stack Overflow isn't a good debugging medium, IRC is better for that, try #[email protected])

Good luck.

Vinko Vrsalovic 2009-06-07 13:32:36

RewriteLogLevel 9 will generate way too much noise to be of much use. 2 or 3 is plenty to understand if the rules are being processed, or why they aren't.

Steve Madsen 2009-06-08 14:12:23

I disagree, I routinely use level 9 and, while verbose, I find it useful.

Vinko Vrsalovic 2009-06-08 14:29:24

RewriteLog should definitely help in tracking any find of problems. And high output can help track problems easily.

Ivan Vučica 2009-06-08 22:36:13

Answer 7

+1 A:

As Vinko said,

RewriteLog "/tmp/rewrite.log"
RewriteLogLevel 9

and look at that file.

Otherwise, here's the code we're using to redirect from zirconium.zrs.hr/~zatemas to zatemas.zrs.hr:

RewriteEngine on

# For sites running on a port other than 80
RewriteCond %{HTTP_HOST}   !^zatemas\.zrs\.hr [NC]
RewriteCond %{HTTP_HOST}   !^$
RewriteCond %{SERVER_PORT} !^80$
RewriteRule ^/~zatemas/(.*)         http://zatemas.zrs.hr:%{SERVER_PORT}/$1 [L,R]

# And for a site running on port 80
RewriteCond %{HTTP_HOST}   !^192\.168\.1\.24 [NC]
RewriteCond %{HTTP_HOST}   !^zatemas\.zrs\.hr [NC]
RewriteCond %{HTTP_HOST}   !^$
RewriteRule ^/~zatemas/(.*)         http://zatemas.zrs.hr/$1 [L,R]

I've seen around the web that people detect HTTPS primarily by looking if the port is 443. mod_rewrite documentation says there should be a variable HTTPS set to on or off, appropriately - I presume you do RewriteCond %{HTTPS} ^on$ to test if it's on.

Also watch out: .htaccess directives for URL rewriting do not work nicely if you're accessing files in user's home directory - for example site.com/~username/. That should not bother you according to your scenario, though. My code above is placed in main server config, under the VirtualHost section(more precisely, in /etc/apache2/sites-enabled/000-default, but that's debian specific and gets merged in main config).

Ivan Vučica 2009-06-08 22:48:46

Thanks for the help, its now working :D

Mike Curry 2009-06-11 13:02:45

No sweat, just helping where I can :-)

Ivan Vučica 2009-06-14 12:09:11

Answer 8

A:

First of all, check to make sure that mod_rewrite is actually loading. You can do that with apache2ctl:

[root@host ~]# apache2ctl -t -D DUMP_MODULES 2>&1 |grep rewrite
rewrite_module (shared)

If it is not, then you might have to run 'a2enmod rewrite'

Next, test to see if your .htaccess file is even being read. I typically do this by putting some garbage inside the .htaccess file, then loading a page in that directory in my browser and verifying that I get a 500 error

On a side note, as others have mentioned, if you have the ability to modify your Apache config directly, you should put the Rewrite Rules there instead of in the .htaccess file as it is less efficient. Apache has to first decide in which directory to look for the .htaccess file, then read it, then perform the rewrites. If the RewriteRules are specified inside your VirtualHost directives, then it can do them before finding the .htaccess file. Specifying them inside your VirtualHost also means that it doesn't matter if your .htaccess file is being read. It would look something like this:

 <VirtualHost *:80>
    .... existing config ....
    RewriteEngine on
    RewriteCond %{HTTP_HOST} ^www\.(.*) [NC]
    RewriteRule (.*) http://%1/$1 [L,R=301]
 </VirtualHost>
 <VirtualHost *:443>
    .... existing config ....
    RewriteEngine on
    RewriteCond %{HTTP_HOST} ^www\.(.*) [NC]
    RewriteRule (.*) https://%1/$1 [L,R=301]
 </VirtualHost>

Brandon 2009-06-10 17:36:59

Answer 9

A:

What are the file permissions for your .htaccess file?

I'm not sure, but I think it needs to be 644.

Dave 2009-06-10 18:03:13

ansaurus

tags:

views:

answers:

.htaccess not working (mod_rewrite)

related questions