<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.28.3">
</HEAD>
<BODY>
How about leaving the orders.domain.com virtual domain on port 80 and setting the concrete.domain.com to listen only on port 81 or 80 on the internal NIC. Virtual servers override the apache2.conf don't they? Then on your nameservers, make an alias. Even godaddy lets you do that sort of redirect. Who is your registrar (rhetorical question) ask them if they can help you set it up.<BR>
<BR>
-----Original Message-----<BR>
<B>From</B>: Lightner, Jeff <<A HREF="mailto:%22Lightner,%20Jeff%22%20%3cjlightner@water.com%3e">jlightner@water.com</A>><BR>
<B>Reply-to</B>: Atlanta Linux Enthusiasts - Yes! We run Linux! <ale@ale.org><BR>
<B>To</B>: Atlanta Linux Enthusiasts - Yes! We run Linux! <<A HREF="mailto:Atlanta%20Linux%20Enthusiasts%20-%20Yes!%20We%20run%20Linux!%20%3cale@ale.org%3e">ale@ale.org</A>><BR>
<B>Subject</B>: Re: [ale] redirect rule for RHEL5?<BR>
<B>Date</B>: Tue, 3 Aug 2010 10:31:04 -0400<BR>
<BR>
<PRE>
Can one specify the inernal NICs IP and external NICs IP in the 2
different virtual hosts both using port 80? I thought that was the
point in virtual hosts.
I realize now that I misspoke below. On the external interface I want
to get to it via the domains specified earlier. On the internal I don't
mind getting to it via <A HREF="http://hostname">http://hostname</A> and <A HREF="http://hostname/orders">http://hostname/orders</A>.
-----Original Message-----
From: <A HREF="mailto:ale-bounces@ale.org">ale-bounces@ale.org</A> [<A HREF="mailto:ale-bounces@ale.org">mailto:ale-bounces@ale.org</A>] On Behalf Of
James Sumners
Sent: Tuesday, August 03, 2010 10:12 AM
To: Atlanta Linux Enthusiasts - Yes! We run Linux!
Subject: Re: [ale] redirect rule for RHEL5?
I don't think a simple rewrite rule is going to work. His web server
is listening on both interfaces, but he wants requests to the external
interface to always go to "example.com/orders" when the request is
actually for "example.com/".
One way to do this would to use virtual hosts. Have "example.com" on
port 80 and "example.com/orders" on port 81. That would let you use a
firewall rule to route external traffic to the correct application
(port 81) without having to specify a different port. Only trouble is
your internal users would have to specify port 81 if they wanted to
hit the "/orders" page.
On Tue, Aug 3, 2010 at 9:53 AM, Chuck Payne <<A HREF="mailto:terrorpup@gmail.com">terrorpup@gmail.com</A>> wrote:
> Do a search on Rewrite URI, that is the direct you need to go in. I
> don't have my notes with me. But take a look at that, it should be
> what you need, the other thing you could does create alias for orders
> have it pointing to the directory CubeCart stuff, to me that ould be
> easier that rewrite rule.
</PRE>
<BR>
</BODY>
</HTML>