curl_version

Last updated: Fri, 13 Nov 2009

curl_setopt

(PHP 4 >= 4.0.2, PHP 5)

curl_setopt — Define uma opção para a transferencia cURL

Descrição

bool curl_setopt ( resource $ch , int $option , mixed $value )

Define uma opção para o manipulador de sessão cURL indicado.

Parâmetros

ch

Um manipulador cURL retornado por curl_init().

option

A CURLOPT_XXX opção a definir.

value

O valor a ser definido em option .

value deve ser um booleano para os seguintes valores do parâmetro option :

Opção	Definir `value` para	Notas
`CURLOPT_AUTOREFERER`	`TRUE` para definir automaticamente um campo Referer: nas requisições aonde ele segue um redirecionamento Location:.	Disponível desde PHP 5.1.0.
`CURLOPT_BINARYTRANSFER`	`TRUE` para retornar a saída crua quando `CURLOPT_RETURNTRANSFER` é usado.
`CURLOPT_COOKIESESSION`	`TRUE` para marcar este como um novo cookie de sessão. Ela irá forçar a libcurl a ignorar todos os cookies que esteja a ponto de carregar que sejam "cookies de sessão" da sessão anterior. Por padrão, libcurl sempre salva e carrega todos os cookies, independente se sejam cookies de sessão ou não. Cookies de sessão são cookies sem data de expiração o que significa que devem estar vivos e existir apenas para essa sesão apenas.	Disponível desde PHP 5.1.0.
`CURLOPT_CRLF`	`TRUE` para converter finais de linha Unix para finais de linha CRLF nas transferencias.
`CURLOPT_DNS_USE_GLOBAL_CACHE`	`TRUE` para usar um cache de DNS global. Esta opção não é thread-safe e esta ativada por padrão.
`CURLOPT_FAILONERROR`	`TRUE` para falhar silenciosamente se o codigo HTTP retornado for maior ou igual a 400. O funcionamento padrão é retornar a pagina normalmente, ignorando o codigo.
`CURLOPT_FILETIME`	`TRUE` para tentar obter a data de modificação do documento remoto. Este valor pode ser obtido usando a opção `CURLINFO_FILETIME` com curl_getinfo().
`CURLOPT_FOLLOWLOCATION`	`TRUE` para seguir qualquer cabeçalho "Location: " que o servidor envie como parte do cabeçalho HTTP (note que isto é recursivo, PHP irá seguir tantos cabeçalhos "Location: " quantos sejam enviados, a menos que `CURLOPT_MAXREDIRS` seja definido).
`CURLOPT_FORBID_REUSE`	`TRUE` para forçar a conexão ser fechada explicitamente quando o processamento seja terminado, e não ser guardada para reuso.
`CURLOPT_FRESH_CONNECT`	`TRUE` para forçar o uso de uma nova conexão ao invés de uma guardada em cache.
`CURLOPT_FTP_USE_EPRT`	`TRUE` para usar EPRT (e LPRT) ao fazer downloads FTP ativos. Use `FALSE` para desabilitar EPRT e LPRT e usar apenas PORT.	Adicionado no PHP 5.0.0.
`CURLOPT_FTP_USE_EPSV`	`TRUE` para tentar primeiro um comando EPSV pára transferencias FTP antes de reverter de volta para PASV. Defina como `FALSE` para desabilitar EPSV.
`CURLOPT_FTPAPPEND`	`TRUE` para adicionar ao arquivo remoto ao invés de sobrescreve-lo.
`CURLOPT_FTPASCII`	um apelido para `CURLOPT_TRANSFERTEXT`. Use aquela ao invés.
`CURLOPT_FTPLISTONLY`	`TRUE` para listar apenas os nomes de um diretório FTP.
`CURLOPT_HEADER`	`TRUE` para incluir o cabeçalho na saída.
`CURLOPT_HTTPGET`	`TRUE` para redefinir o metodo de solicitação HTTP para GET. já que GET é o padrão, isto apenas é necessário se o metodo de solicitação foi modificado.
`CURLOPT_HTTPPROXYTUNNEL`	`TRUE` para fazer tunel através de um servidor HTTP proxy indicado.
`CURLOPT_MUTE`	`TRUE` para ser compeltamente silencioso no que diz respeito as funções cURL.
`CURLOPT_NETRC`	`TRUE` para procurar no arquivo `~/.netrc` um nome de usuário e senha para o local a qual a conexão remota esta sendo estabelecida.
`CURLOPT_NOBODY`	`TRUE` para excluir o corpo da saída. O metodo da solicitação é então definido como HEAD. Mudar isto para `FALSE` não muda-o para o GET.
`CURLOPT_NOPROGRESS`	`TRUE` para desabilitar o medidor de progresso para as transferencias cURL. Nota: PHP automaticamente define essa opção como `TRUE`, isto deve ser modificado apenas para fins de debug.
`CURLOPT_NOSIGNAL`	`TRUE` para ignorar qualquer função cURL que faça com que um sinal seja enviado para o processo PHP. Isto é ativado por padrão em servidores multi-tarefa assim opções de limite de tempo ainda podem ser usadas.	Adicionado no cURL 7.10 e PHP 5.0.0.
`CURLOPT_POST`	`TRUE` para fazer um HTTP POST normal. Este POST é do tipo normal application/x-www-form-urlencoded, mais comunmente usado pelos formulários HTML.
`CURLOPT_PUT`	`TRUE` para enviar um arquivo usando HTTP PUT. O arquivo a enviar deve estar definido com `CURLOPT_INFILE` e `CURLOPT_INFILESIZE`.
`CURLOPT_RETURNTRANSFER`	`TRUE` para retornar a transferencia como uma string de valor de retorno de curl_exec() ao invés de enviar diretamente para a saída.
`CURLOPT_SSL_VERIFYPEER`	`FALSE` para fazer o cURL parar de verificar o certificado do cliente. Certificados alternativos para verificar podem ser definidos com a opção `CURLOPT_CAINFO` ou um diretório de certificados pode ser definido com a opção `CURLOPT_CAPATH`. `CURLOPT_SSL_VERIFYHOST` também precisa ser definido como `TRUE` ou `FALSE` se `CURLOPT_SSL_VERIFYPEER` esta desabilitado (o padrão é 2).	`TRUE` por padrão a partir do cURL 7.10. Instalado por padrão a partir do cURL 7.10.
`CURLOPT_TRANSFERTEXT`	`TRUE` para usar o modo ASCII para transferencias FTP. Para LDAP, ele obtem os datos em texto simples ao invés de HTML. Em Sistemas Windows, ele não irá definir STDOUT para o modo binário.
`CURLOPT_UNRESTRICTED_AUTH`	`TRUE` para continuar enviando o nome de usuário e senha ao seguir localizações (usando `CURLOPT_FOLLOWLOCATION`), mesmo que o nome do servidor tenha mudado.	Adicionado no PHP 5.0.0.
`CURLOPT_UPLOAD`	`TRUE` para preparar para o envio de um arquivo.
`CURLOPT_VERBOSE`	`TRUE` para enviar muita informação para a saída. Escreve a saída para STDERR, ou para o arquivo especificado usando `CURLOPT_STDERR`.

value deve ser um inteiro para os seguintes valores do parâmetro option :

Opção	Definir `value` como	Notas
`CURLOPT_BUFFERSIZE`	O tamanho do buffer a usar em cada lida. Não há garantia de que este pedido será cumprido, entretando.	Adicionado no cURL 7.10 e PHP 5.0.0.
`CURLOPT_CLOSEPOLICY`	Ou `CURLCLOSEPOLICY_LEAST_RECENTLY_USED` ou `CURLCLOSEPOLICY_OLDEST` . Existem ainda três outras constantes CURLCLOSEPOLICY_, mas cURL ainda não as suporta.
`CURLOPT_CONNECTTIMEOUT`	O número de segundos para esperar ao tentar se conectar. Use 0 para esperar infinitamente.
`CURLOPT_DNS_CACHE_TIMEOUT`	O número de segundos para manter entradas DNS na memória. Esta opção é definida para 120 (2 minutos) por padrão.
`CURLOPT_FTPSSLAUTH`	O método de autenticação FTP (quando é ativado): CURLFTPAUTH_SSL (tentar SSL primeiro), CURLFTPAUTH_TLS (tentar TLS primeiro), ou CURLFTPAUTH_DEFAULT (deixar cURL decidir).	Adicionado no cURL 7.12.2 e PHP 5.1.0.
`CURLOPT_HTTP_VERSION`	`CURL_HTTP_VERSION_NONE` (padrão, deixa o CURL decidir qual versão usar), `CURL_HTTP_VERSION_1_0` (força HTTP/1.0), ou `CURL_HTTP_VERSION_1_1` (força HTTP/1.1).
`CURLOPT_HTTPAUTH`	O metodo de autenticação HTTP a usar. As opções são: `CURLAUTH_BASIC` , `CURLAUTH_DIGEST` , `CURLAUTH_GSSNEGOTIATE` , `CURLAUTH_NTLM` , `CURLAUTH_ANY` , e `CURLAUTH_ANYSAFE` . O operador de bits \| (ou) pode ser usado para combinar mais de um metodo. Se isso for feito, o cURL irá conversar com o servidor e ver quais métodos ele suporta e escolher o melhor. `CURLAUTH_ANY` é um apelido para CURLAUTH_BASIC \| CURLAUTH_DIGEST \| CURLAUTH_GSSNEGOTIATE \| CURLAUTH_NTLM. `CURLAUTH_ANYSAFE` é um apelido para CURLAUTH_DIGEST \| CURLAUTH_GSSNEGOTIATE \| CURLAUTH_NTLM.	Adicionado no PHP 5.0.0.
`CURLOPT_INFILESIZE`	O tamanho experado, em bytes, do arquivo ao enviar um arquivo para um local remoto.
`CURLOPT_LOW_SPEED_LIMIT`	A velocidade de transferencia, em bytes por segundos, a qual a transferência deve estar abaixo durante de `CURLOPT_LOW_SPEED_TIME` segundos para o PHP considerar a transferência muito lenta e abortar.
`CURLOPT_LOW_SPEED_TIME`	O número de segundos que a transferência deve estar abaixo de `CURLOPT_LOW_SPEED_LIMIT` para o PHP considerar a transferência lenta de mais e abortar.
`CURLOPT_MAXCONNECTS`	O número máximo de conexões persistentes que são permitidas. Quando o limite é atingido, `CURLOPT_CLOSEPOLICY` é usado para determinar qual conexão deve ser fechada.
`CURLOPT_MAXREDIRS`	O número máximo de redirecionamentos HTTP a seguir. Use esta opção em conjunto com `CURLOPT_FOLLOWLOCATION`.
`CURLOPT_PORT`	Um número alternativo de porta para conectar.
`CURLOPT_PROXYAUTH`	Os métodos HTTP de autenticação usados para conectar ao servidor proxy. Use as mesmas mascaras de bits descritas em `CURLOPT_HTTPAUTH`. Para autenticação com o proxy, apenas `CURLAUTH_BASIC` e `CURLAUTH_NTLM` são suportados atualmente.	Adicionado em cURL 7.10.7 e PHP 5.1.0.
`CURLOPT_PROXYPORT`	O número de porta para conectar ao proxy. Este número de porta também pode ser definido em `CURLOPT_PROXY`.	Adicionado no PHP 5.0.0.
`CURLOPT_PROXYTYPE`	Ou `CURLPROXY_HTTP` (padrão) ou `CURLPROXY_SOCKS5` .	Adicionado no cURL 7.10 e PHP 5.0.0.
`CURLOPT_RESUME_FROM`	O índice, em bytes, a partir do qual continuar a transferencia.
`CURLOPT_SSL_VERIFYHOST`	1 para conferir a existencia do nome comum no certificado SSL do cliente. 2 para conferir a existencia de um nome comum e também conferir se combina com o nome de servidor dado.
`CURLOPT_SSLVERSION`	A versão SSL (2 ou 3) a ser usada. por padrão o PHP tentará determinar isso por sí mesmo, entretando em alguns casos deve ser definido manualmente.
`CURLOPT_TIMECONDITION`	Como `CURLOPT_TIMEVALUE` é tratado. Use `CURL_TIMECOND_IFMODSINCE` para retornar apagina apenas se foi modificada desde o tempo especificado em `CURLOPT_TIMEVALUE`. Se não foi modificada um cabeçalho "304 Not Modified" assumindo que `CURLOPT_HEADER` seja `TRUE`. Use `CURL_TIMECOND_IFUNMODSINCE` para o efeito reverso. `CURL_TIMECOND_IFMODSINCE` é o padrão.	Adicionado no PHP 5.1.0.
`CURLOPT_TIMEOUT`	O número máximo de segundos que uma função cURL pode executar.
`CURLOPT_TIMEVALUE`	O tempo em segundos desde 1º de Janeiro de 1970. O tempo será usado por `CURLOPT_TIMECONDITION`. Por padrão, `CURL_TIMECOND_IFMODSINCE` é usado.

