I suspect this is the cause in the Requests library that powers WP_HTTP: Transfer & connect timeouts, in seconds & milliseconds cURL is unable to handle timeouts under a second in DNS lookups, so we round those up to ensure 1-999ms isn’t counted as an instant failure. The code looks to be here: https://github.com/WordPress/Requests/blob/90db63ab54449c071fc2192a4fc3487cafbf67d0/src/Transport/Curl.php#L448-L460 if … Read more
PHP is synchronous language by design so it must wait for each line to be executed. If you call post request with 15s timeout you must wait untill webservice send response or 15s timeout limit. As I see in the core blocking parameter will not spawn process but simply do not parse response saving you … Read more
WordPress has the action send_headers, which you can use to make it send additional headers: add_action( ‘send_headers’, ‘add_header_acao’ ); function add_header_acao() { header( ‘Access-Control-Allow-Origin: *’ ); } See the documentation http://codex.wordpress.org/Plugin_API/Action_Reference/send_headers
You shouldn’t post directly to your plugin file – WordPress won’t be loaded, and you shouldn’t load it manually. Use the AJAX API and an action hook to handle it (note it doesn’t need to be an actual AJAX request): function wpse_180814_post_to_plugin( $name, $email ) { $result = wp_remote_post( admin_url( ‘admin-ajax.php’ ), array( ‘body’ => … Read more
wp_remote_request header error even though working properly with cURL
I solved it by changing the method to PUT & httpversion to 1.1
You can’t. The requests library that comes bundled in WordPress doesn’t support this. The reason for this is that the request_multiple function only accepts these parameters: * @param array $requests Request data (array of ‘url’, ‘headers’, ‘data’, ‘options’) as per {@see Requests_Transport::request} body is not one of those parameters, which explains why your request is … Read more
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 );
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.
As a general note, there’s the http-api (you’ve already used it to tag your question) that has an archive. WP HTTP API Here’s a list of “How to”-answers about the HTTP API basics chose the right protocol filter the request uri/url. download a file from a remote location deactivate HTTP requests Post Data Yes, you … Read more