No because one user (web browser) can easily open 20 or more
simultaneous
connections to get a better web response.
A bot might be less prone to do the same but most connect at about 5
simultaneous connections.
The limit_req will only be used for requests to dynamic pages, so
there
should only be one connection per user at a time.
But using my example config, which only allows 1 request per second per
user, then wouldn’t limit_conn be superfluous? You can’t have more than
one
connection for a single request, surely?
I’ll paste the config again here as it got missed off the previous
quote:
As you were said before, a client might create multiple connections.
nginx works per request on a connection. Several requests in parallel
from
different TCP connections (for the HTTP module) are not the same as
several
following requests on the same connection.
Limiting the number of requests applies to every connection in parallel,
so
the total requests rate per client is nbConn * nbReq / timeUnit.
limit_conn and limit_req work together in this formula.
Do not assume things that are not said. I personally did exactly that on
numerous occasions. :o)
No because one user (web browser) can easily open 20 or more
simultaneous connections to get a better web response.
A bot might be less prone to do the same but most connect at about 5
simultaneous connections.
The limit_req will only be used for requests to dynamic pages, so there
should only be one connection per user at a time.
Posted at Nginx Forum:
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.