value deve ser uma string para os seguintes valores do parâmetro option :

Opção	Definir o `value` para	Notas
`CURLOPT_CAINFO`	O nome do arquivo contendo um ou mais certidicados para verificar o peer. Esta opção apenas tem sentido em conjunto com `CURLOPT_SSL_VERIFYPEER`.
`CURLOPT_CAPATH`	Um diretório que contem vários certificados CA. Use este opção em conjunto com `CURLOPT_SSL_VERIFYPEER`.
`CURLOPT_COOKIE`	O conteúdo do cabeçalho "Set-Cookie: " a ser utilizado na requisição HTTP.
`CURLOPT_COOKIEFILE`	O nome do arquivo contendo os dados de cookie. O arquivo de cookie pode estar no formato Netscape, ou apenas no estilo de cabeçalhos HTTP salvos em um arquivo.
`CURLOPT_COOKIEJAR`	O nome do arquivo para salvar todos os cookies internos quando a conexão fechar.
`CURLOPT_CUSTOMREQUEST`	Um método de solicitação personalizado para usar ao invés de "GET" ou "HEAD" ao fazer uma solicitação HTTP. Isto é útil para fazer "DELETE" ou outras solicitações HTTP mais obscuras. Valores válidos são coisas como "GET", "POST", "CONNECT" e assim por diante; i.e. Do not enter a whole HTTP request line here. For instance, entrar "GET /index.html HTTP/1.0\r\n\r\n" estaria errado. Nota: Não faça isto sem ter certesa que o servidor suporte a requisição personaçlizada primeiro.
`CURLOPT_EGDSOCKET`	Como `CURLOPT_RANDOM_FILE`, exceto um nome de arquivo para um Entropy Gathering Daemon socket.
`CURLOPT_ENCODING`	O conteúdo do cabeçalho "Accept-Encoding: ". Isto ativa a decodificação da resposta. codificações suportadas são "identity", "deflate", e "gzip". Se for definida uma string vazia, "", um cabeçalho contendo todos os tipos de codificações suportados é enviado.	Adicionado no cURL 7.10.
`CURLOPT_FTPPORT`	O valor o qual vai ser usado para ter o endereço IP para usar com a instrução FTP "POST". A instrução "POST" diz ao servidor remoto conectar com o seu endereço IP especificado. A string deve ser um endereço IP simples, um nome de servidor, um nome de interface de rede (sob o Unix), ou apenas um simples "-" para usar o endereço IP padrão do sistema.
`CURLOPT_INTERFACE`	O nome da interface de rede de saída a usar. Isto pode ser um nome de interface, um endereço IP ou um nome de servidor.
`CURLOPT_KRB4LEVEL`	O nível de segurança KRB4 (Kerberos 4). Qualquer un dos seguintes valores (em ordem do menos ao mais poderoso) são válidos: "clear", "safe", "confidential", "private".. Se a string não combinar com um destes, "private" é usado. Definir esta opção como `NULL` irá desabilitar a segurança KRB4. Atualmente a segurança KRB4 funciona apenas com transações FTP.
`CURLOPT_POSTFIELDS`	Todos os dados para enviar em uma operação HTTP "POST". Para enviar um arquivo, adicione antes do nome do arquivo um @ e use o caminho completo. Isto pode ser passado como uma string codificada para url como 'para1=val1&para2=val2&...' ou como uma matriz com o nome do campo como índice e o dado do campo como valor.
`CURLOPT_PROXY`	O servidor HTTP proxy pelo qual passar as requisições.
`CURLOPT_PROXYUSERPWD`	Um nome de usuário e senha formatados como "[username]:[password]" para usar na conexão com o proxy.
`CURLOPT_RANDOM_FILE`	Um nome de arquivo para ser usado como semente para o gerador de números aleatórios para SSL.
`CURLOPT_RANGE`	Intervalo(s) de data para obter no formato "X-Y" aonde X ou Y é opcional. Transferencias HTTP também suportam vários intervalos, separados por vírgulas no formato "X-Y,N-M".
`CURLOPT_REFERER`	O conteúdo do cabeçalho "Referer: " a ser usado em uma solicitação HTTP.
`CURLOPT_SSL_CIPHER_LIST`	Uma lista de ciphers para usar com SSL. Por exemplo, RC4-SHA e TLSv1 são listas cipher validas.
`CURLOPT_SSLCERT`	O nome de um arquivo contendo um certificado formatado PEM.
`CURLOPT_SSLCERTPASSWD`	A senha necessária para usar o certificado `CURLOPT_SSLCERT`.
`CURLOPT_SSLCERTTYPE`	O formato do certificado. Formatos suportados são "PEM" (default), "DER", e "ENG".	Adicionado no cURL 7.9.3 e PHP 5.0.0.
`CURLOPT_SSLENGINE`	O identificador para o motor de criptografia da chave SSL privada especificada em `CURLOPT_SSLKEY`.
`CURLOPT_SSLENGINE_DEFAULT`	O identificador para o motor de criptografia usado para para operações assimétricas.
`CURLOPT_SSLKEY`	O nome de um arquivo contendo uma chave SSL privada.
`CURLOPT_SSLKEYPASSWD`	A senha secreta necessária para usar a chave privada SSL especificada em `CURLOPT_SSLKEY`. Nota: Já que esta opção contem uma senha sensível, lembre-se de manter o script PHP que a contem em segurança.
`CURLOPT_SSLKEYTYPE`	O tipo de chave para a chave SSL privada especificada em `CURLOPT_SSLKEY`. Tipos de chaves suportados são "PEM" (default), "DER", and "ENG".
`CURLOPT_URL`	A URL para obter. isto também pode ser definido ao inicializar a sessão com curl_init().
`CURLOPT_USERAGENT`	O conteúdo do cabeçalho "User-Agent: " a ser usado na solicitação HTTP.
`CURLOPT_USERPWD`	Um nome de usuário e senha formatado como "[username]:[password]" para usar para a conexão.

value deve ser uma matriz para os seguintes valores do parâmetro option :

Opção	Definir `value` como	Notas
`CURLOPT_HTTP200ALIASES`	Um array de respostas HTTP 200 que serão tratadas como respostas válidas e não como erros.	Adicionado no cURL 7.10.3 e PHP 5.0.0.
`CURLOPT_HTTPHEADER`	Um array de cabeçalhos HTTP a definir.
`CURLOPT_POSTQUOTE`	Um array de comandos FTP a executar no servidor depois de a requisição FTP ter sido realizada.
`CURLOPT_QUOTE`	Um array de comandos FTP a serem executados no servidor antes da requesição.

value deve ser um recurso stream (usando fopen(), por exemplo) para os seguintes valores do parâmetro option :

Opção	Define `value` como	Notas
`CURLOPT_FILE`	O arquivo na qual a transferencia deve ser escrita. O padrão é STDOUT (a janela do browser).
`CURLOPT_INFILE`	O arquivo que deve ser lido ao se fazer um upload.
`CURLOPT_STDERR`	Um local alternativo para se escrever os erros ao invés de STDERR.
`CURLOPT_WRITEHEADER`	O arquivo em que a parte do cabeçalho da transferencia é escrita.

value dese ser uma string que seja o nome de uma função de callback válida para os seguintes valores do parãmetro option :

Opção	Define `value` como	Notas
`CURLOPT_HEADERFUNCTION`	O nome da função de callback aonde a função de callback tem dois parâmetros. O primeiro é o recurso cURL, o segundo é uma string com os ados a serem escritos. Os dados do cabeçalho devem ser escritos usando esta função de callback. Retorna o número de bytes escritos.
`CURLOPT_PASSWDFUNCTION`	O nome da função de callback aonde a função de callback tem três parâmetros. O primeiro é o recurso cURL, o segundo é uma string contendo uma string para o pronpt da senha, e o terceiro é o limite de tamanho da senha. Retorna a string contendo a senha.
`CURLOPT_READFUNCTION`	O nome da função de callback aonde a função de callback tem dois parâmetros. O primeiro é o recurso cURL, e so segundo é uma string com os dados a serem lidos. Os dados devem ser lidos atráves dessa função de callback. Retorna o número de bytes lidos. Retorne 0 para indicar EOF (final do arquivo).
`CURLOPT_WRITEFUNCTION`	O nome da função de callback aonde a função de callback tem dois parâmetros. O primeiro é o recurso resource, e o segundo é a string com os dados a serem escritos. Os dados devem ser escritos usando essa função de callback. Deve retornar o número exato de bytes escritos ou isto irá falhar.

Valor Retornado

Retorna TRUE em caso de sucesso ou FALSE em falhas.

Exemplos

Exemplo #1 inicializando uma nova sessão cURL e obtendo uma pagina da internet


<?php
// create a new cURL resource
$ch = curl_init();

// set URL and other appropriate options
curl_setopt($ch, CURLOPT_URL, "http://www.example.com/");
curl_setopt($ch, CURLOPT_HEADER, false);

// grab URL and pass it to the browser
curl_exec($ch);

// close cURL resource, and free up system resources
curl_close($ch);
?>

Exemplo #2 Enviando um arquivo


<?php

/* http://localhost/upload.php:
print_r($_POST);
print_r($_FILES);
*/

$ch = curl_init();

$data = array('name' => 'Foo', 'file' => '@/home/user/test.png');

curl_setopt($ch, CURLOPT_URL, 'http://localhost/upload.php');
curl_setopt($ch, CURLOPT_POST, 1);
curl_setopt($ch, CURLOPT_POSTFIELDS, $data);

curl_exec($ch);
?>

O exemplo acima irá imprimir:

Array
(
    [name] => Foo
)
Array
(
    [file] => Array
        (
            [name] => test.png
            [type] => image/png
            [tmp_name] => /tmp/phpcpjNeQ
            [error] => 0
            [size] => 279
        )

)

Veja Também

curl_setopt_array() - Set multiple options for a cURL transfer

