Apache and IIS on same box
Posted: Fri Nov 28, 2003 11:02 am
Background Info:
My web server (which is my personal computer) runs WinXP Pro. I run Apache on port 80 and IIS on port 8080.
Apache for PHP and Perl. IIS for ASP.NET.
Apache handles 5 virtual hosts for 5 different domain names.
IIS currently only works with http://localhost:8080, because I haven't purchased any domain names for it yet.
I use PowerDNS (http://www.powerdns.com to download source) as a DNS server.
Problem:
I want visitors to be able to access my IIS web server using domain names without specifying port 8080 in the host name.
Can this be done?
I don't have the option of porting everything over to IIS (PHP, etc.) because I try to maintain the same environment as my clients.
For anyone that has experience with running their own DNS server (bind, etc.) can I specify that all requests for something.com go to something.com:8080?
Or, would I have to set up a virtual host in httpd.conf (for Apache) and forward the user to something.com:8080 so IIS can then handle it? After the initial redirect, I don't mind if :8080 appears in the website address.
Is there anything I can do?
One thing I specifically don't wanna do is HIDE a redirect using frames.
My web server (which is my personal computer) runs WinXP Pro. I run Apache on port 80 and IIS on port 8080.
Apache for PHP and Perl. IIS for ASP.NET.
Apache handles 5 virtual hosts for 5 different domain names.
IIS currently only works with http://localhost:8080, because I haven't purchased any domain names for it yet.
I use PowerDNS (http://www.powerdns.com to download source) as a DNS server.
Problem:
I want visitors to be able to access my IIS web server using domain names without specifying port 8080 in the host name.
Can this be done?
I don't have the option of porting everything over to IIS (PHP, etc.) because I try to maintain the same environment as my clients.
For anyone that has experience with running their own DNS server (bind, etc.) can I specify that all requests for something.com go to something.com:8080?
Or, would I have to set up a virtual host in httpd.conf (for Apache) and forward the user to something.com:8080 so IIS can then handle it? After the initial redirect, I don't mind if :8080 appears in the website address.
Is there anything I can do?
One thing I specifically don't wanna do is HIDE a redirect using frames.