Sure thing, yes. I might raise another ticket for the global setting if ok (and create a pull request), unless this is likely to be rejected?

can i close the ticket?

It is simpler not to make 2 cases you have to handle differently. In Lucee every request has a request timeout.
sure you could do

but in the end this is simpler

and you don't have the risk that if you check that value in a new place that you not forget to check the special condition "0", because there is no special condition.

you always can argue in both directions, i personally prefer to have a setting always available with a default value, so you not have to check if the setting exists in the first place.

Fair enough - it seems an odd solution and I did see that in code. i.e. why not just skip all checks where the timeout is `<= 0`? Is there a good reason not to do that?

FWIW, I was able to completely disable engine-wide timeouts with this awful cludge:

I'm not using that as an option, but it works. Would be good to have some official ways to set engine.allowRequestTimeout(false);. i.e. a server admin setting for ignoring request timeouts that ACF has (and also OpenBD do not do timeouts at all). Probably not used in most cases, but valid in some.

in case of 0 or less Lucee sets a timeout of Long.MAX_VALUE, what normally is "9223372036854775807".
this are 2562047788015 days or around 106751991167 years!
in theory not the same as no timeout, but in practice it makes no difference.