Perhaps you want to adjust timeout for that backend? For example if you are proxying to a backend that takes about 100 seconds for /path/
ProxyPass /path/ https://backend/path/ timeout=120 El mié., 7 oct. 2020 a las 14:41, alchemist vk (<alchemist...@gmail.com>) escribió: > > Hi Eric, > I agree with you.. "keepalive timeout is n/a in the middle of a response". > > WR > A > > On Wed, Oct 7, 2020 at 5:58 PM Eric Covener <cove...@gmail.com> wrote: >> >> On Wed, Oct 7, 2020 at 7:54 AM alchemist vk <alchemist...@gmail.com> wrote: >> > >> > Hi Eric, >> > Thanks for response.. >> > To give more info, I have an URI where GET on this needs lot of >> > processing from backend to process, populate and frame the response and >> > then rendering the same. >> > So what is happening is, by having KeepAliveTimeout as 60, processing and >> > framing of this response taking more than 60 and hence apache returns 503. >> > As a trial, Increased the KeepAliveTimeout to 300 and its working fine >> > always. >> >> as politely as possible: I would be shocked if your final observation >> was not wrong. The keepalive timeout is n/a in the middle of a >> response. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org >> For additional commands, e-mail: users-h...@httpd.apache.org >> -- Daniel -- Daniel Ferradal HTTPD Project #httpd help at Freenode --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
