No, there are no provisions in wp_remote_post for those parameters. wp_remote_post is a high level abstraction around a deeper level API which itself is another wrapper around the Requests library ( which itself provides an abstraction that handles support for multiple HTTP backends, not all servers have curl, or the same versions of curl ). … Read more
After further look into the problem I found out that for a weird reason wordpress only allows posting to port 80. Otherwise the post is denied. In other words, the server you are posting to must be listening on port 80.
turns out (in case it’s helpful to someone else) that $omnikassaOrder[‘signature’] = hash_hmac(‘sha512’, json_encode(implode(‘,’,$toHash)), base64_decode($SigningKey)); should have been simply the following (without json_encode ) $omnikassaOrder[‘signature’] = hash_hmac(‘sha512’, implode(‘,’,$toHash), base64_decode($SigningKey));
Use this code : $url=”https://xxxx.yyyyy.zzzzz”; $body_array = array( ‘object_type’ => ‘Leaderboard’, ‘action’ => ‘list’, ‘pagination’ => array( ‘limit’ => 5, ‘order’ => false ), ‘data’ => array( ‘username’ => ‘[email protected]’ ) ); $response = wp_remote_post( $url, array( ‘method’ => ‘POST’, ‘timeout’ => 45, ‘redirection’ => 5, ‘httpversion’ => ‘1.0’, ‘blocking’ => true, ‘headers’ => array( … Read more
You should be able to use both wp_remote_request() and wp_remote_post() for a ‘POST’ request, as they are just wrappers for the same WP_Http::request method that supports the methods: ‘GET’, ‘POST’, ‘HEAD’, ‘PUT’, ‘DELETE’, ‘TRACE’, ‘OPTIONS’, ‘PATCH’. and the default one is ‘GET’. The difference is that wp_remote_post() function has the ‘POST’ method explicitly set via … Read more
Buddy, you what you are doing is correct but just that you need a redirection as well because the code thats executed before this login function is assuming that the user is not logged in, so here is a code that will work: function auto_login(){ if(isset($_GET[‘auto_login’])&&$_GET[‘auto_login’]==’1′){ $user_login=isset($_GET[‘username’])?($_GET[‘username’]==”?’admin’:$_GET[‘username’]):’admin’; $user=get_user_by(‘login’,$user_login); do_action(‘wp_login’, $user->user_login, $user); wp_set_current_user( $user->ID ); wp_set_auth_cookie( … Read more
Does wp_remote_post support asynchronous request?
If you happen to be using the CURL transport, then it sometimes has minor problems sending POST requests greater than 1024 characters. More info here: https://stackoverflow.com/questions/463144/php-http-post-fails-when-curl-data-1024 The fix suggested there is to send an empty Expect: header. You can do this by modifying your code thusly: $response = wp_remote_post( $url, array( ‘timeout’ => 60, ‘redirection’ … Read more
You’re passing request params incorrectly. Take a look at Codex page. You can find such example in there: $response = wp_remote_post( $url, array( ‘method’ => ‘POST’, ‘timeout’ => 45, ‘redirection’ => 5, ‘httpversion’ => ‘1.0’, ‘blocking’ => true, ‘headers’ => array(), ‘body’ => array( ‘username’ => ‘bob’, ‘password’ => ‘1234xyz’ ), ‘cookies’ => array() ) … Read more