It is something I had tried to work around @bollim . WordPress does not like when plugins have a security bypass on their functions. This is what the results say:
- The URL might be blocked by the WordPress security settings. WordPress has a number of security features that can block certain types of requests, including requests to known malicious websites.
- The URL might be invalid. If the URL is not formatted correctly, wp_safe_remote_get or wp_safe_remote_post will not be able to download it.
- The website might be down. If the website that the URL points to is down, wp_safe_remote_get or wp_safe_remote_post will not be able to download it.
- The website might be using a firewall that blocks WordPress requests. Some websites use firewalls to block requests from bots and other automated scripts. If wp_safe_remote_get or wp_safe_remote_post is being used by a bot, it might be blocked by the firewall.
There may be a way around it, but I probably can’t get it approved in the plugin library itself, because it requires changing the arguments to allow unsafe urls. I will review the rules of plugins and see if I can work it in for a future release.
But there is an argument for reject_unsafe_urls
In the plugin itself, or preferrably a custom functions.php file, you can try adding this.
function turn_off_reject_unsafe_urls($args) {
$args[‘reject_unsafe_urls’] = false;
return $args;
}
add_filter(‘http_request_args’, ‘turn_off_reject_unsafe_urls’);