curl_version

curl_setopt_array

Last updated: Fri, 13 Nov 2009

add a note User Contributed Notes
curl_setopt

php dot net at NO dot sgerrand dot SPAM dot com
03-Nov-2009 05:01


Following from the comment made by Stan van de Burgt, if you change the post array to a string, PHP creates the post data successfully.



As a quick and dirty example of implementing this fix:



<?php



$ch = curl_init;

$url = 'http://www.example.com';



curl_setopt($ch, CURLOPT_URL, $url);

curl_setopt($ch, CURLOPT_POST, true);



foreach ($postData as $var) if (strpos($var, '@') === 0) {

    $postAsString = true;

}



if ($postAsString === true) {

    $str = '';



    foreach ($postData as $key => $val) {

        $str .= '&' . $key . '=' . $val;

    }



    $postData = substr_replace($str, '', 0, 1);

}



curl_setopt($ch, CURLOPT_POSTFIELDS, $postData);



curl_exec($ch);



?>



Hopefully this error gets fixed at a lower level in the PHP cURL library itself to stop the need for this ugly workaround.

Chris at PureFormSolutions dot com
22-Sep-2009 08:54


I've found that setting CURLOPT_HTTPHEADER more than once will clear out any headers you've set previously with CURLOPT_HTTPHEADER.



Consider the following:

<?php

    # ...



    curl_setopt($cURL,CURLOPT_HTTPHEADER,array (

        "Content-Type: text/xml; charset=utf-8",

        "Expect: 100-continue"

    ));



    # ... do some other stuff ...



    curl_setopt($cURL,CURLOPT_HTTPHEADER,array (

        "Accept: application/json"

    ));



    # ...

?>



Both the Content-Type and Expect I set will not be in the outgoing headers, but Accept will.

Stan van de Burgt
19-Sep-2009 07:41


If you get a "failed creating formpost data" upon curl_exec() when POSTing a form, check if one of the field values starts with the @ character.



Took me an hour or so to find out as I wanted to post a @reply tweet to twitter which typically start with @screenname.

Tyranoweb
04-Sep-2009 07:42


There is a function to send POST data in page with five parameters :





$post must be an array


$page is the page where POST datas will be send.


$n must be true to continue if they are php redirection (Location: )


$session must be define true if you want to use cookies 


$referer must be a link to get a wrong referer or only to have a referer.





<?php


function curl_data_post($post, $page, $n, $session, $referer)


    {


        if(!is_array($post))


        {


         return false;


        }


        


        $DATA_POST = curl_init();


        curl_setopt($DATA_POST, CURLOPT_RETURNTRANSFER, true);


        curl_setopt($DATA_POST, CURLOPT_URL, $page);


        curl_setopt($DATA_POST, CURLOPT_POST, true);


        if($n)


        {


         curl_setopt($DATA_POST, CURLOPT_FOLLOWLOCATION, true);


        }


        if($session)


        {


         curl_setopt($DATA_POST, CURLOPT_COOKIEFILE, 'cookiefile.txt');


         curl_setopt($DATA_POST, CURLOPT_COOKIEJAR, 'cookiefile.txt'); 


        }


        


        if($referer)


        {


         curl_setopt($DATA_POST, CURLOPT_REFERER, $referer); 


        }


        


        curl_setopt($DATA_POST, CURLOPT_POSTFIELDS, $post);


        $data = curl_exec($DATA_POST);


        if($data == false)


        {


         echo'Warning : ' . curl_error($DATA_POST);


         curl_close($DATA_POST);


         return false;


        }


        else


        {


         curl_close($DATA_POST);


         return $data;


        }


    }


?>

rob
24-Aug-2009 02:07


Whats not mentioned in the documentation is that you have to set CURLOPT_COOKIEJAR to a file for the CURL handle to actually use cookies, if it is not set then cookies will not be parsed.

Sylvain R
28-Jul-2009 08:05


When you are using CURLOPT_FILE to download directly into a file you must close the file handler after the curl_close() otherwise the file will be incomplete and you will not be able to use it until the end of the execution of the php process.





<?php





$fh = fopen('/tmp/foo', 'w');


$ch = curl_init('http://example.com/foo');


curl_setopt($ch, CURLOPT_FILE, $fh);


curl_exec($ch);


curl_close($ch);





# at this point your file is not complete and corrupted





fclose($fh);





# now you can use your file;





read_file('/tmp/foo');





?>

mikeseth at gmail dot com
15-Jul-2009 07:32


When using CURLOPT_FILE, pass it the file handle that is open for write only (eg fopen('blahblah', 'w+')). If you also open the file for reading (eg fopen('blahblah', 'rw')), curl will fail with error 23.

Victor Jerlin
03-Jul-2009 09:12


Seems like some options not mentioned on this page, but listed on http://curl.haxx.se/libcurl/c/curl_easy_setopt.html is actually supported.



I was happy to see that I could actually use CURLOPT_FTP_CREATE_MISSING_DIRS even from PHP.

xektrum at gmail dot com
02-Jul-2009 02:14


As of php 5.3 CURLOPT_PROGRESSFUNCTION its supported here's how:



<?php



function callback($download_size, $downloaded, $upload_size, $uploaded)

{

    // do your progress stuff here

}



$ch = curl_init('http://www.example.com');



// This is required to curl give us some progress

// if this is not set to false the progress function never

// gets called

curl_setopt($ch, CURLOPT_NOPROGRESS, false);



// Set up the callback

curl_setopt($ch, CURLOPT_PROGRESSFUNCTION, 'callback');



// Big buffer less progress info/callbacks

// Small buffer more progress info/callbacks

curl_setopt($ch, CURLOPT_BUFFERSIZE, 128);



$data = curl_exec($ch);



?>



Hope this help.

Andrew
14-Jun-2009 09:56


I noticed that if you want to get current cookie file after curl_exec() - you need to close current curl handle (like it said in manual), but if you want cookies to be dumped to file after any curl_exec (without curl_close) you can:





<?php


#call it normally


$ch = curl_init(); 


curl_setopt($ch, CURLOPT_HEADER, 0); 


curl_setopt($ch, CURLOPT_COOKIEFILE, "cookiefile"); 


curl_setopt($ch, CURLOPT_COOKIEJAR, "cookiefile"); 


curl_setopt($ch, CURLOPT_FOLLOWLOCATION, 1); 


curl_setopt($ch, CURLOPT_URL, 'http://www.example.com/'); 


$result1 = curl_exec($ch); 





#and then  make a temp copy


$ch_temp=curl_copy_handle(ch);


curl_close($ch);


$ch=$ch_temp;


?>





Only this way, if you close $ch_temp - cookies wont be dumped.

ericbianchetti at gmail dot com
04-Jun-2009 08:06


if you need to send a SOAP string that is the CURL you must use :





<?php


$ch = curl_init();


curl_setopt($ch, CURLOPT_URL, XML_POST_URL); 


curl_setopt ($ch, CURLOPT_HTTPHEADER, array('SOAPAction: ""'));    


curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1); 


curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, FALSE);


curl_setopt($ch, CURLOPT_POSTFIELDS, XML_PAYLOAD); 


curl_setopt($ch, CURLOPT_HEADER, 0);





$output = curl_exec($ch); 


?>





Note : Having based my snipet on Chemo demonstration (oscommerce user know who he is), XML_POST_URL and XML_PAYLOAD where defined as constant with define().





The point is : at the opposite of .xml , SOAP must send the header 'SOAPAction: ""' that can be a valid URI, an empty string (that is here) or nothing ('SOAPAction: '). The later case baing not accepted by all server, the second one indicating the target is the URI used to post the SOAP.


http://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc478383528

franciscocha at gmail dot com
19-May-2009 08:11


Example how to connect to FTPES (FTP explicit SSL). This script will connect to any FTPES server and out put the list of directories.



<?php

    $username = 'username';

    $password = 'password';

    $url = 'url';

    $ftp_server = "ftp://" . $username . ":" . $password . "@" . $url;

    

    echo "Starting CURL.\n";

    $ch = curl_init();

    echo "Set CURL URL.\n";

    

    //curl FTP

    curl_setopt($ch, CURLOPT_URL, $ftp_server);

    

    //For Debugging

    //curl_setopt($ch, CURLOPT_VERBOSE, TRUE);    

    

    //SSL Settings

    curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, FALSE);

    curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, FALSE);

    curl_setopt($ch, CURLOPT_FTP_SSL, CURLFTPSSL_TRY);

    

    //List FTP files and directories

    curl_setopt($ch, CURLOPT_FTPLISTONLY, TRUE);

    

    //Output to curl_exec

    curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);



    echo "Executing CURL.\n";

    $output = curl_exec($ch);

    curl_close($ch);

    echo "Closing CURL.\n";

    echo $output . "\n";



   $files = explode("\n", $output);

   print_r($files);

?>

ashooner - - gmail , com
22-Mar-2009 09:28


When passing CURLOPT_POSTFIELDS a url-encoded string in order to use Content-Type: application/x-www-form-urlencoded, you can pass a string directly:

<?php

curl_setopt(CURLOPT_POSTFIELDS, 'field1=value&field2=value2');

?>



rather than passing the string in an array, as in fred at themancan dot com's example.

Ariz Jacinto
02-Feb-2009 12:36


if unserialize() returns FALSE on a serialized PHP object due to an extraneous string (e.g. "1") appended at the end of the object, you need to set the ff cURL option:





<?php


curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);


?>

urkle at outoforder dot cc
28-Jan-2009 12:49


To send a post as a different content-type (ie.. application/json or text/xml) add this setopt call





<?php


curl_setopt($ch, CURLOPT_HTTPHEADERS,array('Content-Type: application/json'));


?>





[EDIT BY danbrown AT php DOT net: Contains a typofix by 'KdoubleU' on 3-FEB-09.]

fnjordy at gmail dot com
01-Dec-2008 05:28


Note that CURLOPT_RETURNTRANSFER when used with CURLOPT_WRITEFUNCTION has effectively three settings: default, true, and false.



default - callbacks will be called as expected.

true - content will be returned but callback function will not be called.

false - content will be output and callback function will not be called.



Note that CURLOPT_HEADERFUNCTION callbacks are always called.

saidk at phirebranding dot com
19-Nov-2008 07:31


Passing in PHP's $_SESSION into your cURL call:





<?php


session_start();


$strCookie = 'PHPSESSID=' . $_COOKIE['PHPSESSID'] . '; path=/';


session_write_close();





$curl_handle = curl_init('enter_external_url_here');


curl_setopt( $curl_handle, CURLOPT_COOKIE, $strCookie );


curl_exec($curl_handle);


curl_close($curl_handle);


?>





This worked great for me.  I was calling pages from the same server and needed to keep the $_SESSION variables.  This passes them over.  If you want to test, just print_r($_SESSION);





Enjoy!

dorphalsig at gmail dot com
10-Oct-2008 07:20


This may not be a surprise for many, but I know I bled my eyes out trying to implement this in php. And when I knew it was this simple, I really felt extremely stupid. So I put this just so google will save somebody some time in the future.





PHP NTLM AUTH





Make sure you have the 'curl' extension loaded


now just do...





<?php


curl_setopt($ch,CURLAUTH_NTLM);


curl_setopt($ch,CURLOPT_USERPWD,"$username:$password");


?>





and just continue to use curl in the ordinary fashion.

OPALA
26-Sep-2008 05:37


To fetch (or submit data to) multiple pages during one session,use this:





