You’re confusing the location of a .cfm file in the ColdFusion web root and the location of the file the CLIENT (web browser) sees. The way that ColdBox works is the browser sees all requests as coming from the /index.cfm file in the root of the app mapping. The fact that the actual HTML returned by that page is aggregated from a number of places (handlers, layouts, view) in different subfolders has no bearing on how the browser resolves images.
What is your web root? (Showing us the URL should suffice) The ColdBox sample apps are structured such that there are several stand-alone applications in subfolders inside the web root. That file is contained up in the main application, however if you’ve started the site with the web root at the same level as your app root, then the …/ won’t work.
The problem lies in the mapping of paths in Lucee/Tomcat. I have copied helloworld application under the document root of Lucee/Tomcat. Images are shown with following line in Main.cfm
On the face of it, it appears Coldbox shows images and other assets as long as application is hosted directly under the web root and no other mapping of the path is involved.
I’m not sure I’m following you. ColdBox does not show images. Your browser does. The powered by image in that sample app will only display if the app is nested under the main application like it comes in the download. If you move the app elsewhere, the relative path will break. Regardless, this has nothing to do with ColdBox. It is your browser that resolves images and displays them.
