Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We have a central httpd.conf and we include confs for various virtual hosts. Until today, we didn't really have a need for "www.subdomain.site.com" domains, only "subdomain.site.com." Now we do, so I am trying to figure out which of these two approaches is better:

[1]. Use a Rewrite:

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

OR

[2]. Use ServerAlais:

    <VirtualHost 111.22.33.44:80>
    ServerName subdomain.site.com
    ServerAlias www.subdomain.site.com
    Include conf/subdomain.conf
    </VirtualHost>

I imagine there is more processing on the Rewrite, but unsure of how ServerAlias would behave in this mix. Does one get better SEO foo than the other?

Any and all ideas welcome!

Thanks,

KM

share|improve this question
    
In the rewrite, the RewriteCond needs to go first, and the variable should be %{HTTP_HOST}. –  David Z Jun 28 '10 at 20:39
1  
@DavidZaslavsky I fixed that –  cstamas Oct 15 '12 at 16:04

2 Answers 2

up vote 1 down vote accepted

I would probably do both. With something like:

<VirtualHost 111.22.33.44:80>
  ServerName subdomain.site.com

  #Using Wildcard: might as well handle any variation
  #such as ww.subdomain.site.com (remember to set this in DNS too)
  ServerAlias *.subdomain.site.com

  RewriteEngine On

  #Change all variations to the Canonical hostname for SEO.
  RewriteCond %{HTTP_HOST} !^subdomain.site.com [NC]
  RewriteRule ^/(.*)$ http://subdomain.site.com/$1 [R=301]
  Include conf/subdomain.conf 
</VirtualHost>

Note: the solution by David Zaslavsky above does more or less the same thing, but this way you don't have to do a separate VirtualHost section for each subdomain.

share|improve this answer
    
Dave and Matthew, thank you both for your suggestions. Between the two suggestions I have more than enough to get going in the right direction! –  KM. Jul 2 '10 at 13:52

I'd imagine the rewriting solution gets better SEO-foo (nice term :-P) since it's usually considered best to have one canonical domain that everybody gets sent to for a particular set of content. In other words, having two different domains that produce the same results from the server can split your site rankings between the two domains, reducing the value of each. (Google allows you to specify a canonical domain using its Webmaster Tools, but that only works on Google)

I think you can actually use a Redirect here, i.e.

<VirtualHost *:80>
    ServerName www.subdomain.site.com
    Redirect permanent / http://subdomain.site.com/
</VirtualHost

That is less computationally intensive than invoking mod_rewrite.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.