You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modules-dev@httpd.apache.org by Sam Carleton <sc...@miltonstreet.com> on 2009/06/02 14:45:03 UTC

do I need a custom proxy?

I do develop Apache Modules which is why I thought to ask this question
here...

I run a micro ISV out of my home and I only have one external IP address.  I
need to have some services on Apache and others on IIS.  How would I pull
this off since I only have one external IP address?  My thought is create a
custom mod_proxy that will redirect some URL's from the public facing Apache
to the internal IIS.  Is this the correct approach or is there an approach
that does not require actual development?

Sam

RE: do I need a custom proxy?

Posted by "Houser, Rick" <Ho...@aoins.com>.
Not entirely.  You could also either use a wildcard certificate
(although IE doesn't support dots in the wildcard portion) or
exclusively support the vhosts on modern browsers running TLS.
 


Thanks,

Rick Houser
Auto-Owners Insurance
Systems Support
(517)703-2580


 


________________________________

	From: Sam Carleton [mailto:scarleton@gmail.com] 
	Sent: Tuesday, June 02, 2009 9:44 AM
	To: modules-dev@httpd.apache.org
	Subject: Re: do I need a custom proxy?
	
	
	I did not mention that I am only interested in HTTPS, not HTTP.
It is my understanding that virtual host's don't work for HTTPS, is this
correct?
	
	Sorin Manolache wrote: 

		On Tue, Jun 2, 2009 at 14:45, Sam Carleton
<sc...@miltonstreet.com> <ma...@miltonstreet.com>  wrote:
		  

			I do develop Apache Modules which is why I
thought to ask this question
			here...
			
			I run a micro ISV out of my home and I only have
one external IP address.  I
			need to have some services on Apache and others
on IIS.  How would I pull
			this off since I only have one external IP
address?  My thought is create a
			custom mod_proxy that will redirect some URL's
from the public facing Apache
			to the internal IIS.  Is this the correct
approach or is there an approach
			that does not require actual development?
			    

		
		Can't you create two virtual hosts or two locations on
your apache,
		one of them handling requests and the other forwarding
them to IIS?
		
		Something like
		
		<VirtualHost *>
		ServerName apache.my-domain.org
		</VirtualHost>
		<VirtualHost *>
		ServerName iis.my-domain.org
		ProxyPass / http://internal-IP-of-IIS-server/
		</VirtualHost>
		
		and you register apache.my-domain.org and
iis.my-domain.org as having
		the same IP address in the authoritative nameserver of
my-domain.org.
		
		or
		<Location /apache>
		</Location>
		<Location /iis>
		ProxyPass http://internal-IP-of-IIS-server/
		</Location>
		
		
		S
		
		  


Re: do I need a custom proxy?

Posted by Sam Carleton <sc...@gmail.com>.
I did not mention that I am only interested in HTTPS, not HTTP.  It is 
my understanding that virtual host's don't work for HTTPS, is this correct?

Sorin Manolache wrote:
> On Tue, Jun 2, 2009 at 14:45, Sam Carleton <sc...@miltonstreet.com> wrote:
>   
>> I do develop Apache Modules which is why I thought to ask this question
>> here...
>>
>> I run a micro ISV out of my home and I only have one external IP address.  I
>> need to have some services on Apache and others on IIS.  How would I pull
>> this off since I only have one external IP address?  My thought is create a
>> custom mod_proxy that will redirect some URL's from the public facing Apache
>> to the internal IIS.  Is this the correct approach or is there an approach
>> that does not require actual development?
>>     
>
> Can't you create two virtual hosts or two locations on your apache,
> one of them handling requests and the other forwarding them to IIS?
>
> Something like
>
> <VirtualHost *>
> ServerName apache.my-domain.org
> </VirtualHost>
> <VirtualHost *>
> ServerName iis.my-domain.org
> ProxyPass / http://internal-IP-of-IIS-server/
> </VirtualHost>
>
> and you register apache.my-domain.org and iis.my-domain.org as having
> the same IP address in the authoritative nameserver of my-domain.org.
>
> or
> <Location /apache>
> </Location>
> <Location /iis>
> ProxyPass http://internal-IP-of-IIS-server/
> </Location>
>
>
> S
>
>   

Re: do I need a custom proxy?

Posted by Sorin Manolache <so...@gmail.com>.
On Tue, Jun 2, 2009 at 14:45, Sam Carleton <sc...@miltonstreet.com> wrote:
> I do develop Apache Modules which is why I thought to ask this question
> here...
>
> I run a micro ISV out of my home and I only have one external IP address.  I
> need to have some services on Apache and others on IIS.  How would I pull
> this off since I only have one external IP address?  My thought is create a
> custom mod_proxy that will redirect some URL's from the public facing Apache
> to the internal IIS.  Is this the correct approach or is there an approach
> that does not require actual development?

Can't you create two virtual hosts or two locations on your apache,
one of them handling requests and the other forwarding them to IIS?

Something like

<VirtualHost *>
ServerName apache.my-domain.org
</VirtualHost>
<VirtualHost *>
ServerName iis.my-domain.org
ProxyPass / http://internal-IP-of-IIS-server/
</VirtualHost>

and you register apache.my-domain.org and iis.my-domain.org as having
the same IP address in the authoritative nameserver of my-domain.org.

or
<Location /apache>
</Location>
<Location /iis>
ProxyPass http://internal-IP-of-IIS-server/
</Location>


S

-- 
A: Because it reverses the logical flow of conversation.
Q: Why is top-posting frowned upon?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

Re: do I need a custom proxy?

Posted by Joachim Zobel <jz...@heute-morgen.de>.
Am Dienstag, den 02.06.2009, 08:45 -0400 schrieb Sam Carleton:
> My thought is create a
> custom mod_proxy that will redirect some URL's from the public facing
> Apache
> to the internal IIS.  Is this the correct approach or is there an
> approach
> that does not require actual development?

Probably no.

http://httpd.apache.org/docs/2.0/mod/mod_proxy.html#ProxyPass

Hth,
Joachim



Re: do I need a custom proxy?

Posted by Sam Carleton <sc...@gmail.com>.
Ray Morris wrote:
>    You could of course run one serer on a non standard port.
Yes, except that there are many many access points out there that ONLY 
allow port 80 and 443 out, if I used a different port for one of the 
servers, than it would be blocked from such places.

Re: do I need a custom proxy?

Posted by Ray Morris <su...@bettercgi.com>.
   You could of course run one serer on a non standard port.
--
Ray B. Morris
support@bettercgi.com

Strongbox - The next generation in site security:
http://www.bettercgi.com/strongbox/

Throttlebox - Intelligent Bandwidth Control
http://www.bettercgi.com/throttlebox/

Strongbox / Throttlebox affiliate program:
http://www.bettercgi.com/affiliates/user/register.php


On 06/02/2009 07:45:03 AM, Sam Carleton wrote:
> I do develop Apache Modules which is why I thought to ask this
> question
> here...
> 
> I run a micro ISV out of my home and I only have one external IP
> address.  I
> need to have some services on Apache and others on IIS.  How would I
> pull
> this off since I only have one external IP address?  My thought is
> create a
> custom mod_proxy that will redirect some URL's from the public facing
> Apache
> to the internal IIS.  Is this the correct approach or is there an
> approach
> that does not require actual development?
> 
> Sam
>