You are here

Port 80 Already In Use

February 9, 2011 - 08:20 — Bonnie

It's possible for a network to be setup in such a way that Port 443 is forwarded to the Apache machine for online sales and Port 80 is not. Often Port 80 is in use by another application within the network. The online sales will run however this can impact the patrons ability to access the online sales.

Notice there is no S after the http. The http uses Port 80 to connect to Apache. Apache then redirects the site to httpS://tickets.yourvenue.org/TheatreManager/1/login which then hands the connection over to Port 443 since the link is now using httpS.

It is recommend that Port 80 is also forwarded so that when someone tries to type the address of the online sales site into their browser they are more likely to get to the ticketing site rather then experience errors indicating the site may not be working.

Options for working around a network where Port 80 is already in use are listed below:

Change the exchange server settings to use a port other than 80. This becomes a case of what is more important, that end customers can reach web sales on a standard HTTP port, or staff use an alternate port when using exchange from home. Arts Management Systems believes the customers and standard should prevail and so the answer is change Port 80 for exchange to something else.

Get another external IP dedicated to the exchange server so that both can use Port 80. One will be through tickets.yourvenue.org:80, the other will be a different external ip.

Do some HTTP magic on the IIS server to redirect the path. On apache, there is a module called mod-rewrite, or you can create proxy settings so that anything with /TheatreManager/..... in the http path name in it gets sent off to Port 80 on the web listener. There should be something similar in IIS.

Don't serve exchange on the outside so that its not a problem any more and leave Port 80 on the single IP for customer web purchases