Russell's Blog

The nicest guy you'll never know
Vimeo Flickr Twitter RSS

Railo, Tomcat, IIS and default index page giving a 404.

With Railo, Tomcat and IIS working in harmony, there was one thing I just coudln’t get to work – the default index page would give a 404 error. Using '/example/index.cfm' worked, but '/example' or '/example/' would not.

A quick Google search presented several possible solutions:

Making sure 'index.cfm' is in the list of default content pages within the IIS website document properties.

Making sure '/*.cfm=ajp13' was listed within the 'uriworkermap.properties' file in the Tomcat conf folder.

Both these were already done, and still nothing. Another solution was outlined at several sites, including http://cflove.org/2010/12/railotomcat-and-iis-http-error-443-not-found-the-page-you-are-requesting-cannot-be-served-error.cfm, which looked at Handler Mapping within IIS. This did work fine, except Railo Session and Client data was being lost everytime it would redirect to the default index.cfm. So, when a logged in user went to ‘/example’, they would be given a new CFID.

The only way to get the default index.cfm page to work and maintain session and client data was to add '/*=ajp13' to the 'uriworkermap.properties' file in the Tomcat conf folder, which passes EVERYTHING off to Tomcat and Railo, making IIS redundant, but at least everything is working.

posted under Coldfusion

Email will not be published

Website example

Your Comment: