[ale] redirect rule for RHEL5?

[Lightner, Jeff]

Registrar isn't the issue - that just points the domains to our DNS
servers which points them to this web server here.   Nothing in DNS
specifies ports for sites - that's all done in web setup.

 

My last post was basically just a gripe about the lack of documentation
for Concrete5.  It gives you a Readme that list 6 steps most of which
boil down to "use your web hosting company's utilities to do some web
magic" rather than actually talking about how Apache itself should be
configured.   We're using this software because of a 3rd party and they
aren't giving us much guidance.  Not being a web admin myself I know
just enough to be dangerous.  (I am our DNS admin though so I'm sure I'm
correct on the first line.)

 

________________________________

From: ale-bounces at ale.org [mailto:ale-bounces at ale.org] On Behalf Of
wolf at wolfhalton.info
Sent: Tuesday, August 03, 2010 10:56 AM
To: Atlanta Linux Enthusiasts - Yes! We run Linux!
Subject: Re: [ale] redirect rule for RHEL5?

 

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.

-----Original Message-----
From: Lightner, Jeff <jlightner at water.com
<mailto:%22Lightner,%20Jeff%22%20%3cjlightner at water.com%3e> >
Reply-to: Atlanta Linux Enthusiasts - Yes! We run Linux! <ale at ale.org>
To: Atlanta Linux Enthusiasts - Yes! We run Linux! <ale at ale.org
<mailto:Atlanta%20Linux%20Enthusiasts%20-%20Yes!%20We%20run%20Linux!%20%
3cale at ale.org%3e> >
Subject: Re: [ale] redirect rule for RHEL5?
Date: Tue, 3 Aug 2010 10:31:04 -0400

 
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 http://hostname  and http://hostname/orders.
 
-----Original Message-----
From: ale-bounces at ale.org [mailto:ale-bounces at ale.org] 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 <terrorpup at gmail.com> 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.
 
Proud partner. Susan G. Komen for the Cure.
 
Please consider our environment before printing this e-mail or attachments.
----------------------------------
CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you.
----------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.ale.org/pipermail/ale/attachments/20100803/8d2f666b/attachment.html