>>After verification, the one that is not catchable is:
>>
>>HTTP Error 404.0 - Not Found
>>
>>As opposed to the regular 404 error that I can trap in the code, this is a 404.0 error which differs a little bit.
>>
>>I am still looking at the proper way to intercept those as well from the code.
>
>It will be returned as a text message:
>
https://www.w3.org/Protocols/rfc2616/rfc2616-sec6.html>
>Example:
>
https://www.tutorialspoint.com/http/http_responses.htm>
HTTP/1.1 200 OK
>Date: Mon, 27 Jul 2009 12:28:53 GMT
>Server: Apache/2.2.14 (Win32)
>Last-Modified: Wed, 22 Jul 2009 19:15:56 GMT
>Content-Length: 88
>Content-Type: text/html
>Connection: Closed
>
>You can see the exact response using Telnet (download PuTTY if you don't have a telnet client):
>
C:\> telnet yourweburl.com 80
>
>Type "GET / HTTP/1.1" or whatever the url is producing the error, and press enter twice. Look at the top line of the header returned. That's what you'd need to parse if you can get the raw returned content, including that header.
>
>-----
>A possible fix?
>
https://stackoverflow.com/questions/33972144/maprequesthandler-404-0-error-when-routing-html-from-aspx-in-iis-8-0Or you can just use postman or fiddler …
