Ryfujk

I'm not 100% sure if this is the right part of StackOverflow to post this but to me it made the most sense. Sorry if its not!

Currently I have a site in IIS configured on HTTPS with port 7500. I can access this site by using the URL: https://portal.company.com:7500.

What I would like to do is remove the port number at the end of the URL so users can access this site using https://portal.company.com...

I am a complete beginner with IIS, but what I have tried is the HTTP Redirect, which if I used on this IIS site, would redirect a user that hits portal.company.com:7500 to some other site, which is not what I need. Another thing I have though about is creating another IIS site which serves the purpose of being at the URL portal.company.com and when its hit, it redirects to my portal.company.com:7500, but I don't know if this is the best approach.

So my question is, what are my options for achieving the behavior mentioned above and what is the best/recommended approach?

I haven't played with URL Rewriting before but I will look into that now while I wait for a reply. Thanks!!

Using IIS Manager on a Windows Server 2008 machine.

If as you note in a comment on the other answer you have another site already running on port 443, you will need another IP address so that you can bind the site to port :443 on that address, then change your DNS records accordingly. You cannot bind more than one site to the same socket with HTTPS in IIS, at least until SNI becomes totally viable and Microsoft updates the software accordingly.

The exception would be if you are running a wildcard or ASN certificate that is valid for both sites, then follow this procedure.

This is assuming your goal is to allow visitors to hit the site over HTTPS from their browsers without specifying a port. If I misunderstood your question then the answer won't be accurate:)

Try This

<configuration>

<system.webServer>

    <rewrite>

           <rules>

            <rule name="removePort" stopProcessing="true">

                <match url="^(http(s)?://)?(portal.company.com):7500(/.*)?$" />

                <action type="Redirect" url="https://{R:3}/{R:4}" />

            </rule>

        </rules>

    </rewrite>

</system.webServer>

Have you tried simply changing the http binding to use port 80? That should be all you need to do, no need for redirection to take place. Assuming you don't have another web site on port 80, this should work just fine for you.

http://www.gadgetcage.com/how-to-change-iis-port-in-windows-7/3457/

This is based on the fact you were willing to create a new website on port 80 for the sake of simply redirecting to port 7500. Just take out the middle man and move you port 7500 site onto port 80, and problem solved.

you can use 2 ssl certs on the same server with one IP but they must use another port. Multi-name certs are quite costly. URL rewrite can be used to hide the port from the client.