Ok, so firstly forget completely about the CFM file and the HTML image tag. Those are all distractions. Just test this by typing the URLs directly in your browser’s address bar.
The first exampel beow shows it, the 2nd doesn’t.
Do you realize that your two examples are not the same? The second one has a leading forward slash which means the canonical URL (unless you’ve overridden it with a base href) will be
It sounds like the first URL you posted in your first post should work, but there’s too much I don’t know, like what was in the browser’s address bar at the time. Relative image paths are going to be determined by what folder the browser thinks it served the current HTML/CF page from. Turn on your browser’s debugging toolset and look in the networking tab so you can see the actual full paths that your browser is trying to hit for the images. That should help you troubleshoot.
I would start by determining what the correct FULL URL is to the image, and then work backwards to determine what the correct relative URL would be. Or, you can just make all your image paths start with / but then you need to include everything after the host name.
I have tried to access them with ./img/filename
I don’t think that’s even valid. This isn’t bash and URLs have no concept of a dot to represent the current folder.
and even full path IMG SRC=C:/lucee/tomcat/webapps/ROOT/ptr/img/imgname…
That would never work. Think about it-- your browser has no idea what the local file system of your server is and for good reason. All the browser has is a host name and path.