IIS 7 and Above
404.4 on HTTP but HTTPS works fine
Last post Nov 13, 2017 10:01 AM by Yuk Ding
Nov 10, 2017 02:44 PM|Mastrat|LINK
I'm going mad on a problem with a site in IIS on a 2012 R2 server. I was trying to configure an URL rewrite from HTTP to HTTPS when I found out that a HTTP call leads into a 404.4:
Maybe this is why the rewrite from HTTP to HTTPS does not work either. A HTTPS call works fine.
There are no active redirects configured and all rewrite rules have been erased.
The only thing is that I'm using an alias in the URL. The certificate was issued to this alias and HTTPS works so it shouldn't be the problem, right?
I would appreciate any help...
Nov 13, 2017 02:27 AM|Yuk Ding|LINK
The 404.4 error means no handler. So please check whether you could access both http and https site at the same time.
If you need to rewrite to an external website, please install the application request routing and go to IIS manager->server node->application request routing cache->proxy->enabled.
You could just download it from here or web platform installer:
If only the htm file can't be accessed. Please go to turn windows features on or off and check ensure the IIS feature internet information service/world wide web services/common http feature/static content has been installed. If the other exntesion can't be
accessed, please check whether any other feature like asp.net has been installed in world wide web services/application development features.
Nov 13, 2017 09:23 AM|Mastrat|LINK
thanks for your reply. I'm not rewriting to an external site. I just wanted the rewrite from http to https. No http calls work. It doesn't matter if I try to access an *.html, *.php or anything else. It always leads to an 404.4. And the same content works
fine when called by https.
ASP.NET 4.5 is installed, but I dont have any .net apps. FastCGI for php is installed and used.
The static content is installed. So I think there must be something hard broken. Is it possible that by any way all handlers have been deactivated for http?
Nov 13, 2017 10:01 AM|Yuk Ding|LINK
Your configuration equal to build a reverse proxy, so for proxy, you could follow this document.
In addition, you need to promise the https handshake. So what if use a trusted CA. I may test the http rewrite to https at a later time. I remembered I could rewrite http to https without any issue.