При написании плагинов к WordPress приходится править curl на wp_remote_request() ибо иначе ругается поддержка WP plugin directory:
You will not be able to submit another plugin while this one is being reviewed, so please read the email carefully. We know it can be long, but you must follow the directions at the end as not doing so will result in your review being delayed. It is required for you to read and reply to these emails, and failure to do so will result in significant delays with your plugin being accepted.
## Including your own CURL code
WordPress comes with an extensive HTTP API that should be used instead of creating your own curl calls. It’s both faster and more extensive. It’ll fall back to curl if it has to, but it’ll use a lot of WordPress’ native functionality first.
Простейший пример с базовой авторизацией.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 |
//неправильно $ch = curl_init($url); curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1); curl_setopt($ch, CURLOPT_HEADER, false); curl_setopt($ch, CURLOPT_FRESH_CONNECT, 1); curl_setopt($ch, CURLOPT_CONNECTTIMEOUT, 0); curl_setopt($ch, CURLOPT_TIMEOUT, 30); curl_setopt($ch, CURLOPT_USERPWD, AUTH_USER.":".AUTH_PASSWORD); $response = curl_exec($ch) //правильно $args = array( 'headers' => array( 'Authorization' => 'Basic ' . base64_encode( AUTH_USER. ':' . AUTH_PASSWORD ) ) ); $response = wp_remote_request( $url, $args ); |
Простая замена но с подвохом, который чреват ошибками. CURLOPT_USERPWD эта опция у curl без base64. Потому что само расширение формирует заголовок для базовой авторизации.
Свежие комментарии