Dehydrated caused rate limits to be reached

Semi-related (let me know if I should open a separate topic), but does anyone know more about the underlying redirects that caused this problem with dehydrated? Is it new that requests like http://cert.int-x3.letsencrypt.org perform a redirect?

For what it’s worth, that URL doesn’t seem to be redirecting for me now, but I know over the weekend I had been observing the staging environment performing redirects off and on for http://cert.stg-int-x1.letsencrypt.org/ (redirecting to https://letsencrypt.org/cert.stg-int-x1/). However, those redirects seemed somewhat intermittent, sometimes I’d get a 200 OK response, and other times a 301 redirect.

All of this is obviously solved by the upgrade to the dehydated library to follow redirects, I was just curious about the underlying change and whether the introduction of redirects was documented anywhere or if any other libraries besides dehydrated might be affected. Thanks!