Re: Bug in mod_ratelimit?
So far we’ve not seen much in the logs of our customer reports, however I was
able to get the following settings:
SetEnv rate-limit 512
SetEnv rate-initial-burst 625
When removed/commented out and/or removing mod_ratelimit the site would begin to work again.
When in a broken state we would see things like the following when visiting the page:
HTTP/1.1 200 OK
Date: Thu, 19 Jul 2018 13:33:05 GMT
http://XXXXXXXXX/wp-json/>; rel="https://api.w.org/", <http://XXXXXXXXX/>;
Keep-Alive: timeout=5, max=100
Content-Type: text/html; charset=UTF-8
We are working internally to attempt to get more of these answers.. having trouble so far reproducing in house.
Sorry I don’t have more info but I will reply again if we can get it reproducible.
Thanks for your quick response!
Release Manager - EasyApache
> On Jul 19, 2018, at 10:32 AM, Luca Toscano <toscano.luca@xxxxxxxxx> wrote:
> Hi Cory,
> 2018-07-19 16:10 GMT+02:00 Cory McIntire <cory@xxxxxxxxxx>:
> Hello all,
> We’re starting to see some issues where mod_ratelimit change here:
> *) mod_ratelimit: fix behavior when proxing content. PR 62362.
> [Luca Toscano, Yann Ylavic]
> Is causing some sites to load in plain text/source code…
> We haven’t found the connection beyond unloading mod_ratelimit which resolves the issue,
> and its not happening everywhere, just curious if anyone else is seeing this?
> I’ll report back once I have more info on further factors involved.
> Thanks a lot for reporting this. Can you add a bit more info about how to reproduce (httpd config I mean)? Anything relevant in the error logs?
Description: S/MIME cryptographic signature