<?php


$ch = curl_init();


curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, FALSE);


curl_setopt($ch, CURLOPT_RETURNTRANSFER, TRUE);


curl_setopt($ch, CURLOPT_COOKIESESSION, TRUE);


curl_setopt($ch, CURLOPT_HEADER, 0);


curl_setopt($ch, CURLOPT_COOKIEFILE, "cookiefile");


curl_setopt($ch, CURLOPT_COOKIEJAR, "cookiefile");


curl_setopt($ch, CURLOPT_COOKIE, session_name() . '=' . session_id());


curl_setopt($ch, CURLOPT_FOLLOWLOCATION, 1);





curl_setopt($ch, CURLOPT_URL, 'http://example.com/page1.php');


$result1 = curl_exec($ch);





curl_setopt($ch, CURLOPT_URL, 'http://example.com/page2.php');


$result2 = curl_exec($ch);





curl_close($ch);


?>

rkirilow at gmail dot com
16-Sep-2008 06:34


Some of you may noticed that curl is not transferring cookies between sequent calls to a host. This is because you must activate curl`s "cookie parser". That is achieved using an external file like this:


<?php


curl_setopt(CURLOPT_FILE, '/tmp/cookies_file');


?>


If you don`t need to read any cookies but you still want the "cookie parser" use the same code but with dummy file with no data like '/dev/null', that way curl is storing cookies internaly per curl_handle:


<?php


curl_setopt(CURLOPT_FILE, '/dev/null');


?>





[EDIT BY danbrown AT php DOT net: In a note dated 26-SEP-08, (adamplumb AT gmail DOT com) offered the following addendum:





[It] should really be CURLOPT_COOKIEFILE.  I was bitten by this issue myself with code that previously worked for logging into a website and posting a form.  However, at some point the code just stopped working, and I eventually found that I needed to set this option to /dev/null for it to work.


]

George
22-Aug-2008 10:14


If you set CURLOPT_RESUME_FROM to resume the file, and then reuse the same Curl handle to download another file, you must reset the resume status by calling curl_setopt( $ch, CURLOPT_RESUME_FROM, 0 ). It will not reset, and will apply to all subsequent transfers even if the URL is the same.

w dot danford at electronics-software dot com
12-Aug-2008 03:12


Just a small detail I too easily overlooked.

<?php

/*  If you set:  */

curl_setopt ($ch, CURLOPT_POST, 1);

/* then you must have the data: */

curl_setopt ($ch, CURLOPT_POSTFIELDS, $PostData);

?>

I found with only the CURLOPT_POST set (from copy, paste editing of course) cookies were not getting sent with CURLOPT_COOKIE.  Just something subtle to watch out for.

fred at themancan dot com
05-Aug-2008 09:28


To find what encoding a given HTTP POST request uses is easy -- passing an array to CURLOPT_POSTFIELDS results in  multipart/form-data:





<?php


curl_setopt(CURLOPT_POSTFIELDS, array('field1' => 'value'));


?>





Passing a URL-encoded string will result in application/x-www-form-urlencoded:





<?php


curl_setopt(CURLOPT_POSTFIELDS, array('field1=value&field2=value2'));


?>





I ran across this when integrating with both a warehouse system and an email system; neither would accept multipart/form-data, but both happily accepted application/x-www-form-urlencoded.

jID
05-Aug-2008 09:56


if you use

<?php

curl_setopt($ch, CURLOPT_INTERFACE, "XXX.XXX.XXX.XXX");

?>

to specify IP adress for request, sometimes you need to get list of all your IP's.



ifconfig command will output something like:



rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500

    options=8<VLAN_MTU>

    inet 82.146.XXX.XXX netmask 0xffffffff broadcast 82.146.XXX.XXX

    inet 78.24.XXX.XXX netmask 0xffffffff broadcast 78.24.XXX.XXX

    inet 82.146.XXX.XXX netmask 0xffffffff broadcast 82.146.XXX.XXX

    inet 82.146.XXX.XXX netmask 0xffffffff broadcast 82.146.XXX.XXX

    inet 82.146.XXX.XXX netmask 0xffffffff broadcast 82.146.XXX.XXX

    inet 78.24.XXX.XXX netmask 0xffffffff broadcast 78.24.XXX.XXX

    inet 78.24.XXX.XXX netmask 0xffffffff broadcast 78.24.XXX.XXX

    ether XX:XX:XX:XX:XX:XX

    media: Ethernet autoselect (100baseTX <full-duplex>)

    status: active

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384

tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500

    Opened by PID 564

tun1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500

    Opened by PID 565

    Opened by PID 565



My solution for FreeBSD 6 and PHP 5 was:

<?php

  ob_start();

  $ips=array();

  $ifconfig=system("ifconfig");

  echo $ifconfig;

  $ifconfig=ob_get_contents();

  ob_end_clean();

  $ifconfig=explode(chr(10), $ifconfig);

  for ($i=0; $i<count($ifconfig); $i++) {

    $t=explode(" ", $ifconfig[$i]);

    if ($t[0]=="\tinet") {

      array_push($ips, $t[1]);

    }     

  }

  for ($i=0; $i<count($ips); $i++) {

    echo $ips[$i]."\n";

  }

?>



You will get list of IP adresses in $ips array, like:

82.146.XXX.XXX

78.24.XXX.XXX

82.146.XXX.XXX

82.146.XXX.XXX

82.146.XXX.XXX

78.24.XXX.XXX

78.24.XXX.XXX

ac at an dot y-co dot de
10-Jul-2008 03:08


If you want to connect to a server which requires that you identify yourself with a certificate, use following code. Your certificate and servers certificate are signed by an authority whose certificate is in ca.ctr.



<?php

curl_setopt($ch, CURLOPT_VERBOSE, '1');

curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, '1');

curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, '1');

curl_setopt($ch, CURLOPT_CAINFO,  getcwd().'/cert/ca.crt');

curl_setopt($ch, CURLOPT_SSLCERT, getcwd().'/cert/mycert.pem');

curl_setopt($ch, CURLOPT_SSLCERTPASSWD, 'password');

?>



If your original certificate is in .pfx format, you have to convert it to .pem using following commands

# openssl pkcs12 -in mycert.pfx -out mycert.key

# openssl rsa -in mycert.key -out mycert.pem

# openssl x509 -in mycert.key >> mycert.pem

nick at glype dot com
07-Jul-2008 02:18


Although CURLOPT_CLOSEPOLICY and the applicable choices are valid constants, setting this option with curl_setopt() always returns false. A quick google search suggests the option is deprecated and/or never worked.

heron at xnapid dot com
19-Jun-2008 07:19


Someone posted this under tmpfile (http://us3.php.net/manual/en/function.tmpfile.php#69419), and I thought it was particularly useful:





[The PHP function tmpfile()] is really useful for libcurl's CURLOPT_PUT feature if what you're trying to PUT is a string.   For example:





<?php


/* Create a cURL handle. */


$ch = curl_init();





/* Prepare the data for HTTP PUT. */


$putString = "Hello, world!";


$putData = tmpfile();


fwrite($putData, $putString);


fseek($putData, 0);





/* Set cURL options. */


curl_setopt($ch, CURLOPT_URL, "http://www.example.com");


curl_setopt($ch, CURLOPT_PUT, true);


curl_setopt($ch, CURLOPT_INFILE, $putData);


curl_setopt($ch, CURLOPT_INFILESIZE, strlen($putString));


/* ... (other curl options) ... */





/* Execute the PUT and clean up */


$result = curl_exec($ch);


fclose($putData);


curl_close($ch);


?>

Salil Kothadia
19-Jun-2008 02:02


In PHP5, for the "CURLOPT_POSTFIELDS" option, we can use:



<?php

$ch = curl_init($URI);

$Post = http_build_query($PostData);

curl_setopt($ch, CURLOPT_POSTFIELDS, $Post);

$Output = curl_exec($ch);

curl_close($ch);

?>

sgamon at yahoo dot com
09-Apr-2008 10:55


If you are doing a POST, and the content length is 1,025 or greater, then curl exploits a feature of http 1.1: 100 (Continue) Status.



See http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html#sec8.2.3



* it adds a header, "Expect: 100-continue".  

* it then sends the request head, waits for a 100 response code, then sends the content 



Not all web servers support this though.  Various errors are returned depending on the server.  If this happens to you, suppress the "Expect" header with this command:



<?php

curl_setopt($ch, CURLOPT_HTTPHEADER, array('Expect:'));

?>



See http://www.gnegg.ch/2007/02/the-return-of-except-100-continue/

john factorial
04-Apr-2008 02:22


Clarification for the CURLOPT_NOBODY option: by excluding the body from your request, you're effectively making a HEAD request. Use the CURLOPT_NOBODY option to return only the headers in the remote response.





Example:





<?php


function check_url($url) {


    $c = curl_init();


    curl_setopt($c, CURLOPT_URL, $url);


    curl_setopt($c, CURLOPT_HEADER, 1); // get the header


    curl_setopt($c, CURLOPT_NOBODY, 1); // and *only* get the header


    curl_setopt($c, CURLOPT_RETURNTRANSFER, 1); // get the response as a string from curl_exec(), rather than echoing it


    curl_setopt($c, CURLOPT_FRESH_CONNECT, 1); // don't use a cached version of the url


    if (!curl_exec($c)) { return false; }





    $httpcode = curl_getinfo($c, CURLINFO_HTTP_CODE);


    return ($httpcode < 400);


}


?>

c00lways at gmail dot com
04-Mar-2008 07:16


if you would like to send xml request to a server (lets say, making a soap proxy),


you have to set





<?php


curl_setopt($ch, CURLOPT_HTTPHEADER, Array("Content-Type: text/xml"));


?>





makesure you watch for cache issue:


the below code will prevent cache...





<?php


curl_setopt($ch, CURLOPT_FORBID_REUSE, 1);


curl_setopt($ch, CURLOPT_FRESH_CONNECT, 1);


?>





hope it helps ;)

mavook at gmail dot com
16-Feb-2008 04:26


If you try to upload file to a server, you need do CURLOPT_POST first and then fill CURLOPT_POSTFIELDS.





<?php


curl_setopt($ch, CURLOPT_POST, 1);


curl_setopt($ch, CURLOPT_POSTFIELDS, $postvars);


// ^^ This will post multipart/form-data


?>

jade dot skaggs at gmail dot com
07-Jan-2008 03:48


After much struggling, I managed to get a SOAP request requiring HTTP authentication to work.  Here's some source that will hopefully be useful to others. 





         <?php





         $credentials = "username:password";


         


         // Read the XML to send to the Web Service


         $request_file = "./SampleRequest.xml";


        $fh = fopen($request_file, 'r');


        $xml_data = fread($fh, filesize($request_file));


        fclose($fh);


                


        $url = "http://www.example.com/services/calculation";


        $page = "/services/calculation";


        $headers = array(


            "POST ".$page." HTTP/1.0",


            "Content-type: text/xml;charset=\"utf-8\"",


            "Accept: text/xml",


            "Cache-Control: no-cache",


            "Pragma: no-cache",


            "SOAPAction: \"run\"",


            "Content-length: ".strlen($xml_data),


            "Authorization: Basic " . base64_encode($credentials)


        );


       


        $ch = curl_init();


        curl_setopt($ch, CURLOPT_URL,$url);


        curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);


        curl_setopt($ch, CURLOPT_TIMEOUT, 60);


        curl_setopt($ch, CURLOPT_HTTPHEADER, $headers);


        curl_setopt($ch, CURLOPT_USERAGENT, $defined_vars['HTTP_USER_AGENT']);


        


        // Apply the XML to our curl call


        curl_setopt($ch, CURLOPT_POST, 1);


        curl_setopt($ch, CURLOPT_POSTFIELDS, $xml_data); 





        $data = curl_exec($ch); 





        if (curl_errno($ch)) {


            print "Error: " . curl_error($ch);


        } else {


            // Show me the result


            var_dump($data);


            curl_close($ch);


        }





