This is really not recommended.
That being said, you could easily handle this using Server Name Indication - its like host headers for encrypted websites. By editing the site bindings you should be able to route https requests for your two additional websites to the appropriate site in IIS based upon the URL; the remainder can be routed to the Exchange-...
I have seen a similar issue on a core banking Web application. The problem was that sometimes some of the sessions remained locked into the ASPState database, resulting in hundreds of calls per second to dbo.TempGetStateItemExclusive3 for each of the locked sessions.
The CPU on the IIS server would eventually go up with the number of locked sessions. A ...
I figured this out. First you have to realise the areas that this can be committed to. I found it at https://docs.microsoft.com/en-us/iis/get-started/getting-started-with-iis/getting-started-with-appcmdexe and these are the below which I needed to use the "URL" section:
url — same as default; write configuration at the level for which it is set
site — ...
The supported method is with Get-WindowsFeature, because the registry keys can change at any time.
"Available" means that the feature is available for installation but is not installed
Gets information about Windows Server roles, role services, and
features that are available for installation and installed on a
.NetCore intentionally throws the InvalidOperationException with mentioned message when a dictionary is modified by multiple threads.
The key is to use a thread-safe ConcurrentDictionary.
Please see the GitHub Issue.
I never did find a solution to the ASP problem. So, I converted all of my pages from ASP to PHP and I haven't seen any errors at all. I'm not thrilled, but the problem is solved.
I hope you find this useful.
There seemed to be alot of ways to fix this, but what worked for me was clicking "Request Restructions from "Handler Mappings" setting Maping to file or folder, Verbs to All Verb and Access to Execute.
The issue here was due to our ISP. Our ISP manages our firewall. A request was sent to them to open port 443 for incoming and outgoing connections to the machine running the site. They had done this for port 1234 so we expected the same changes to be made. Apparently, the port was opened but also was not ??.. I'm not a network guy so I couldn't understand ...
First of all, I found you had to actually perform an HTTP request to get the connection timeout to kick in e.g entering.
telnet <webserver> 80
GET / HTTP/1.0
Once this is set, I found that system.applicationHost/webLimit/connectionTimeout does not work, but system.applicationHost/sites/[Default Web Site]/limits/...
Well, I gave up. Uninstalled and then reinstalled everything from the beginning including .Net frameworks, IIS, php extension, etc. ... and it is working now. It might been caused by that I haven't had .NET framework 3.5 installed. I had installed versions 2xx and 4xx, but it seems, that I missed to install 3.5
I figured out the problem and it's pretty dumb, but I was definitely 100% right about the binding to the IP.
There were other sites on the same server with bindings that someone had bound directly to the IP address, too. Correcting those, and the netsh show sslcert suddenly stopped showing my IP address bound to a cert, and I knew right away that it was ...
If you don't have SNI on, a HTTP server looks at the Host: HTTP header to decide which virtual host the connection was intended for.
If you are connecting over HTTPS, the server cannot see that header: it would need to decrypt the request first, but before decrypting, the server must identify itself, and it has no other option but to guess the default ...
how do I get a CA signed SSL certificate on windows servers without any access to internet
Install an internal Microsoft CA
Issue the certificates
Ensure the system with the application trusts your internal
Even if you were to use an external issuing CA, it's very common to not have Internet access. In that scenario you could host the ...
While we had used SAN certificate for all domain and subdomains for 4 years now, someone had configured this particular subdomain with old SNI certificate in the Fortiweb firewall.
I ended up removing this configuration and it works now.
Thank you for your help.