[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 702
  • Last Modified:

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 192.168.111.12 and internal DNS routing traffic through 192.168.111.13.  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.
0
macmahoooon
Asked:
macmahoooon
  • 2
1 Solution
 
ChetOS82Commented:
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")
0
 
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.
0
 
ChetOS82Commented:
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.
0
 
jaswinder108Commented:
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.


Thanks
0

Featured Post

 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now