?>

contacto at hardcode dot com dot ar
12-Dec-2007 06:34


hey hey hey!


the problem: curl_setopt($ch,FOLLOW_LOCATION,1);


the error: trouble with open_basedir and safe_mode


the solution: a function already developed by someone


the solution n 2: the same function, modifed, works great for me..





<?php


function curl_redir_exec($ch,$debug="")


{


    static $curl_loops = 0;


    static $curl_max_loops = 20;





    if ($curl_loops++ >= $curl_max_loops)


    {


        $curl_loops = 0;


        return FALSE;


    }


    curl_setopt($ch, CURLOPT_HEADER, true);


    curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);


    $data = curl_exec($ch);


    $debbbb = $data;


    list($header, $data) = explode("\n\n", $data, 2);


    $http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);





    if ($http_code == 301 || $http_code == 302) {


        $matches = array();


        preg_match('/Location:(.*?)\n/', $header, $matches);


        $url = @parse_url(trim(array_pop($matches)));


        //print_r($url);


        if (!$url)


        {


            //couldn't process the url to redirect to


            $curl_loops = 0;


            return $data;


        }


        $last_url = parse_url(curl_getinfo($ch, CURLINFO_EFFECTIVE_URL));


    /*    if (!$url['scheme'])


            $url['scheme'] = $last_url['scheme'];


        if (!$url['host'])


            $url['host'] = $last_url['host'];


        if (!$url['path'])


            $url['path'] = $last_url['path'];*/


        $new_url = $url['scheme'] . '://' . $url['host'] . $url['path'] . ($url['query']?'?'.$url['query']:'');


        curl_setopt($ch, CURLOPT_URL, $new_url);


    //    debug('Redirecting to', $new_url);





        return curl_redir_exec($ch);


    } else {


        $curl_loops=0;


        return $debbbb;


    }


}


?>





just use this function without de FOLLOW_LOCATION and should work. the problem was that when you get to the line where you return the data if http_code was different than 301 oe 302, $data has obsolete information or none. so $debbbb does the job.





hope this helps someone out there





thanks from argentina

Ojas Ojasvi
25-Sep-2007 03:52


<?php


/*


* Author: Ojas Ojasvi


* Released: September 25, 2007


* Description: An example of the disguise_curl() function in order to grab contents from a website while remaining fully camouflaged by using a fake user agent and fake headers.


*/





$url = 'http://www.php.net';





// disguises the curl using fake headers and a fake user agent.


function disguise_curl($url)


{


  $curl = curl_init();





  // Setup headers - I used the same headers from Firefox version 2.0.0.6


  // below was split up because php.net said the line was too long. :/


  $header[0] = "Accept: text/xml,application/xml,application/xhtml+xml,";


  $header[0] .= "text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5";


  $header[] = "Cache-Control: max-age=0";


  $header[] = "Connection: keep-alive";


  $header[] = "Keep-Alive: 300";


  $header[] = "Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7";


  $header[] = "Accept-Language: en-us,en;q=0.5";


  $header[] = "Pragma: "; // browsers keep this blank.





  curl_setopt($curl, CURLOPT_URL, $url);


  curl_setopt($curl, CURLOPT_USERAGENT, 'Googlebot/2.1 (+http://www.google.com/bot.html)');


  curl_setopt($curl, CURLOPT_HTTPHEADER, $header);


  curl_setopt($curl, CURLOPT_REFERER, 'http://www.google.com');


  curl_setopt($curl, CURLOPT_ENCODING, 'gzip,deflate');


  curl_setopt($curl, CURLOPT_AUTOREFERER, true);


  curl_setopt($curl, CURLOPT_RETURNTRANSFER, 1);


  curl_setopt($curl, CURLOPT_TIMEOUT, 10);





  $html = curl_exec($curl); // execute the curl command


  curl_close($curl); // close the connection





  return $html; // and finally, return $html


}





// uses the function and displays the text off the website


$text = disguise_curl($url);


echo $text;


?>





Ojas Ojasvi

charles at tastik dot net
01-Sep-2007 07:27


FYI,





Anyone trying to connect to .NET with CURL to send a simple XML post, pay attention to the following. This will save you hours! There is a previous note that I saw either on this page, or somewhere else on this site that explains the correct way to specify the header option is to create an array, then reference the array from the CURLOPT. 





ie.  Do something like this:





<?php


// Req. HTTP Header Values 


 $header[] = "Content-type: text/xml";





// Target URL


 $sendTo = "http://www.example.com";





// Post Data


 $post = "<?xml version=\"1.0\" encoding=\"utf-8\"?>\n<root>\n....etc, etc,";





// Create CURL Connection


 $ch = curl_init();


 curl_setopt($ch, CURLOPT_USERAGENT, 'XtraDoh xAgent');


 curl_setopt($ch, CURLOPT_URL, $sendTo);


 curl_setopt($ch, CURLOPT_TIMEOUT, 900);


 curl_setopt($ch, CURLOPT_CONNECTIONTIMEOUT, 30);


 curl_setopt($ch, CURLOPT_FAILONERROR, false);


 curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, 0);


 curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, 0);


 curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);


 curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);


 curl_setopt($ch, CURLOPT_HTTPHEADER, $header);


 curl_setopt($ch, CURLOPT_POST, true);


 curl_setopt($ch, CURLOPT_POSTFIELDS, $post);


?>





Notice the HTTPHEADER, $header above. I have not been able to get .NET to properly read the HTTP header as specified (in this case as text/xml) when using the following:





<?php


curl_setopt($ch, CURLOPT_HTTPHEADER, array('Content-Type'=>'text/xml'));


?>





Although this may work when working with other PHP, IIS, or even PHP, Apache, it does not (at least in my experience) work with .NET, IIS.

andrabr at gmail dot com
20-Aug-2007 07:03


This is very clear in hindsight, but it still cost me several hours:





<?php curl_setopt($session, CURLOPT_HTTPPROXYTUNNEL, 1); ?>





means that you will tunnel THROUGH the proxy, as in "your communications will go as if the proxy is NOT THERE".





Why do you care? - Well, if you are trying to use, say, Paros, to debug HTTP between your cURL and the server, with CURLOPT_HTTPPROXYTUNNEL set to TRUE Paros will not see or log your traffic thus defeating the purpose and driving you nuts.





There are other cases, of course, where this option is extremely useful...

michael sky
05-Jul-2007 08:09


if you are trying to connect to 'https://...' and after that want to work with POST data - that's the way:





<?php


$curl = curl_init();


curl_setopt($curl, CURLOPT_SSL_VERIFYPEER, FALSE);


curl_setopt($curl, CURLOPT_HEADER, 0);


curl_setopt($curl, CURLOPT_POST, true);


curl_setopt($curl, CURLOPT_RETURNTRANSFER, true);


curl_setopt($curl, CURLOPT_USERAGENT, "Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)");


curl_setopt($curl, CURLOPT_FOLLOWLOCATION, true);


curl_setopt($curl, CURLOPT_COOKIEFILE, "cookiefile");


curl_setopt($curl, CURLOPT_COOKIEJAR, "cookiefile"); # SAME cookiefile


curl_setopt($curl, CURLOPT_URL, "url1"); # this is where you first time connect - GET method authorization in my case, if you have POST - need to edit code a bit


$xxx = curl_exec($curl);





curl_setopt($curl, CURLOPT_URL, "url2"); # this is where you are requesting POST-method form results (working with secure connection using cookies after auth)


curl_setopt($curl, CURLOPT_POSTFIELDS, "var1=value&var2=value&var3=value&"); # form params that'll be used to get form results


$xxx = curl_exec($curl);





curl_close ($curl);


echo $xxx;


?>

sleepwalker at rahulsjohari dot com
27-Jun-2007 04:18


Two things that I noted, one of which has been mentioned earlier, if you are connecting to an SSL site (https) and don't have the appropriate certificate, don't forget to set CURLOPT_SSL_VERIFYPEER as "false"... it's set to "true" by default. Scratched my head over 2 hours to figure this one out as I had a machine with an older version installed and everything worked fine without using this option on that one - but failed on other machines with newer versions.





Second very important thing, I've never had my scripts work (tried on various machines, multiple platforms) with a Relative path to a COOKIEJAR or COOKIEFILE. In my experience I HAVE to specify the absolute path and not the relative path. 





Small script I wrote to connect to a page, gather all cookies into a jar, connect to another page to login, taking the cookiejar with you for authentication:





<?php


$ch = curl_init();


curl_setopt($ch, CURLOPT_COOKIEJAR, "/Library/WebServer/Documents/tmp/cookieFileName");


curl_setopt($ch, CURLOPT_URL,"https://www.example.com/myaccount/start.asp");


curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);


ob_start();      // Prevent output


curl_exec ($ch);


ob_end_clean();  // End preventing output


curl_close ($ch);


unset($ch);





$ch = curl_init();


curl_setopt($ch, CURLOPT_POST, 1);


curl_setopt($ch, CURLOPT_POSTFIELDS, "field1=".$f1."&field2=".$f2."&SomeFlag=True");


curl_setopt($ch, CURLOPT_RETURNTRANSFER,1);


curl_setopt($ch, CURLOPT_COOKIEFILE, "/Library/WebServer/Documents/tmp/cookieFileName");


curl_setopt($ch, CURLOPT_URL,"https://www.example.com/myaccount/Login.asp");


curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);


curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);


$result = curl_exec ($ch);


curl_close ($ch);


?>

mcbreen at gmail dot com
12-Jun-2007 07:35


If you are getting the following error:





SSL: certificate subject name 'example.com' does not match target host name 'example.net'





Then you can set the following option to get around it:





<?php curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, FALSE); ?>

vincent at ludden dot nl
12-Jun-2007 06:55


Please note that the CURLOPT_INTERFACE setting only accepts IP addresses and hostnames of the local machine. It is not meant to send a URL to a specific IP address.

ashw1 - at - no spam - post - dot - cz
03-Jun-2007 09:51


In case you wonder how come, that cookies don't work under Windows, I've googled for some answers, and here is the result: Under WIN you need to input absolute path of the cookie file.





This piece of code solves it:





<?php





if ($cookies != '')


    {


    if (substr(PHP_OS, 0, 3) == 'WIN')


        {$cookies = str_replace('\\','/', getcwd().'/'.$cookies);}


    curl_setopt($ch, CURLOPT_COOKIEJAR, $cookies);


    curl_setopt($ch, CURLOPT_COOKIEFILE, $cookies);


    }





?>

Jon Freilich
12-May-2007 02:52


curl will sometimes return an "Empty reply from server" error if you don't send a User-Agent string.  Use the CURLOPT_USERAGENT option.

rob at infoglobe dot net
24-Apr-2007 02:01


Options not included in the above, but that work (Taken from the libcurl.a C documentation)



CURLOPT_FTP_SSL 



Pass a long using one of the values from below, to make libcurl use your desired level of SSL for the ftp transfer. (Added in 7.11.0) 



