>> AFAIK, 2 different requests are served separately, meaning you can have
>> some requests sent when some other is being responded to.
>>
>> If you talk about the same request, then it is only sent to the next
>> upstream server when there is an 'unsuccessful attempt' at communicating
>> with the
Hello
I would like to go back to this item:
>> Yes, nginx will process requests one-by-one and won't pipeline
>> requests to upstream.
Can you please confirm, if no new request is sent to the upstream before the
entire response is received for the ongoing request (ongoing request
finished)?
In
Hello,
> I'm talking about upstream server, not the "server" directive in
> the "upstream" block. Assuming you are using nginx as an upstream
> server you should use keepalive_requests.
We are not using nginx on the upstream side (we have some legacy server),
this is why I was looking for keepa
> Yes, nginx will process requests one-by-one and won't pipeline
> requests to upstream.
So, you confirm that the current implementation of nginx doesn't pipeline
towards upstream, and there is no way to enable that functionality?
> No, it's not something currently implemented. It's not conside
Thanks for your prompt response.
Let's a client is sending pipelined requests on the client side and nginx
has multiple upstream keepalive connections.
Are you saying that NGINX will NOT pipeline on upstream side even though it
is receiving pipelined requests on client side?
Is there a way to clos
Hi,
Does anyone know a way to disable HTTP request pipelining on a same upstream
backend connection?
Let's say we have the below upstream backend that is configured with
keepalive and no connection close:
upstream http_backend {
server 127.0.0.1:8080;
keepalive 10;
