Forcing HTTP or HTTPS based on internal/external traffic

I have a server hosting a web application being used for both internal and external users.   I have applied an SSL certificate, but really only need to have external traffic secured.  Machine has 2 interfaces with external DNS routing traffic through and internal DNS routing traffic through  I have played with bindings but no real solution yet.  How can I have the server for HTTP/HTTPS based on the interface the traffic is entering.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

If you right-click on a website, and choose properties, you will see a drop down list of IP addresses.  I would create two sites, one using HTTP, and the other using HTTPS.  Bind the external one to the .12 IP, and the internal one to the .13 address.  (That is, rather than leaving it as "All Unassigned")
macmahoooonAuthor Commented:
Yes this works to limit traffic as is what I have currently set up.  The problem is entering the domain still attempts to resolve http:// instead of htts://. Any redirects will obviously affect both internal and external, as well setting "Require SSL" blocks internal users from accessing the http only.
Have a third site bound to the external IP, and have it redirect its pages to the same page, but with https instead.

So, the first external site will not listen on port 80 (only 443).  The second external site will not listen on 443 (only 80).  There will not be a conflict this way.  You can set the home directory to "Redirect to URL", and if you mess around with the various settings for that, you can redirect all traffic to the same page, but with https instead.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
You need to secure you server rather IIS what i understand .

You can try windows firewall and rules for HTTPS (443) HTTP (80) . ( IPsec is good option)

You need to explain what is to be secured as SSL is secured it self.

If Server security is good then you need not think much on it.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft IIS Web Server

From novice to tech pro — start learning today.