Error page when url is requested without file extension
Hi,
it's already me again. I've setup a custom error page to handle 404 errors, which works perfectly when calling a non-existing url as localhost/bla.aspx and raises the error page. When requesting localhost/bla (which also does not exists), i get the ugly IIS 7-generated default 404 page.
I have not set up extensionless urls and to be honest, even if this fixes the problem, i dont wan't to use it.
In IIS 6, you have to set up Wildcard script mapping and I suspect you have to do the same in IIS 7 - I'd check if this is setup first, then check back here to see in anyone else has chimed in (I run IIS 6).
Error page when url is requested without file extension
Hi,
it's already me again. I've setup a custom error page to handle 404 errors, which works perfectly when calling a non-existing url as localhost/bla.aspx and raises the error page. When requesting localhost/bla (which also does not exists), i get the ugly IIS 7-generated default 404 page.
I have not set up extensionless urls and to be honest, even if this fixes the problem, i dont wan't to use it.
Cheers,
André
Andre,
In IIS 6, you have to set up Wildcard script mapping and I suspect you have to do the same in IIS 7 - I'd check if this is setup first, then check back here to see in anyone else has chimed in (I run IIS 6).
Regards
Tom
Checkout this link It's a great resource about how to set exstionless url's up in IIS 6 and 7(both classic and integrated pipeline)
Hope it helps you,
Richard
I'll give it a try tonight.
Thanks,
André
Didn't work for me, have to study this once again in a silent moment.
You might wanna give this a try: (did not check it in IIS7)
In IIS6:
You can also check this: http://msdn.microsoft.com/en-us/library/h0hfz6fc</span>(VS.80).aspx
Since 'RemoteOnly' specifies that custom errors are shown only to the remote clients, and that ASP.NET errors are shown to the local host.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.