It should automatically work. I did have this problem with Coldbox debugger graphs when I locked down admin in Apache. I just did /lucee and then got an error it couldn’t read graph.cfm in my WEB-INF. I had to change the lockdown to /lucee/admin.
I was able to get access to lucee admin and I noticed that there is already a mapping for /lucee pointing to {lucee-config}/context/
Then why I am seeing this error? Do this need an IIS mapping as well?
Hi, thanks for the reply. We are switching over an existing ACF application so it makes calls to graph.cfm in /web-inf/lucee/context - we’re not in a position at the moment to convert anything over.
The issue is that the given, default mappings in Lucee Admin don’t resolve the internal calls to the location of graph.cfm.
Can you show us what error you see? Chances are you’re proxy via IIS or Apache is not sending the traffic to CF at all. A good test is to see whether the URL works when hitting Lucee/Tomcat’s HTTP port directly and bypassing any external web server.