1

I've setup custom errors and it's working, But in some cases IIS does not recognize the file extension and therefore does not even process the page...

For example: http://example-web-site.com/page.aaa

So, ".aaa" is not recognized and IIS shows an ugly error page HTTP Error 404.0 - Not Found The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.

How can I handle all (unknown extensions) so I can still capture every hit to the web site and do something with it or show my custom error page?

Yovav
  • 2,557
  • 2
  • 32
  • 53
  • 1
    Have you read this: http://stackoverflow.com/questions/6648007/iis7-custom-404-not-showing/6661699#6661699 – paul Mar 02 '15 at 11:17
  • I think this would be better asked on serverfault or webmasters. – Ash Burlaczenko Mar 02 '15 at 11:17
  • 1
    I'd really advertise against allowing all extensions.. It's a potential big security risk. Register just the file extensions you know and need (it's called whitelisting btw). – walther Mar 02 '15 at 11:34
  • I don't really want to process these extensions, just to be able to have everything hit my app on IIS so I can decide what to do with it... maybe it can be done using the IIS rewrite module... – Yovav Mar 03 '15 at 20:59

0 Answers0