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
() escribió:
>
> Hi Eric,
> I agree with you.. "keepalive
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 wrote:
> On Wed, Oct 7, 2020 at 7:54 AM alchemist vk
> wrote:
> >
> > Hi Eric,
> > Thanks for response..
> > To give more info, I have an URI where GET on
On Wed, Oct 7, 2020 at 7:54 AM alchemist vk 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
en create a unique URL which will fetch the data/or say
> comeback later
> - You then have a ticker in the page which retrieves the data
> via AJAX or just waits till ready and redirects
>
>
>
>
>
> *From:* alchemist vk
> *Sent:* 07 October 2020
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
From: alchemist vk
Sent: 07 October 2020 11:53
To: users@httpd.apache.org
Subject: [users@httpd] Configuring KeepAliveTimeout to individual URIs [EXT]
Hi All,
I have a requirement where serving GET on few URIs whose payload is large
takes more than 1min compared to our configured "KeepAliveTi
On Wed, Oct 7, 2020 at 6:53 AM alchemist vk wrote:
>
> Hi All,
> I have a requirement where serving GET on few URIs whose payload is large
> takes more than 1min compared to our configured "KeepAliveTimeout 60"
> directive. And this is resulting in 503 error to clients.
> Is there a way where
Hi All,
I have a requirement where serving GET on few URIs whose payload is large
takes more than 1min compared to our configured "KeepAliveTimeout 60"
directive. And this is resulting in 503 error to clients.
Is there a way where I can group few URIs and increase KeepAliveTimeout to
300 secs ?
