Only use wp_remote_post() if you are actually posting something. Try using wp_remote_get() with a full url $url=”http://blabla.org/mailinglist/add?” . $user_email; $results = wp_remote_get( $url ); // var_dump( $results );
Here is a quick and dirty plugin that shows you how to achieve this (adapt this example to your own architecture and needs): <?php /* Plugin Name: Custom rewrite rule test */ add_action( ‘plugins_loaded’, array(Registration::get_instance(), ‘setup’) ); class Registration { protected static $instance = NULL; public function __construct() {} public static function get_instance() { NULL … Read more
Try this in wp-config.php: define( ‘WP_HTTP_BLOCK_EXTERNAL’, true );
The curl is sending a POST request, to convert this you’ll want to use wp_remote_post(). As described in the documentation, the request arguments are the same as WP_Http::request(), so let’s look there how we can replicate your current version. curl_setopt( $ch, CURLOPT_URL, $url ); just sets the URL. Already doing this with wp_remote_post() curl_setopt( $ch, … Read more
It does not. Some functionality actively uses HTTP API and is cached – feed fetching, updates checking. But caching is always implemented at wrapper’s level. Making HTTP request without context is too unspecific to make educated guess about caching needs (one minute or one hour).
Ad Timeout You should be able to get around the timeout using a filter add_filter( ‘http_request_timeout’, ‘wpse35826_timeout_extd’ ); function wpse35826_timeout_extd( $time ) { // Default timeout is 5 return 10; } Choose the right protocol/scheme About your protocol/scheme problem: If it’s your local install, you can use the conditional. function wpse35826_remote_get( $args ) { $protocol … Read more
The best way to check the referrer will depends of what are you trying to do. You can use wp_get_referer() or wp_get_original_referer(), but if you want to check the referer for security reasons you should definitely use other functions like check_admin_referer(), check_ajax_referer(), wp_referer_field() or other of the WordPress Nonces related functions.
Disclaimer: I can’t give you a real explanation why this happens. I investigated this issue multiple times and (like you) didn’t even get a consistent error behavior. Anyway: Every sort of RESTful remote request using a remote API is painful and error prone – it simply highly depends what the counter part gives you… not. … Read more
There are no answers here yet, but atleast we ended up using a combination of WP REST API and WP OAuth Server. The WP REST API was really easy to work with, as it provided a common framework to respond to HTTP requests. I found it similar to ASP.NET Web API, as that’s the framework … Read more
This doesn’t seem to be error coming from WP itself, but is likely generated by curl, which WP likes to pick first for network requests. I’d try to replicate request with curl by hand on your hosting and elsewhere. If you are content with doing network request in other way you can tweak to make … Read more