veppa

Hello,

Thank you for reporting. I added fix and released new version 1.3.10.

Yes, it is by design this way.

“Custom rules” work only in “smart block” mode. For this reason all requests obey smart block rules, including 3 second page generation rule.

“Smart block” designed to make blocking simple, with one switch. “Custom rules” added to overwrite “Smart block” with individual requests related to particular plugin or domain.

Main goal was to prevent WordPress from slow loading or timing out due to an excessive number of slow WP_HTTP requests.

I waited couple days to test workaround for this.

You can add an other rule:

allow: all - allow in: everywhere

This way all requests are allowed, your initial blocking rule will also work.

But downside is your logs will have lots of cron jobs requests( WP_HTTP made to wp-cron.php). Originally they are not logged. But when “allow” custom rule applied they are logged in order to show that custom rule applied to it.

Hello,

I assume that you are using http-requests-manager plugin in “Smart block” operation mode. In that case you can explicitly allow WP_HTTP external requests that cause infinite loop.

First check what requests are being blocked too many times in “Tools” -> “HTTP Requests Manager” page.

Use “group by page type” from dropdown to see on which page type too many blocking happens.
Use “group by request domain” from dropdown to see on which domain too many blocking happens.

I do not see logs from that page in you report so I can assume following values.

Most blocking happens on “rest_api” page type to “SOMEDOMAIN.com” domain. Using this data you can create following custom rule:

1. Navigate to “Settings” tab in “Tools” -> “HTTP Requests Manager” page
2. Make sure operation mode is “Smart block”.
3. Click “Add new” button next to ‘Custom rules for “Smart Block” mode’ text.
4. Create following rule:
   What -> “domain” -> “SOMEDOMAIN.com”,
   Where -> “rest_api”,
   Action -> “Allow”,
   Then click “Save changes” button.

This should prevent blocking particular external request and avoid infinite loop caused by “custom code” or “other plugin”.

View tutorial to explicitly allow some external WP_HTTP requests.

Why infinite loop happens?

1. http-requests-manager plugin blocks some WP_HTTP requests based on “operation mode”.
2. “Other plugin” or “custom code” expects successful response from remote WP_HTTP request. When request is not valid then it tries to get valid response and sends external request again and again (infinite times).

Optimal solution should be optimizing “Other plugin” or “custom code” to avoid infinite loop. Because any external request can fail due to network or server error. And that failure should not create infinite loop.

To fix timeout issues when loading reports, in version 1.3.7 I have added response data truncating feature. So 50% less data should be used when loading reports.

Compressed (gzip, deflate, brotli etc.) report data ~100 kb, uncompressed 1-2 MB.

Make sure that your web server and web browser uses data compression so only around 100kb data loaded when viewing reports.

Regards.

Thank you for reaching out.

Increased custom rule limit to 30 in version 1.3.6.

Hope it meets your requirements.

Regards.

HTTP Requests Manager plugin is not related to search.

I found another one in WordPress repository that might help. https://ww.wp.xz.cn/plugins/search-limiter-blocker/

Regards.

Released fix with version 1.3.5.

Regards.