Forums (Obsolete)

Old Forums

New features If you wish to suggest a new feature, please use the New features forum for version 3.x.

Version 2.x > New features > Use of customized 404 error page to parse URL/Path

View modes:

Member

sciamannikoo - 6/15/2005 2:35:00 PM

Use of customized 404 error page to parse URL/Path

Hi!

I've think that. In some cases (depending to provider ot if web site is in a own server) we can customize "Error Messages for HTTP Errors" in IIS.
Well Kentico engine can be configure to manage this error to parse AliasPath (if AliasPath is without ".aspx" extension); after, if that AliasPath dont exist, it redirect to standard 404b.htm page or other custom page. This can prevents creation of dummies folders and pages.

I've taken this idea reading this article:
http://www.codeproject.com/aspnet/urlcloaking.asp

Bye,
Andrea

Guest

admin - 6/15/2005 10:01:38 PM

Re: Use of customized 404 error page to parse URL/Path

Hi Andrea,

Thank you for this suggestion. This could work, but it the problem is that it requires server configuration and it will also cause 404 errors in the web statistics.

Anyway, we plan to use *.aspx paths by default since version 1.7 to make everything easier for the developers. The current path format with dummy files will still be supported, of course.

Best Regards,

Member

wtijsma - 6/17/2005 6:41:45 PM

Re: Use of customized 404 error page to parse URL/Path

Hi,

I've used the same method, it doesn't cause 404 errors, you have full control over what status code is returned if the server is configured to output an URL rather than a file (/error404.aspx).

In the beginning I actually had unknown status codes because I didn't return a status code at all, but I think most ISP's don't mind configuring IIS to use your own 404 page.

Getting rid of the dummy files will be a relief, thanks. Makes synchronization too hard anyway.


Member	wtijsma - 6/28/2005 11:50:41 AM Re: Use of customized 404 error page to parse URL/Path Another option would be to have only 1 dummy page at the root, (kentico.aspx) and have the aliaspath after that: http://[host]/kentico.aspx/home/products/etc... This path can also be handled on the Global_asax.BeginRequest event...

Top