CURLFTPSSL_NONE 



Don't attempt to use SSL. 



CURLFTPSSL_TRY 



Try using SSL, proceed as normal otherwise. 



CURLFTPSSL_CONTROL 



Require SSL for the control connection or fail with CURLE_FTP_SSL_FAILED. 



CURLFTPSSL_ALL 



Require SSL for all communication or fail with CURLE_FTP_SSL_FAILED.

alfredoaguirre dot v at gmail dot com
13-Mar-2007 10:26


Seems that CURLOPT_RETURNTRANSFER Option set to TRUE, returns a "1" when the transaction returns a blank page.



I think is for eliminate the FALSE to can be with a blank page as return

paczor
08-Mar-2007 12:50


How to get rid of response after POST: just add callback function for returned data (CURLOPT_WRITEFUNCTION) and make this function empty.





<?php


function curlHeaderCallback($ch, $strHeader) {


}


curl_setopt($ch, CURLOPT_WRITEFUNCTION, 'curlHeaderCallback');


?>

null at nahdah dot com
27-Nov-2006 07:42


I was having problems with Authorize.net and the SSL cert matching even after adding:





<?php


curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, 0);


?>





What I found after a lot of stumbling was I needed to set VERIFYHOST to FALSE.  So if you are still have a problem with Authorize.NET SSL and cURL add this:





<?php


curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, 0);


?>

pyroevi at yahoo dot com
22-Nov-2006 04:33


I was working on using php to interface with an authorize.net gateway, and I ran into a problem with certificates using curl to talk the https:// url.





curl_error() told me "SSL certificate problem, verify that the CA cert is OK."





I googled it and found the same "solution" over and over again: bypass verification by adding this line after curl_init():





<?php


curl_setopt($connection, CURLOPT_SSL_VERIFYPEER, false);


?>





This worked great, but I was required to verify, so here's what I did. Add the following lines:





<?php


curl_setopt($connection, CURLOPT_SSL_VERIFYPEER, 1);


curl_setopt($connection, CURLOPT_CAINFO, "path:/ca-bundle.crt");


?>





with "path:/ca-bundle.crt" being the path to that certificate file. You can get this file by downloading the curl package (http://curl.haxx.se/download.html) and looking for it in the lib folder.





Feel free to email me.

eion at bigfoot dot com
22-Nov-2006 02:40


If you are trying to use CURLOPT_FOLLOWLOCATION and you get this warning:

Warning: curl_setopt() [function.curl-setopt]: CURLOPT_FOLLOWLOCATION cannot be activated when in safe_mode or an open_basedir is set...



then you will want to read http://www.php.net/ChangeLog-4.php which says "Disabled CURLOPT_FOLLOWLOCATION in curl when open_basedir or safe_mode are enabled." as of PHP 4.4.4/5.1.5.  This is due to the fact that curl is not part of PHP and doesn't know the values of open_basedir or safe_mode, so you could comprimise your webserver operating in safe_mode by redirecting (using header('Location: ...')) to "file://" urls, which curl would have gladly retrieved.



Until the curl extension is changed in PHP or curl (if it ever will) to deal with "Location:" headers, here is a far from perfect remake of the curl_exec function that I am using.



Since there's no curl_getopt function equivalent, you'll have to tweak the function to make it work for your specific use.  As it is here, it returns the body of the response and not the header.  It also doesn't deal with redirection urls with username and passwords in them.



<?php

    function curl_redir_exec($ch)

    {

        static $curl_loops = 0;

        static $curl_max_loops = 20;

        if ($curl_loops++ >= $curl_max_loops)

        {

            $curl_loops = 0;

            return FALSE;

        }

        curl_setopt($ch, CURLOPT_HEADER, true);

        curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);

        $data = curl_exec($ch);

        list($header, $data) = explode("\n\n", $data, 2);

        $http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);

        if ($http_code == 301 || $http_code == 302)

        {

            $matches = array();

            preg_match('/Location:(.*?)\n/', $header, $matches);

            $url = @parse_url(trim(array_pop($matches)));

            if (!$url)

            {

                //couldn't process the url to redirect to

                $curl_loops = 0;

                return $data;

            }

            $last_url = parse_url(curl_getinfo($ch, CURLINFO_EFFECTIVE_URL));

            if (!$url['scheme'])

                $url['scheme'] = $last_url['scheme'];

            if (!$url['host'])

                $url['host'] = $last_url['host'];

            if (!$url['path'])

                $url['path'] = $last_url['path'];

            $new_url = $url['scheme'] . '://' . $url['host'] . $url['path'] . ($url['query']?'?'.$url['query']:'');

            curl_setopt($ch, CURLOPT_URL, $new_url);

            debug('Redirecting to', $new_url);

            return curl_redir_exec($ch);

        } else {

            $curl_loops=0;

            return $data;

        }

    }

?>

zarko at svetlozar dot net
01-Oct-2006 09:51


As Yevgen mentioned earlier sometimes we can't use CURLOPT_COOKIEJAR and CURLOPT_COOKIEFILE. Below is a header callback function I wrote back in January that lets you maintain cookies between cURL requests. Cookies are added to $ch during all requests even during redirection, so you can use it together with CURLOPT_FOLLOWLOCATION.


Here is the code:





<?php


function read_header($ch, $string)


{


    global $location; #keep track of location/redirects


    global $cookiearr; #store cookies here


    global $ch; 


       # ^overrides the function param $ch


       # this is okay because we need to 


       # update the global $ch with 


       # new cookies


    


    $length = strlen($string);


    if(!strncmp($string, "Location:", 9))


    { #keep track of last redirect


      $location = trim(substr($string, 9, -1));


    }


    if(!strncmp($string, "Set-Cookie:", 11))


    { #get the cookie


      $cookiestr = trim(substr($string, 11, -1));


      $cookie = explode(';', $cookiestr);


      $cookie = explode('=', $cookie[0]);


      $cookiename = trim(array_shift($cookie)); 


      $cookiearr[$cookiename] = trim(implode('=', $cookie));


    }


    $cookie = "";


    if(trim($string) == "") 


    {  #execute only at end of header


      foreach ($cookiearr as $key=>$value)


      {


        $cookie .= "$key=$value; ";


      }


      curl_setopt($ch, CURLOPT_COOKIE, $cookie);


    }





    return $length;


}


?>





Using the header function with curl (add this before curl_exec): 





<?php


#don't forget globals, especially if you are using this in function


curl_setopt($ch, CURLOPT_HEADERFUNCTION, 'read_header');


?>





This code assumes that you will reuse $ch without initializing it every time (call curl_init only once, in the beginning). If you need to initialize $ch again at any point in your code you can access the currently stored cookies in $cookiearr and include them in the new $ch.





I wrote this function before I had enough experience with regular expressions so you won't find any preg_match calls here. I have used this code for quite a while and without any problems accessing gmail, yahoo, hotmail, aol etc. where I had to go through login and a few pages before getting to what I was looking for. 





Svetlozar Petrov (http://svetlozar.net)

php at miggy dot org
23-Aug-2006 03:35


Note that if you want to use a proxy and use it as a _cache_, you'll have to do:





<?php curl_setopt($ch, CURLOPT_HTTPHEADER, array("Pragma: ")); ?>





else by default Curl puts a "Pragma: no-cache" header in and thus force cache misses for all requests.

Philippe dot Jausions at 11abacus dot com
30-May-2006 04:31


Clarification on the callback methods:



- CURLOPT_HEADERFUNCTION is for handling header lines received *in the response*,

- CURLOPT_WRITEFUNCTION is for handling data received *from the response*,

- CURLOPT_READFUNCTION is for handling data passed along *in the request*.



The callback "string" can be any callable function, that includes the array(&$obj, 'someMethodName') format.



 -Philippe

mr at coder dot tv
14-Apr-2006 12:22


Sometimes you can't use CURLOPT_COOKIEJAR and CURLOPT_COOKIEFILE becoz of the server php-settings(They say u may grab any files from server using these options). Here is the solution

1)Don't use CURLOPT_FOLLOWLOCATION

2)Use curl_setopt($ch, CURLOPT_HEADER, 1)

3)Grab from the header cookies like this:

preg_match_all('|Set-Cookie: (.*);|U', $content, $results);    

$cookies = implode(';', $results[1]);

4)Set them using curl_setopt($ch, CURLOPT_COOKIE,  $cookies);



Good Luck, Yevgen

heyrocker at yahoo dot com
23-Feb-2006 07:57


The examples below for HTTP file upload work great, but I wanted to be able to post multiple files through HTTP upload using HTML arrays as specified in example 38.3 at





http://us3.php.net/features.file-upload





In this case, you need to set the arrays AND keys in the $post_data, it will not work with just the array names. The following example shows how this works:





<?php





    $post_data = array();


    


    $post_data['pictures[0]'] = "@cat.jpg";


    $post_data['pictures[1]'] = "@dog.jpg";


    





    $ch = curl_init();


    curl_setopt($ch, CURLOPT_URL, "http://example.com/my_url.php" ); 


    curl_setopt($ch, CURLOPT_POST, 1 );


    curl_setopt($ch, CURLOPT_POSTFIELDS, $post_data);


    curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);


    $postResult = curl_exec($ch);





    if (curl_errno($ch)) {


       print curl_error($ch);


    }


    curl_close($ch);


    print "$postResult";


?>

petelu $ post dot sk
17-Feb-2006 10:19


load https:// or  http://example.com/exam.php  


with  POST  data (name=alex&year=18) and apply COOKIEs





<?php


$sessions = curl_init();


curl_setopt($sessions,CURLOPT_URL,'http://example.com/exam.php');


curl_setopt($sessions, CURLOPT_POST, 1);


curl_setopt($sessions,CURLOPT_POSTFIELDS,'name=alex&year=18');


curl_setopt($sessions,CURLOPT_COOKIEJAR,


dirname(__FILE__).'/cookie.txt');


curl_setopt($sessions,CURLOPT_FOLLOWLOCATION,0);


curl_setopt($sessions, CURLOPT_HEADER , 1);


curl_setopt($sessions, CURLOPT_RETURNTRANSFER,1);


$my_load_page = curl_exec($this->sessions);


?>

luca dot manzo at bbsitalia dot com
02-Feb-2006 09:55


If you're getting trouble with cookie handling in curl: 





- curl manages tranparently cookies in a single curl session


- the option 


<?php curl_setopt($ch, CURLOPT_COOKIEJAR, "/tmp/cookieFileName"); ?>





makes curl to store the cookies in a file at the and of the curl session





- the option 


<?php curl_setopt($ch, CURLOPT_COOKIEFILE, "/tmp/cookieFileName"); ?>





makes curl to use the given file as source for the cookies to send to the server. 





so to handle correctly cookies between different curl session, the you have to do something like this:





<?php


       $ch = curl_init(); 


       curl_setopt ($ch, CURLOPT_URL, $url); 


       curl_setopt ($ch, CURLOPT_COOKIEJAR, COOKIE_FILE_PATH);


       curl_setopt ($ch, CURLOPT_COOKIEFILE, COOKIE_FILE_PATH);





       curl_setopt ($ch, CURLOPT_RETURNTRANSFER, 1); 


       $result = curl_exec ($ch);


       curl_close($ch);


       return $result;


?>





in particular this is NECESSARY if you are using PEAR_SOAP libraries to build a webservice client over https and the remote server need to establish a session cookie. in fact each soap message is sent using a different curl session!!





