htaccess is there a better way

[jonniejoejonson]

I have the following in an htaccess file to prefix a www. incase a user has left it blank...

 

RewriteCond %{HTTP_HOST} ^mysite\.org$ [NC]

RewriteRule ^(.*)$ http://www.mysite.org/$1 [L,R=301]

 

Is there another way of doing this, or a way to include the possibilty of needing to rewrite to https://

Kind regards J

 

 

 

[requinix]

That's pretty much how it's done - nothing wrong with it. Not much room to do it differently.

 

 

FWIW, here's what I do:

RewriteCond %{HTTP_HOST} !^www.example.com$
RewriteRule ^ //www.example.com%{REQUEST_URI} [L]

The differences are:

1. Mine checks whether the hostname is not what I want, as opposed to whether it is what I don't want.

2. I don't match the URL in the RewriteRule because it doesn't have to - %{REQUEST_URI} gives the same information.

3. It doesn't include the "http:" - redirecting to "//www.example.com" will keep the same protocol (http: vs https:) but change everything else.

 

With that pattern, yours would look like

RewriteCond %{HTTP_HOST} !^www.mysite.org$
RewriteRule ^ //www.mysite.org%{REQUEST_URI} [L]

[jonniejoejonson]

requinix thats what im talking about.. thanks for that. regards J

[jonniejoejonson]

requinix, i think i was a little hasty with my reply, becuase when i use your code, i get..

 

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

 

IM guessing there is something ary... your continued support would be much appreciated.. kind regards J

[requinix]

I'm wondering if the // is causing the problem. Never tried it before. Maybe adding a [R] would resolve any ambiguities.

 

Anyway, what does Apache's error log say?