Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (herse.apache.org: domain of jslive@gmail.com designates
 209.85.132.249 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=CXkVVP0RkLx0ox/ImV3JdLJhYJEtJfUXwLgsm6bsBMss1hAB//5rSwwLdKunUxpjfXtqm/DYMkqSIiaWYLAmr6E8pEV+HDtLAjOPcS+lP67jUk+mVFWkiBs9nZyQ+N8NztXiEZehzRfVJSI5J/yl8msIGq88W0v/mt9JeNVZu8Y=
Message-ID: <e498c1660705061317w93a3b28se29e59f572925365@mail.gmail.com>
Date: Sun, 6 May 2007 16:17:22 -0400
From: "Joshua Slive" <joshua@slive.ca>
Sender: jslive@gmail.com
To: users@httpd.apache.org
In-Reply-To: <15765.37768.qm@web606.biz.mail.mud.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <250019.34554.qm@web614.biz.mail.mud.yahoo.com>
	 <15765.37768.qm@web606.biz.mail.mud.yahoo.com>
Subject: Re: [users@httpd] single webpage redirect

On 5/6/07, Dave Henderson <dhenderson@digital-pipe.com> wrote:
> Guys,
>
>     I have another question.  This one is just to maintain uniformity and is
> not a must.  I adjusted the apache server that doesn't contain the user
> database (site2) to use the database at site1 by redirecting the login.html
> to login.server.com.  This is working just fine when people access the
> site2's apache server.  If the people use the site1 apache server, no
> redirection is required (obviously), but I would like the url to remain
> consistant between the two sites when people access the webpage.  Is there a
> way to mask the url on site1's apache server to read as login.server.com
> instead of the actual server name.  I already have dns setup and working
> correctly (since site2 works fine), I would just like this to be uniform.

Just use a normal name-virtual-vhost configuration to setup
login.server.com as a virtual host on the site2 machine (evidently
sharing all the same configuration as site2). Then do a redirect from
the site2 virtualhost to the login virtual host, just as you did on
site1.

Joshua.

---------------------------------------------------------------------
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