Apache and IIS side by side both listening to port 80 on windows2003

Question

What are some good ways to do this  Is it even possible to do cleanly    Ideally I d like to use packet headers to decide which server should handle requests  However  if there is an easier better way let me know

User · Answer

You will need to use different IP addresses   The server  whether Apache or IIS  grabs the traffic based on the IP and Port  which ever they are bound to listen to   Once it starts listening  then it uses the headers  such as the server name to filter and determine what site is being accessed  You can t do it will simply changing the server name in the request

User · Answer

It s impossible for both servers to listen on the same port at the same IP address  since a single socket can only be opened by a single process  only the first server configured for a certain IP port combination will successfully bind  and the second one will fail    You will thus need a workaround to achieve what you want  Easiest is probably to run Apache on your primary IP port combination  and have it route requests for IIS  which should be configured for a different IP and or port  to it using mod rewrite   Keep in mind that the alternative IP and port IIS runs on should be reachable to the clients connecting to your server  if you only have a single IP address available  you should take care to pick an IIS port that isn t generally blocked by firewalls  8080 might be a good option  or 443  even though you re running regular HTTP and not SSL   P S  Also  please note that you do need to modify the IIS default configuration using httpcfg before it will allow other servers to run on port 80 on any IP address on the same server  see Micky McQuade s answer for the procedure to do that

User · Answer

You need at least mod proxy and mod proxy http which both are part of the distribution  yet not everytime built automatically   Then you can look here  http   httpd apache org docs 2 2 mod mod proxy html  Simplest config in a virtualhost context is   ProxyPass          winapp http   127 0 0 1 8080 somedir   ProxyPassReverse   winapp http   127 0 0 1 8080 somedir     Depending on your webapp  the actual config might become more sophisticated    That transparently redirects every request on the path winapp  to the windows server and transfers the resulting output back to the client    Attention  Take care of the links in the delivered pages  they aren t rewritten  so you can save yourself lotsa hassle if you generally use relative links in your app  like      lt a href    pics mypic jpg  gt    instead of the usual integration nightmare of every link being absolute     lt a href  http   myinternalhostname somedir crappydesign jpg  gt    THE LATTER IS BAD ALMOST EVERY SINGLE TIME   For rewriting links in pages there s mod proxy html  not to confuse with mod proxy http   but that s another story and a cruel one as well

User · Answer

That s not quite true  E g  for HTTP Windows supports URL based port sharing  allowing multiple processes to use the same IP address and Port

User · Answer

Either two different IP addresses  like recommended  or one web server is reverse-proxying the other  which is listening on a port  lt  80    For instance  Apache listens on port 80  IIS on port 8080  Every http request goes to Apache first  of course   You can then decide to forward every request to a particular  named virtual  domain or every request that contains a particular directory  e g  http   www example com winapp   to the IIS   Advantage of this concept is that you have only one server listening to the public instead of two  you are more flexible as with two distinct servers   Drawbacks  some webapps are crappily designed and a real pain in the ass to integrate into a reverse-proxy infrastructure  A working IIS webapp is dependent on a working Apache  so we have some inter-dependencies

User · Answer

For people with only one IP address and multiple sites on one server  you can configure IIS to listen on a port other than 80  e g 8080 by setting the TCP port in the properties of each of its sites  including the default one    In Apache  enable mod proxy and mod proxy http  then add a catch-all VirtualHost  after all others  so that requests Apache isn t explicitly handling get  forwarded  on to IIS    lt VirtualHost   80 gt      ServerName foo bar     ServerAlias       ProxyPreserveHost On     ProxyPass   http   127 0 0 1 8080   lt  VirtualHost gt    Now you can have Apache serve some sites and IIS serve others  with no visible difference to the user   Edit  your IIS sites must not include their port number in any URLs within their responses  including headers

User · Answer

I see this is quite an old post  but came across this looking for an answer for this problem   After reading some of the answers they seem very long winded  so after about 5 mins I managed to solve the problem very simply as follows   httpd conf for Apache leave the listen port as 80 and  Server Name  as FQDN IP  80   Now for IIS go to Administrative Services    IIS Manager    Sites  in the Left hand nav drop down   in the right window select the top line  default web site  then bindings on the right   Now select http   edit and change to 81 and enter your local IP for the server pc and in domain enter either your FQDN  www domain com  or external IP close   Restart both servers ensure your ports are open on both router and firewall  done   This sounds long winded but literally took 5 mins of playing about  works perfectly   System  Windows 8  IIS 8  Apache 2 2

User · Answer

Installing Windows 10 I had this problem  apache ipv4  and spooler service ipv6  listening the same 80 port   I resolved editing apache httpd conf file changing the line  Listen 80  to  Listen 127 0 0 1 80

User · Answer

I found this post which suggested to have two separate IP addresses so that both could listen on port 80   There was a caveat that you had to make a change in IIS because of socket pooling   Here are the instructions based on the link above    Extract the httpcfg exe utility from the support tools area on the Win2003 CD  Stop all IIS services  net stop http  y Have IIS listen only on the IP address I d designated for IIS  httpcfg set iplisten -i 192 168 1 253 Make sure  httpcfg query iplisten  The IPs listed are the only IP addresses that IIS will be listening on and no other   Restart IIS Services  net start w3svc Start the Apache service

[apache] Apache and IIS side by side (both listening to port 80) on windows2003

Examples related to apache

Examples related to iis

Examples related to networking

Examples related to windows-server-2003