Skip to main content
Participant
April 6, 2010
Question

Can't get index.cfm as default file

  • April 6, 2010
  • 2 replies
  • 926 views

I finally got CF8 standalone running under Leopard on my Mac, but I've noticed that unless I add index.cfm, I get a 404 error.  I have already modified the DirectoryIndex entry on /etc/apache2/httpd.conf so that it now reads index.html index.cfm.  Still I get 404 if I don't add index.cfm to a URL.  Is ther a step I'm missing?  I've restarted both Apache and ColdFusion with no success.

Additionally, I have noticed that image files aren't rendering at all on my cfm pages.  Code renders as expected but images do not even with a full path, which I have verified numerous times. If I select 'View image in new tab' I get a 404 error, but again I have verified that the image is in fact in place and the path is correct.  Is there another setting I need to change in Apache?  Thanks.

    This topic has been closed for replies.

    2 replies

    Participant
    April 9, 2010

    Still no luck.  In fact, I've discovered today that perhaps CF8 isn't playing nice with Apache after all.  It appears that .cfm files render properly, however .jpg or anything else for that matter, even .html does not render, instead throwing a 404 error.  A little digging revealed that it is looking for those files under the defaul Apache webroot /Library/Web Server/Documents/.  What gives?  Is there somewhere out there a clear set of instructions that details how to correctly install ColdFusion 8 on an intel-based MacBook running Leopard?  Nothing I've tried yet seems to work properly.  Getting a bit frustrating.  I've never seen a situation where it seems PC is in fact simpler than Mac and neither Adobe nor Apple seem to have much desire in helping.

    Owainnorth
    Inspiring
    April 6, 2010

    As it's a unix-based OS, you may be falling foul of case-sensitivity.

    Are you sure you haven't named the file Index.cfm not index.cfm, or vice versa? Depending on how you've created/saved your images, it could also be a permissions issue - check whatever user CF is running as has permissions over the images.

    When you view the image info (in a browser, right/ctl+click) what does it give as the image source path?

    O.