Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (nike.apache.org: domain of tevans.uk@googlemail.com
 designates 209.85.220.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <DAE3CB30-AA3F-4B09-B691-1786AABC8B6A@bergersen.no>
References: <F550B14E-C75B-4FA3-B0AD-42FDB879DE23@bergersen.no>
	<CAFHbX1+=OrX3+9uMASGWdRxH46gnowunk39jMAdEBiaAWO9S3w@mail.gmail.com>
	<DAE3CB30-AA3F-4B09-B691-1786AABC8B6A@bergersen.no>
Date: Wed, 17 Aug 2011 17:03:22 +0100
Message-ID: 
 <CAFHbX1+q4uPkoFhrYE_0hHhaZWyDNed8+-_cV3AtRkrsxjoLaw@mail.gmail.com>
From: Tom Evans <tevans.uk@googlemail.com>
To: users@httpd.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [users@httpd] ServerAlias and RewriteRule

On Wed, Aug 17, 2011 at 4:56 PM, Richard Taubo <ort@bergersen.no> wrote:
> Thanks!
>
> So to be 110% clear, since this is kind of important to get right :-)
>
> 1) So either this =E2=80=93 leave off the / from the end of the rewritten=
 URL:
> =C2=A0 =C2=A0 =C2=A0 =C2=A0RewriteRule ^(.*)$ http://www.example.com$1 [L=
,R=3D301]
>
> 2) Or this =E2=80=93 not capture the slash from the original URL:
> =C2=A0 =C2=A0 =C2=A0 =C2=A0RewriteRule ^/(.*)$ http://www.example.com/$1 =
[L,R=3D301]
>
> 3) But not this =E2=80=93 as was the alternative I started out with (the =
browsers I have tested
> do not seem mind, but the rewrite logs shows that an extra slash is added=
):
> =C2=A0 =C2=A0 =C2=A0 =C2=A0RewriteRule ^(.*)$ http://www.example.com/$1 [=
L,R=3D301]
>
>>>
>>> Question 2)
>>> Is the method I use to alias "example.com" with "www.example.com",
>>> a good way to set up a ServerAlias in my httpd.conf file, or are there =
better ways?
>>> My current method, as mentioned above, is:
>>> =C2=A0 =C2=A0ServerName www.example.com
>>> =C2=A0 =C2=A0ServerAlias example.com
>>> =C2=A0 =C2=A0RewriteEngine On
>>> =C2=A0 =C2=A0RewriteCond %{HTTP_HOST} ^example\.com$ [NC]
>>> =C2=A0 =C2=A0RewriteRule ^(.*)$ http://www.example.com$1 [L,R=3D301]
>>>
>>
>> It's fine. Some people prefer to have the host name canonicalization
>> occur in a separate vhost, as this separates the configuration for the
>> 'correct' hostname from the configuration for 'incorrect' hostnames.
>
> So instead of:
> <VirtualHost *:80>
> =C2=A0 ....
> =C2=A0 ServerName www.example.com
> =C2=A0 ServerAlias example.com
> =C2=A0 RewriteEngine On
> =C2=A0 RewriteCond %{HTTP_HOST} ^example\.com$ [NC]
> =C2=A0 RewriteRule ^(.*)$ http://www.example.com$1 [L,R=3D301]
> </VirtualHost>
>
> They would rather create two VirtualHosts like this instead:
> <VirtualHost *:80>
> =C2=A0 ....
> =C2=A0 ServerName www.example.com
> =C2=A0 ....
> </VirtualHost>
>
> <VirtualHost *:80>
> =C2=A0 ....
> =C2=A0 ServerName example.com
> =C2=A0 RewriteEngine On
> =C2=A0 RewriteRule ^(.*)$ http://www.example.com$1 [L,R=3D301]
> =C2=A0 ....
> </VirtualHost>
>
>
> Appreciate your answers!
>
> Richard Taubo

Yep, precisely. Personally I do option 2 for the first question, and
multiple vhosts for the second question (but a single vhost is also
perfectly fine).

Cheers

Tom

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org