You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mod_cfml doesn't trigger when a directoryIndex index.cfm directive is used, on a first request to just /, which ends up with the default welcome to lucee page on port 8888
the reason is it's checking the r->uri, as opposed to the actual file which is handling the request? i.e. r->filename
it works after any other request has triggered mod_cfml and tomcat knows about the context
mod_cfml doesn't trigger when a
directoryIndex index.cfm
directive is used, on a first request to just /, which ends up with the default welcome to lucee page on port 8888the reason is it's checking the
r->uri
, as opposed to the actual file which is handling the request? i.e.r->filename
it works after any other request has triggered mod_cfml and tomcat knows about the context
https://github.com/viviotech/mod_cfml/blob/master/C/mod_cfml.c#L385
https://dev.lucee.org/t/mod-cfml-isnt-triggering-on-the-first-request/8263
It looks like we are almost doing more processing, to avoid adding the extra headers, than just adding the headers involves?
The text was updated successfully, but these errors were encountered: