How can you tell the difference between an HTTP / HTTPS request that fails in an ASP .NET Core application and one that fails from an incorrect IIS configuration?
Most of the time, IIS and ASP .NET Core have different registers, and the solution is often to simply turn off HTTPS to find out which one is returning the error, but IIS error messages seem to be on the same line
HTTP 500 internal server error in the output of a registration message with W3C format, and do not specify anything deeper than that.
As far as I can tell, ASP .NET Core applications simply sit behind IIS and the requests / responses are a kind of reverse proxy to the actual application.
I found the following configuration configuration of IIS in which you can enable the tracking of failed requests, and it seems that you specify that you will gladly record the deeper error messages as
HTTP 500 internal server error It is mentioned at the end of that documentation, but I'm not sure about this.