Ah, got it! So it is just that one line that is causing the issue.

In theory, it would never be lucee-light in the first place. The same truncation logic exists around line 888 where we first initialize that variable in the first place. If you can find a path where serverInfo.enginename is ever set equal to anything other than just the engine names, the we need to fix that as well.

I would be happy to send a pull, but I am not sure what the desired behavior is. If serverInfo.engineName is not set at all at the outset, it will be set from installDetails.engineName, but truncated. In my case that would mean that if the engineName was lucee-light it would be set in the server info to lucee, whereas if it was already set in the server info, it would remain lucee-light. And then the fix for this issue clears the engine name (since lucee-light is not in the list).

Do you want the engine name to be set/remain as lucee-light or do you want it to be set to lucee in a case like mine?

yeah, I think this line was just an accident and should be removed. Not sure why it’s there

Can you test that and send me a pull?

I just bumped into the fix for this issue, which is in the following commit: . That fix doesn’t consider the possibility that the server could be lucee-light, and if you use that, the engineName gets cleared.

In looking at that section of the code in ServerService.cfc, I also find the following confusing: - you have an if block that checks if serverInfo.engineName is not set, and if not, it sets it from installDetails.engineName, but truncated to one of lucee,railo,adobe,boxlang. And then you have the line serverInfo.engineName = installDetails.engineName; - which means that no matter what `serverDetails.engineName` will be the same as installDetails.engineName
.