Comments on: Rewrite domain.com to www.domain.com using htaccess in Apache

By: Gerd Naschenweng

Gerd Naschenweng — Wed, 04 Jan 2012 16:24:10 +0000

Thanks for the snippet – works as intended.

By: Hal_9000_ai

Hal_9000_ai — Fri, 13 May 2011 17:04:00 +0000

Oh and, if it’s good enough for FACEBOOK.COM which re-routes to http://www.facebook.com, THEN there is obvious reason for it. Let’s see, Aaron Toponce versus $9 Billion Valued Company. Let the masses decide, what is redundant

By: Hal_9000_ai

Hal_9000_ai — Fri, 13 May 2011 17:01:00 +0000

It’s not silly nor redundant if you are the one running and owning the server and the dedicated IP address running to it. The choice to force content to be served from one NameHost is a valid one, especially if you Host several domains. Anyone that has worked with servers and DNS knows that anyone can point their domain to your Dedicated IP address, and without such technology as mod_rewrite available at the domain root level, someone can essentially server your content under their domain name in a web browser. It is common practise with Domain Harvesters. Anyways, my point is that what is absurd and/or redundant to someone, usually means it the reasoning may be over their head. If we talking about apples and we’re looking at an Macintosh Apple and a Granny Smith Apple, you just see Apples, I see apples and computers and my Grandma Smith. Difference is really, I OWN the apples , while you’re just talkin abot it ;)

By: bmatthewshea

bmatthewshea — Mon, 04 Apr 2011 00:29:00 +0000

Not quite there..
needs to a match true condition -> “!”:

RewriteCond %{HTTP_HOST} !^(www.example.com)?$ [NC]

(added ‘!” and [NC])

By: g1smd

g1smd — Mon, 03 May 2010 06:45:00 +0000

If the idea is to redirect all non-canonical forms of the hostname to exactly http://www.example.com/ beware that your standard code does not redirect www requests with an appended port number http://www.example.com:80/ and does not redirect www requests with an appended period http://www.example.com./ either. This leaves a site open to Duplicate Content indexing if malicious links are pointed at non-canonical URLs.

The fix is very simple, a minor edit to the originally suggested code:

Options +FollowSymLinks
RewriteEngine on
RewriteCond %{HTTP_HOST} ^(www.example.com)?$
RewriteRule (.*) http://www.example.com/$1 [R=301,L]

Additionally, the ( ) ? syntax ensures that HTTP/1.0 requests – which have a blank HOST header – do not cause an infinite redirection loop.

By: Anonymous

Anonymous — Thu, 25 Feb 2010 08:08:00 +0000

YOU are just silly and redundant.

By: Aaron Toponce

Aaron Toponce — Fri, 13 Feb 2009 12:08:00 +0000

Why? WWW (World Wide Web) was incorporated to force browsers to use the HTTP protocol when the Internet was new. Now all modern browsers default to HTTP by default, so what is the point of WWW? Mail servers certainly don’t require you to use ‘address@mail.yourdomain.com’, so why should the web be any different?

No, sites should be redirecting the ‘www’ subdomain to the TLD without ‘www’. See http://no-www.org for more info. Class B compliance should be the goal of every site owner. Forcing WWW is just silly and redundant.

By: escorts

escorts — Sun, 04 Jan 2009 04:50:00 +0000

Thanks i will try