Our upstream actually supports HTTP/2 connections.
So, another question would be, if I use HTTP when fetching data from
upstream. I will be able to have more than 50 requests concurrently on
upstream?
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,269248,292162#msg-292162
___
> No, it's not possible.
>
> As already were said twice, nginx dosn't support pipelining on the
> upstream
> side.
>
> wbr, Valentin V. Bartenev
Has there been any progress on this in the last few years?
I am trying to use Nginx as a proxy to our legacy server but the hosting
company has a
On Friday 16 September 2016 08:41:11 hkahlouche wrote:
> >> 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 whe
>> 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
On Thu, Sep 15, 2016 at 11:12 PM, hkahlouche
wrote:
> 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 other words, is possible that upstream module sends the next request to
> u
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
Hello!
On Mon, Aug 29, 2016 at 12:23:34PM -0400, hkahlouche wrote:
> > 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 fu
> 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
Hi
I have a question the other way.
how to enable pipelining on upstream side? or atleast how to make nginx open
multiple loopack connections to serve requests pipelined from client side?
Thanks
Prasad.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,269248,269272#msg-269272
_
Hello!
On Mon, Aug 29, 2016 at 10:04:08AM -0400, hkahlouche wrote:
> 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 thou
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
Hello!
On Sun, Aug 28, 2016 at 08:22:08AM -0400, hkahlouche wrote:
> Does anyone know a way to disable HTTP request pipelining on a same upstream
> backend connection?
Pipelining is not used by nginx, there is no need to disable
anything.
--
Maxim Dounin
http://nginx.org/
__
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;
14 matches
Mail list logo