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 this
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 K
Thanks Smith for your well informative and educative response.
Yes, we are looking into options what you mentioned: look for bottlenecks
to speed the data processing and also streaming of the data as and when it
gets generated.
Thank you once again..
With Regards,
Venkatesh
On Wed, Oct 7, 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 takin
This has nothing to do with keepalivetimeout – that is to do with keeping a
connection open to send subsequent requests without re-negotiating the
connection.
It is TimeOut which is the gap between sending packets of the response.
If your response is taking more than 1 minute to generate then y
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 I
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 ?
Tr
