Setting requesttimeout no affect over admin requesttimeout

Lucee 5.3.9.141 and 5.3.10.97
Servlet Container Apache Tomcat/9.0.35
Java 11.0.7 (AdoptOpenJDK) 64bit
OS Windows Server 2012 R2 (6.3) 64bit
Architecture 64bit

apache http with connector settings in server.conf:

Lucee admin “Request timeout” 120 seconds.

Posts to page containing:

cfsetting requesttimeout=“3600”
cfset body = GetHTTPRequestData( includeBody=True )
cfoutput #left(body.content,200)# cfoutput
cfabort

Form post is a 10mb json string. sent in body. Using POSTMAN.

Times out after 2 minutes. Roughly the same as the admin “Request timeout”. The requesttimeout on page does not seem to do anything.

Also, I tried adding a request timeout at the application level. It timed out at roughly 2 minutes as well.

If I change the admin request timeout to 10 minutes it works as expected.

“ERROR”,“Thread-93”,“12/27/2022”,“15:09:28”,“controller”,“stop request (20) because run into a timeout. ATM we have 1 active request(s) and 0 active cfthreads (no path available).;java.lang.Throwable;java.lang.Throwable
at lucee.commons.net.URLDecoder.decode(URLDecoder.java:64)
at lucee.runtime.type.scope.ScopeSupport.fillDecoded(ScopeSupport.java:181)
at lucee.runtime.type.scope.FormImpl.initializeUrlEncodedOrTextPlain(FormImpl.java:278)
at lucee.runtime.type.scope.FormImpl.initialize(FormImpl.java:133)
at lucee.runtime.PageContextImpl.formScope(PageContextImpl.java:1265)
at lucee.runtime.type.scope.UndefinedImpl.reinitialize(UndefinedImpl.java:625)
at lucee.runtime.type.scope.UndefinedImpl.initialize(UndefinedImpl.java:604)
at lucee.runtime.PageContextImpl.initialize(PageContextImpl.java:549)
at lucee.runtime.CFMLFactoryImpl.getPageContextImpl(CFMLFactoryImpl.java:246)
at lucee.runtime.engine.CFMLEngineImpl._service(CFMLEngineImpl.java:1184)
at lucee.runtime.engine.CFMLEngineImpl.serviceCFML(CFMLEngineImpl.java:1162)
at lucee.loader.engine.CFMLEngineWrapper.serviceCFML(CFMLEngineWrapper.java:97)
at lucee.loader.servlet.CFMLServlet.service(CFMLServlet.java:51)
…”

response:

502 Bad Gateway

Bad Gateway

The proxy server received an invalid response from an upstream server.