I hope this can help someone


Luca

Dustin Hawkins
27-Dec-2005 08:24


To further expand upon use of CURLOPT_CAPATH and CURLOPT_CAINFO...



In my case I wanted to prevent curl from talking to any HTTPS server except my own using a self signed certificate. To do this, you'll need openssl installed and access to the HTTPS Server Certificate (server.crt by default on apache)



You can then use a command simiar to this to translate your apache certificate into one that curl likes.



$ openssl x509 -in server.crt -out outcert.pem -text



Then set CURLOPT_CAINFO equal to the the full path to outcert.pem and turn on CURLOPT_SSL_VERIFYPEER.



If you want to use the CURLOPT_CAPATH option, you should create a directory for all the valid certificates you have created, then use the c_rehash script that is included with openssl to "prepare" the directory.



If you dont use the c_rehash utility, curl will ignore any file in the directory you set.

skyogre __at__ yandex __dot__ ru
22-Dec-2005 08:13


There is really a problem of transmitting $_POST data with curl in php 4+ at least.

I improved the encoding function by Alejandro Moreno to work properly with mulltidimensional arrays.



<?php

function data_encode($data, $keyprefix = "", $keypostfix = "") {

  assert( is_array($data) );

  $vars=null;

  foreach($data as $key=>$value) {

    if(is_array($value)) $vars .= data_encode($value, $keyprefix.$key.$keypostfix.urlencode("["), urlencode("]"));

    else $vars .= $keyprefix.$key.$keypostfix."=".urlencode($value)."&";

  }

  return $vars;

}



curl_setopt($ch, CURLOPT_POSTFIELDS, substr(data_encode($_POST), 0, -1) );



?>

phpnet at wafflehouse dot de
23-Oct-2005 11:34


Resetting CURLOPT_FILE to STDOUT won't work by calling curl_setopt() with the STDOUT constant or a php://output stream handle (at least I get error messages when trying the code from phpnet at andywaite dot com). Instead, one can simply reset it as a side effect of CURLOPT_RETURNTRANSFER. Just say





<?php curl_setopt($this->curl,CURLOPT_RETURNTRANSFER,0); ?>





and following calls to curl_exec() will output to STDOUT again.

webmaster () stauceni.com
20-Oct-2005 06:42


A little mistake, that took a half-day to fix it:

When specifing CURLOPT_COOKIEFILE or CURLOPT_COOKIEJAR options, don't forget to "chmod 777" that directory where cookie-file must be created.

ROXORT at TGNOOB dot FR
21-Sep-2005 12:09


<?php


/*


  Here is a script that is usefull to :


  - login to a POST form,


  - store a session cookie,


  - download a file once logged in.


*/





// INIT CURL


$ch = curl_init();





// SET URL FOR THE POST FORM LOGIN


curl_setopt($ch, CURLOPT_URL, 'http://www.example.com/Members/Login.php');





// ENABLE HTTP POST


curl_setopt ($ch, CURLOPT_POST, 1);





// SET POST PARAMETERS : FORM VALUES FOR EACH FIELD


curl_setopt ($ch, CURLOPT_POSTFIELDS, 'fieldname1=fieldvalue1&fieldname2=fieldvalue2');





// IMITATE CLASSIC BROWSER'S BEHAVIOUR : HANDLE COOKIES


curl_setopt ($ch, CURLOPT_COOKIEJAR, 'cookie.txt');





# Setting CURLOPT_RETURNTRANSFER variable to 1 will force cURL


# not to print out the results of its query.


# Instead, it will return the results as a string return value


# from curl_exec() instead of the usual true/false.


curl_setopt ($ch, CURLOPT_RETURNTRANSFER, 1);





// EXECUTE 1st REQUEST (FORM LOGIN)


$store = curl_exec ($ch);





// SET FILE TO DOWNLOAD


curl_setopt($ch, CURLOPT_URL, 'http://www.example.com/Members/Downloads/AnnualReport.pdf');





// EXECUTE 2nd REQUEST (FILE DOWNLOAD)


$content = curl_exec ($ch);





// CLOSE CURL


curl_close ($ch); 





/*


  At this point you can do do whatever you want


  with the downloaded file stored in $content :


  display it, save it as file, and so on.


*/


?>

mcknight at chek dot com
23-Aug-2005 01:10


when specifing the file for either CURLOPT_COOKIEFILE or CURLOPT_COOKIEJAR you may need to use the full file path instead of just the relative path.

phpnet at andywaite dot com
07-Jun-2005 07:08


After setting CURLOPT_FILE, you may want want to revert back to the normal behaviour of displaying the results. This can be achieved using:





<?php


$fp = fopen ("php://output", "w") or die("Unable to open stdout for writing.\n");


curl_setopt($ch, CURLOPT_FILE, $fp);


?>

michaeledwards.com
01-Jun-2005 07:57


Problems can occur if you mix CURLOPT_URL with a 'Host:' header in CURLOPT_HEADERS on redirects because cURL will combine the host you explicitly stated in the 'Host:' header with the host from the Location: header of the redirect response. 





In short, don't do this:





<?php


$host = "www.example.com";


$url = "http://$host/";





$headers = array("Host: $host");





$ch = curl_init();





curl_setopt($ch, CURLOPT_URL, $url);


curl_setopt($ch, CURLOPT_HTTPHEADER, $headers);





Do this instead:





$host = "www.example.com";


$url = "http://$host/";





$ch = curl_init();





curl_setopt($ch, CURLOPT_URL, $url);


?>

samlowry at e-baka dot net
14-May-2005 11:09


About CURLOPT_ENCODING:


added in curl in 7.10 - Oct 1 2002


In 7.10.5 - May 19 2003 syntax was chnaged:


"setting CURLOPT_ENCODING to "" automaticly enables all supported encodings"

ikendra at yken dot nospam dot org
09-May-2005 02:26


Using cURL, I needed to call a third-party script which was returning binary data as attachment to pass on retrieved data again as attachment.





Problem was that the third-party script occassionally returned HTTP errors and I wanted to avoid passing on zero-length attachment in such case.





Combination of using CURLOPT_FAILONERROR and CURLOPT_HEADERFUNCTION callback helped to process the third-party script HTTP errors neatly:





<?php


function curlHeaderCallback($resURL, $strHeader) {


    if (preg_match('/^HTTP/i', $strHeader)) {


        header($strHeader);


        header('Content-Disposition: attachment; filename="file-name.zip"');


    }


    return strlen($strHeader);


}





$strURL = 'http://www.example.com/script-whichs-dumps-binary-attachment.php';





$resURL = curl_init();


curl_setopt($resURL, CURLOPT_URL, $strURL);


curl_setopt($resURL, CURLOPT_BINARYTRANSFER, 1);


curl_setopt($resURL, CURLOPT_HEADERFUNCTION, 'curlHeaderCallback');


curl_setopt($resURL, CURLOPT_FAILONERROR, 1);





curl_exec ($resURL);





$intReturnCode = curl_getinfo($resURL, CURLINFO_HTTP_CODE);


curl_close ($resURL);





if ($intReturnCode != 200) {


    print 'was error: ' . $intReturnCode;


}


?>

mcknight at chek dot com
21-Feb-2005 03:38


Another way to automate a login process and store multiple cookies for additional transfers.





(The easiest way is probably just to use CURLOPT_COOKIEJAR and CURLOPT_COOKIEFILE and save them to a file. But if you need to change those cookie values or add/delete them then you can use the code below to set them.)





Continuing with Paul Ebermann's parsing function.





<?php


 function parse_response($this_response)


    {


    // Split response into header and body sections


    list($response_headers, $response_body) = explode("\r\n\r\n", $this_response, 2);


    $response_header_lines = explode("\r\n", $response_headers);





    // First line of headers is the HTTP response code


    $http_response_line = array_shift($response_header_lines);


    if(preg_match('@^HTTP/[0-9]\.[0-9] ([0-9]{3})@',$http_response_line, $matches)) { $response_code = $matches[1]; }





    // put the rest of the headers in an array


    $response_header_array = array();


    foreach($response_header_lines as $header_line)


        {


        list($header,$value) = explode(': ', $header_line, 2);


        $response_header_array[$header] .= $value."\n";


        }





    return array("code" => $response_code, "header" => $response_header_array, "body" => $response_body); 


    }





// Do transfer, and make sure to include header in response


$ch = curl_init();


curl_setopt($ch, CURLOPT_URL, "[login process]");


curl_setopt($ch, CURLOPT_HEADER, 1);


curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);


$response = curl_exec($ch);


curl_close($ch);





// Parse the response message


$response = parse_response($response);





// Create the basic header


$this_header = array(


    "MIME-Version: 1.0",


    "Content-type: text/html; charset=iso-8859-1",


    "Content-transfer-encoding: text"


);





// Add each cookie that has been returned in the response


// If cookies need to be added/deleted or value changed, then add code here


$cookies = explode("\n", $response["header"]["Set-Cookie"]);


foreach($cookies as $this_cookie) { array_push($this_header, "Cookie: ".$this_cookie); }





// Next set of transfers


$ch = curl_init();


curl_setopt($ch, CURLOPT_URL, "[new transfer]");


curl_setopt($ch, CURLOPT_HTTPHEADER, $this_header);


curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);


$response = curl_exec($ch);


curl_close($ch);


?>

Aaron Stephanic
11-Nov-2004 03:51


The parse_response code below does not return multiple cookies as the value of 'Set-Cookie' if multiple cookies are set by the server.  It appears to only return the last cookie set.

raul at navenetworks dot com
21-Jul-2004 06:19


Hi!



I have found some information I am sure it could help lot of programmers when they want to connect with curl to any https website and they haven't a good or right CA Cert :)



I give you just one example It has resolved me 2 hours of my time looking for a solution.



It is simple, just if you get any error in the curl_exec (use curl_error(...) to see the error to trace it) add the next line and everything is solved:



(note: replace $ch with the right curl variable)



curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, FALSE);



<?php



$ch = curl_init();

$res= curl_setopt ($ch, CURLOPT_URL,"https://yoururl/cgi");



curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, FALSE);

curl_setopt ($ch, CURLOPT_HEADER, 0);

curl_setopt($ch, CURLOPT_POST, 1);

curl_setopt($ch, CURLOPT_POSTFIELDS, "Idc=si&");

curl_setopt ($ch, CURLOPT_RETURNTRANSFER, 1);

$xyz = curl_exec ($ch);



curl_close ($ch);

echo $xyz;

if ($xyz == NULL) { 

           echo "Error:<br>";

           echo curl_errno($ch) . " - " . curl_error($ch) . "<br>";

}

?>



I hope this helps.



Raul Mate Galan

Ceo Navenetworks Corp.



Note: Thanks to Ruben Lopez Gea for his help too.

ron at ttvavanti dot nl
07-May-2004 01:00


