[wp-meta] [Making WordPress.org] #5458: Redirects should not trigger 429 responses, and rate limiting should be relaxed.

[Making WordPress.org]

#5458: Redirects should not trigger 429 responses, and rate limiting should be
relaxed.
----------------------------+---------------------
 Reporter:  jonoaldersonwp  |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  high            |   Milestone:
Component:  General         |  Resolution:
 Keywords:  seo             |
----------------------------+---------------------

Comment (by dd32):

 Just noting that it's impossible to rate limit redirects at a different
 rate than non-redirects.

 Due to how nginx
 [https://nginx.org/en/docs/http/ngx_http_limit_req_module.html rate
 limiting] works, the counters are updating prior to the request being
 made, and the blocking is applied prior to the system processing the
 request. As a result, the module does not know if the request is a
 redirect either at the point of bumping the request counters or blocking
 the request from happening.

 The only way to resolve that is to increase the allowed rate limits, or
 fix the clients which are requesting pages at a too high rate that
 ultimately triggers the blocking.

 ----

 Consolidating redirects / etc can somewhat be done (and has been), but the
 vast majority are not worth the effort or are almost impossible to do so
 due to the varied places that the redirects happen, as has been explained
 many times.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5458#comment:6>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org