The WP_Http class is essentially a wrapper for cURL in the same way that wpdb is essentially a wrapper for mysqli. As such, implemented properly, using cURL directly is exactly as safe as using WP_Http (since WP_Http uses cURL to make the requests). That said, implementing cURL functions optimally isn’t the easiest thing in the … Read more
There’s the XML RPC – the Remote Posting Protocol – that is already in use by WP.org Applications. What you’re searching for is wp.newPost. The API is extensible. The URL for the XML RPC is http://example.com/xmlrpc.php To send data to WP, use xmlrpc_encode_request() where the first argument would be wp.newPost and second one your arguments … Read more
I don’t know of a plugin that does it in a general way; for the most part, you’ll need to build something custom for each specific API you intend to communicate with. For your purposes, the key function will be wp_remote_post(), which is a wrapper for the POST method of WP’s HTTP class. (Use this … Read more
Lots of places in WordPress use xml_parse including the Atom library, the XML-RPC Library that we use, and SimplePie The oembed class uses SimpleXML. The WordPress Importer and Jetpack actually use both (Jetpack for different things, and the importer tries to use SimpleXML and falls back if it doesn’t exist). Basically, there’s nothing built into … Read more
AFAIK URL encoding the cookie value is still kind of a defacto standard, it’s an ancient relict based on the old, ugly Netscape cookie specs, that basically says that semicolons, commas and whitespaces are disallowed, and should be encoded, for example using URL encoding. Neither does it does it require enocding, nor does it force … Read more
// make request… (optionally save in transient for faster future fetches) $dom = new DOMDocument(); $dom->loadHTML(wp_remote_retrieve_body($request)); $sections=$dom->getElementsByTagName(“section”); foreach ($sections as $section) { // Do something… }
The (built-in) Requests class lets you call multiple requests simultaneously: Requests::request_multiple. <?php $requests = Requests::request_multiple([ [ ‘url’ => ‘https://www.mocky.io/v2/5acb821f2f00005300411631’, ‘type’ => ‘GET’, ‘headers’ => [ ‘Accept’ => ‘application/json’ ], ], [ ‘url’ => ‘https://www.mocky.io/v2/5acb821f2f00005300411631’, ‘type’ => ‘POST’, ‘headers’ => [ ‘Accept’ => ‘application/json’ ], ‘data’ => json_encode([ ‘text’ => ‘My POST Data’ ]) ], [ … Read more
[*][**] So is there ever any other situation in which I would want to use wp_remote_post or should I always stick with wp_safe_remote_post? The two functions are exactly the same, except wp_safe_remote_post() sets the reject_unsafe_urls argument to true. That argument causes the URL to be passed through wp_http_validate_url() in WP_Http::request(). From that function, we see … Read more
After quite some time letting the error message bugging my screen, I figured out a way to solve this. Yes, it’s a timeout issue, and the codex didn’t help me much. So I tried another approach, by setting a filter; add_filter( ‘http_request_timeout’, ‘wp9838c_timeout_extend’ ); function wp9838c_timeout_extend( $time ) { // Default timeout is 5 return … Read more
Update & the internal WP HTTP API A slightly modified version of my answer to this question, but also as a plugin that shows how it could work. Note: The code is not tested – I don’t know your server setup, etc. – and just written out of my head. You’ll have to test it, … Read more