Yeah, thats not a CF error. Or at-least not specifically a CF error. It could be a apache config problem. Specifically in the way that apache passes off the request to the CF engine. When apache gets a request for a *.cfm page, it *should* pass it to the CF server. It looks like this is not...