Installation and deployment Questions on installation, system configuration and deployment to the live server.
Version 6.x > Installation and deployment > Extensionless Urls and problems with physical folders View modes: 
User avatar
Member
Member
BitWise Blake - 6/19/2012 7:54:56 AM
   
Extensionless Urls and problems with physical folders
Recently moved a Kentico 6 site to IIS7, and we're having a problem with extensionless urls using the suggested method here: http://devnet.kentico.com/docs/devguide/index.html?custom_url_extensions_iis7.htm

The problem we run into when setting up <modules runAllManagedModulesForAllRequests="true"> is not that the extensionless urls don't work, they do, all the aliases work as well, but when we set it to run this way, Kentico doesn't honor any folders that physically exist and any default document settings.

For example, we have some old classic ASP Code that is still running in a folder. If we setup the above, and link to:

http://www.site.com/ASPFolder or http://www.site.com/ASPFolder/, Kentico processes this, and doesn't give things a chance to see that there is actually an index.asp (which is setup as a default document) file in there that it should link to. Kentico can't find it in it's file structure and gives a 404. Things work fine if we link directly to http://www.site.com/ASPFolder/index.asp

Is there additional configuration that can/should be done to allow IIS7 to know there is a physical file to load before Kentico handles it, or will we have to change how we link to things?

User avatar
Member
Member
kentico_alleng - 6/20/2012 1:19:47 PM
   
RE:Extensionless Urls and problems with physical folders
For the folders containing classic ASP Code, you can change a setting in the Site Manager to exclude them from being processed by Kentico. The request will be passed directly to IIS.

Go to Site Manager -> Settings -> URLs and SEO

Add the folders to the Excluded URLs property and separate entries using semi-colons. So for site.com/ASPFolder and site.com/ASPFolder2, enter:

/ASPFolder;/ASPFolder2

You can find more details in the Developer's Guide:

URL format and configuration

Regards,

Allen