If you specify a CAINFO, note that the file must be in PEM format! (If not, it won't work).

Using Openssl you can use: 

openssl x509 -in <cert> -inform d -outform PEM -out cert.pem 

To create a pem formatted certificate from a binary certificate (the one you get if you download the ca somewhere).

brett at brettbrewer dot com
29-Apr-2004 12:48


I found it very annoying that cURL did not offer any easy way to extract the response headers. If you do 





  <?php curl_setopt($ch, CURLOPT_HEADER, 1); ?>





then you only get the headers output inline with the rest of your response. Here's a nice little function to parse the cURL response when you use CURLOPT_HEADER.  I took it from an example on another site and turned it into a function. It assumes you're using CURLOPT_RETURNTRANSFER to return the response to some variable that is then passed to the function. You just pass it a curl_exec result and it returns the result parsed into an array with headers broken up into their correct parts.





<?php


function parse_response($response){


    /*


    ***original code extracted from examples at 


    ***http://www.webreference.com/programming/php/cookbook/chap11/1/3.html





    ***returns an array in the following format which varies depending on headers returned





        [0] => the HTTP error or response code such as 404


        [1] => Array


        (


            [Server] => Microsoft-IIS/5.0


            [Date] => Wed, 28 Apr 2004 23:29:20 GMT


            [X-Powered-By] => ASP.NET


            [Connection] => close


            [Set-Cookie] => COOKIESTUFF


            [Expires] => Thu, 01 Dec 1994 16:00:00 GMT


            [Content-Type] => text/html


            [Content-Length] => 4040


        )


        [2] => Response body (string)


*/





    list($response_headers,$response_body) = explode("\r\n\r\n",$response,2);


    $response_header_lines = explode("\r\n",$response_headers);





    // first line of headers is the HTTP response code


    $http_response_line = array_shift($response_header_lines);


    if (preg_match('@^HTTP/[0-9]\.[0-9] ([0-9]{3})@',$http_response_line,


                   $matches)) {


        $response_code = $matches[1];


    }





    // put the rest of the headers in an array 


    $response_header_array = array();


    foreach ($response_header_lines as $header_line) {


        list($header,$value) = explode(': ',$header_line,2);


        $response_header_array[$header] = $value;


    }





    return array($response_code,$response_header_array,$response_body);


}


?>

Jakub Horky <jakub dot php at horky dot net>
04-Apr-2004 06:20


A bit more documentation (without minimum version numbers):



- CURLOPT_WRITEFUNCTION

- CURLOPT_HEADERFUNCTION

  Pass a function which will be called to write data or headers respectively. The callback function prototype:



long write_callback (resource ch, string data)



The ch argument is CURL session handle. The data argument is data received. Note that its size is variable. When writing data, as much data as possible will be returned in all invokes. When writing headers, exactly one complete header line is returned for better parsing.

The function must return number of bytes actually taken care of. If that amount differs from the amount passed to this function, an error will occur.



- CURLOPT_READFUNCTION

  Pass a function which will be called to read data. The callback function prototype:



string read_callback (resource ch, resource fd, long length)



The ch argument is CURL session handle. The fd argument is file descriptor passed to CURL by CURLOPT_INFILE option. The length argument is maximum length which can be returned.

The function must return string containing the data which were read. If length of the data is more than maximum length, it will be truncated to maximum length. Returning anything else than a string means an EOF.



[Note: there is more callbacks implemented in current cURL library but they aren't unfortunately implemented in php curl interface yet.]

tim dot php at ebw dot ca
19-Nov-2003 12:18


The page http://curl.haxx.se/libcurl/c/curl_easy_setopt.html at the cURL site has a list of all the CURLOPTS, including many not mentioned here. Also see http://curl.haxx.se/libcurl/php/examples/ for cURL examples in PHP.

eric at imap dot ch
07-Jul-2003 02:38


I managed to use curl to retrieve information from severs on ports other than 80 or 443 (for https) on some installations but not on all. 


If you get an "CURLE_COULDNT_CONNECT /* 7 */" error, try adding the port : (for example)





<?php curl_setopt($ch, CURLOPT_PORT, $_SERVER['SERVER_PORT']); ?>

me
14-May-2003 02:36


Just a reminder: When setting your CURLOPT_POSTFIELDS remember to replace the spaces in your values with %20

dweingart at pobox dot com
02-Apr-2003 09:08


If you want to Curl to follow redirects and you would also like Curl to echo back any cookies that are set in the process, use this:





<?php curl_setopt($ch, CURLOPT_COOKIEJAR, '-'); ?>





'-' means stdout





-dw

yann dot corno at free dot fr
13-Nov-2002 10:19


About the CURLOPT_HTTPHEADER option, it took me some time to figure out how to format the so-called 'Array'. It fact, it is a list of strings. If Curl was already defining a header item, yours will replace it. Here is an example to change the Content Type in a POST:





<?php curl_setopt ($ch, CURLOPT_HTTPHEADER, Array("Content-Type: text/xml")); ?>





Yann

23-Oct-2002 05:04


beware that not all cURLlib constants are supported under php :


e.g. CURLOPT_PROGRESSFUNCTION or CURLOPT_WRITEDATA are not supported.





CURLOPT_WRITEFUNCTION, although undocumented is supported. It takes the name of a user_defined function.


the function should take two arguments (the curl handle, and the inputdata) and return the length of the written data


e.g.





<?php


function myPoorProgressFunc($ch,$str){


global $fd;


$len = fwrite($fd,$str);


print("#");


return $len;


}





curl_setopt($ch,CURLOPT_WRITEFUNCTION,"myPoorProgressFunc");


?>





Also be aware that CURLOPT_WRITEFUNCTION  does NOT take the CURLOPT_FILE as a parameter! 


in curl lib it would take CURLOPT_WRITEDATA but this is not supported by php; that's why I use "global $fd;" in my exemple function.





CURLOPT_HEADERFUNCTION works the same, and is guaranteed to receive complete header lines as input! 





Hope this helps





Ivan

mrcheezy at hotmail dot com
13-Sep-2002 07:34


If you set return transfer to 1 and are sending a post form and find that this crashes php try setting follow location to 1 also. I'm not exactly sure why this crashed, but after i used follow it stopped.





<?php


  curl_setopt ($sess, CURLOPT_FOLLOWLOCATION, '1');


  curl_setopt ($sess, CURLOPT_RETURNTRANSFER, '1');


?>

paul at zgtec dot com
26-Aug-2002 07:31


To make a POST in multipart/form-data mode 


this worked for me, the " \n" at the end of the variables was very important on my OS X server.





<?php





$file = "file_to_upload.txt";


$submit_url = "http://www.example.com/upload_page.php";





$formvars = array("cc"=>"us \n");


$formvars[variable_1] = "bla bla \n";


$formvars[variable_2] = "bla bla \n";


$formvars[variable_3] = "bla bla \n";


$formvars[variable_4] = "bla bla \n";


$formvars[upfile] = "@$file"; // "@" causes cURL to send as file and not string (I believe) 





    // init curl handle


    $ch = curl_init($submit_url);


    curl_setopt($ch, CURLOPT_COOKIEJAR, "my_cookies.txt");  //initiates cookie file if needed


    curl_setopt($ch, CURLOPT_COOKIEFILE, "my_cookies.txt");  // Uses cookies from previous session if exist


    curl_setopt($ch, CURLOPT_REFERER, "http://www.example.net");  //if server needs to think this post came from elsewhere


    curl_setopt($ch, CURLOPT_VERBOSE, 1);


    curl_setopt($ch, CURLOPT_HEADER, 1);


    curl_setopt($ch, CURLOPT_FOLLOWLOCATION,1); // follow redirects recursively


    curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);


    curl_setopt($ch, CURLOPT_POSTFIELDS, $formvars);





    // perform post


    echo $pnp_result_page = curl_exec($ch);


    curl_close ($ch);





?>

tychay at alumni dot caltech dot edu
03-Apr-2002 07:14


CURLOPT_HTTPHEADER is NOT like the -H command line switch. The command line switch adds or replaces headers (much like the header() line in PHP, but for HTTP clients instead of servers), but the curl extension will eliminate the headers cURL sends by default.



For instance, your Authorization, Host, Referer, Pragma, and Accept headers which are normally written by default or by other CURLOPT_*'s.



Also, it might seem intuitive that this should accept an array hash of header->values, but this is not the case. It accepts an array of strings of the format "Header: Value", much like the -H command-line switch.



Hope this helps,



terry

asmith at crawlspace dot com
01-Mar-2002 01:18


It's possible to take advantage of multiple URLs on the same host in one curl_exec transaction ... just use multiple instances of CURLOPT_URL.





Example:





<?php


$ch = curl_init();


curl_setopt($ch, CURLOPT_URL, "http://example.com/a.html");


curl_setopt($ch, CURLOPT_URL, "http://example.com/b.html");


curl_setopt($ch, CURLOPT_URL, "http://example.com/c.html");


curl_exec($ch);


curl_close($ch);


?>





... the URLs appear to be hit in the same order they are entered. This takes advantage of cURL's Persistant Connection capability if all the URLs are on the same host!

bvwj at swbell dot net
18-Dec-2001 07:35


To collect cookies recieved with a request, set CURLOPT_COOKIEJAR "cookieFileName".  Then use CURLOPT_COOKIEFILE "cookieFileName" to recall them in subsequent transactions.

22-Sep-2001 02:52


To make a POST in multipart/form-data mode





(to upload a file for example) you can use 





<?php curl_setopt($ch,CURLOPT_POSTFIELDS,$post); ?>





where $post is an array :





<?php


$post['key1'] = 'data1';


//  like a text field in a POST


$post['file1'] = '@filename1' 


// upload filename1


?>





For more informations see the 





curl_formparse man page.

sr2899.at.hotmail.com
14-May-2001 07:00


CURLOPT_RETURNTRANSFER has the interesting behaviour of tacking a null char onto the end of the string.  This null char is actually on the end of the php string, and can cause some odd results if you're not expecting it to be there.

fil at rezox dot com
21-Feb-2001 11:50


If you want to connect to a secure server for posting info/reading info, you need to make cURL with the openSSL options. Then the sequence is nearly identical to the previous example (except http_S_://, and possibly add the useragent):





<?php


curl_setopt($ch, CURLOPT_URL,"https://example.com");


//some sites only accept your request if your browser looks legit, so send a useragent profile... 


curl_setopt ($ch, CURLOPT_USERAGENT, "Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)");


?>

bvr at xs4all dot nl
07-Feb-2001 01:09


If you'd like to include extra headers in your POST request, you can accomplish this by setting the following option:





CURLOPT_HTTPHEADER





This is similar to the CURL -H command line switch.





Thanks to Daniel Stenberg for pointing out this usefull feature!





Note: this option was first supported in PHP version 4.03 .

awestholm at imail dot usi dot net
25-Jan-2001 05:33


Just because the docs are rather sparse on this, to set multiple values in a cookie, you separate them with a semicolon, as usual. An example, yo set j to j and k to k:





<?php curl_setopt($ch,CURLOPT_COOKIE,"j=j;k=k"); ?>





    -- Alex

dan dot polansky at seznam dot cz
17-Jan-2001 08:31


I used to download www pages to my script and one of the pages was different in MS explorer and different, when I downloaded it. Namely, information, I was really interested in was missing. That was because the server on the other bank of the river was looking at who is downloading the page. Everything got fixed when I pretended I was MSIE. It is done with curl. Here is a function, that you may use in similar situation





<?php


function download_pretending($url,$user_agent) {


   $ch = curl_init();


   curl_setopt ($ch, CURLOPT_URL, $url);


   curl_setopt ($ch, CURLOPT_USERAGENT, $user_agent);


   curl_setopt ($ch, CURLOPT_HEADER, 0);


   curl_setopt ($ch, CURLOPT_RETURNTRANSFER, 1);


   $result = curl_exec ($ch); 


   curl_close ($ch);


   return $result;


}


?>

add a note

curl_version

curl_setopt_array

Last updated: Fri, 13 Nov 2009