Thanks for the info.
I did a extended find on this in the app’s code. This is the only instance it’s used.
The bad code in in the 404 script is being called from a function declared in a .cfc
I did a quick test and made a test404error.cfm page, and declared it as the 404 error page in both Lucee and OpenBD’s respect web.xml.
<cfset subFolder = "#request.javax.servlet.error.request_uri#">
In Lucee, if I request the non existant ‘test123’ file, via domain.com/test123, it returns the error I posted above.
In OpenBD, doing the same returns the .cfm file as requested with the output:
I then added various .cgi variables to each 404test.cfm page and realized something. The .cgi variables are referring the url of the 404 error page, not the url of the user requested page.
Yields browser output of
This leads me back to why I think ‘javax.servlet.error.request_uri’ is being used here. It’s returning ‘test123’ from ‘domain. com/test123’ when the 404test.cfm is called.
So, if Lucee doesn’t support this method, I need to ask, what variable can I call to get the part of the requested url that is needed?
User types ‘domain .com/test123’, but ‘test123’ isn’t a valid resource. Tomcat calls 404test.cfm, and from within 404test.cfm I need a variable that will provide me with the ‘test123’ portion of the url that was originally requested.