With just these settings (with or without the last mentioned web.config addition) my 404 page works, and displays, for nonsense such as 'http://localhost:61239/wibble'. This is fine.
If I go to 'http://localhost:61239/wibble.cshtml' I get
"This type of page is not served. Description: The type of page you have requested is not served because it has been explicitly forbidden."
But if I go to 'http://localhost:61239/views/wibble.cshtml' I get another 404:
"The resource cannot be found. Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed..."
Please tell me what additional settings, or amendments, I need in the web.config to get my 404 page working for these difference circumstances?
P.S. I've tried all kinds of combinations of an added system.webServer block in web.config, as the following indicates, but none have changed the above-described behaviour:
(There are also existing system.webServer sections, so I'm not sure if any changes need to be applied to one of these sections, or a completely new system.webServer section.)
custom 404 for variety of url errors
I followed this tutorial
so in umbracoSettings.config I have
plus this
which notes in the file suggest to skip IIS custom errors.
I also attempted adding a section to the bottom of the root web.config, as suggested:
Note that I am working locally.
With just these settings (with or without the last mentioned web.config addition) my 404 page works, and displays, for nonsense such as 'http://localhost:61239/wibble'. This is fine.
If I go to 'http://localhost:61239/wibble.cshtml' I get "This type of page is not served. Description: The type of page you have requested is not served because it has been explicitly forbidden."
But if I go to 'http://localhost:61239/views/wibble.cshtml' I get another 404: "The resource cannot be found. Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed..."
Please tell me what additional settings, or amendments, I need in the web.config to get my 404 page working for these difference circumstances?
P.S. I've tried all kinds of combinations of an added system.webServer block in web.config, as the following indicates, but none have changed the above-described behaviour:
(There are also existing system.webServer sections, so I'm not sure if any changes need to be applied to one of these sections, or a completely new system.webServer section.)
is working on a reply...