how nginx handle connection with backend web server?
xuepeng.li at gmail.com
Mon Aug 10 13:00:05 MSD 2009
if it's is 1:1 module and nginx establishes HTTP 1.0 only to apache
server, every time enginx receive a request, it has to proxy the request to
apache server, what is the advantange make enginx as reverse proxy other
than make direct connection between browser and apache?
2009/8/10 Joshua Zhu <zhuzhaoyuan at gmail.com>
> 2009/8/10 李学鹏 <xuepeng.li at gmail.com>:
> > So, it means that client (browser) will get a 5** error ?
> > if this, what's the meaning of enginx high concurrent connection ?
> > 2009/8/10 Weibin Yao <nbubingo at gmail.com>
> >> 李学鹏 at 2009-8-10 10:37 wrote:
> >>> hi all
> >>> i have a question that how nginx handle connection with backend web
> >>> server ?
> >>> for example, i have a nginx server for receiving client request, and
> >>> reverse proxy to backend 2 web server(such as apache server), every
> >>> server have 100 child process(prefork module). so, if there are 1000
> >>> requests, how nginx map 1000 requests to only 200 apache server
> >> Nginx can handle more than 10000 concurrent connections, but apache with
> >> prefork's max concurrent connections is the number of its process
> number. So
> >> Apache will send the 5** error.
> >> --
> >> Weibin Yao
> It's 1:1 model actually and for now nginx establishes HTTP 1.0
> connections only.
> In your circumstance, you use nginx as a reverse proxy, hence it's not
> nginx but your upstream's duty to handle real connections, I.E., your
> upstream's capacity must be big enough, otherwise, it will become the
> Joshua Zhu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nginx