]
>>
startxref
4727
%%EOF
curl-7.35.0/docs/libcurl/curl_easy_setopt.html 0000644 0001750 0001750 00000574573 12272124467 016366 0000000 0000000
curl_easy_setopt man page
NAME
curl_easy_setopt - set options for a curl easy handle
SYNOPSIS
#include <curl/curl.h>
CURLcode curl_easy_setopt(CURL *handle, CURLoption option, parameter);
DESCRIPTION
curl_easy_setopt() is used to tell libcurl how to behave. By using the appropriate options to curl_easy_setopt, you can change libcurl's behavior. All options are set with the option followed by a parameter. That parameter can be a long, a function pointer, an object pointer or a curl_off_t, depending on what the specific option expects. Read this manual carefully as bad input values may cause libcurl to behave badly! You can only set one option in each function call. A typical application uses many curl_easy_setopt() calls in the setup phase.
Options set with this function call are valid for all forthcoming transfers performed using this handle. The options are not in any way reset between transfers, so if you want subsequent transfers with different options, you must change them between the transfers. You can optionally reset all options back to internal default with curl_easy_reset(3).
Strings passed to libcurl as 'char *' arguments, are copied by the library; thus the string storage associated to the pointer argument may be overwritten after curl_easy_setopt() returns. Exceptions to this rule are described in the option details below.
Before version 7.17.0, strings were not copied. Instead the user was forced keep them available until libcurl no longer needed them.
The handle is the return code from a curl_easy_init(3) or curl_easy_duphandle(3) call.
BEHAVIOR OPTIONS
CURLOPT_VERBOSE
Set the parameter to 1 to get the library to display a lot of verbose information about its operations. Very useful for libcurl and/or protocol debugging and understanding. The verbose information will be sent to stderr, or the stream set with CURLOPT_STDERR. The default value for this parameter is 0.
You hardly ever want this set in production use, you will almost always want this when you debug/report problems. Another neat option for debugging is the CURLOPT_DEBUGFUNCTION.
CURLOPT_HEADER
A parameter set to 1 tells the library to include the header in the body output. This is only relevant for protocols that actually have headers preceding the data (like HTTP). The default value for this parameter is 0.
CURLOPT_NOPROGRESS
Pass a long. If set to 1, it tells the library to shut off the progress meter completely. It will also prevent the CURLOPT_PROGRESSFUNCTION from getting called. The default value for this parameter is 1.
Future versions of libcurl are likely to not have any built-in progress meter at all.
CURLOPT_NOSIGNAL
Pass a long. If it is 1, libcurl will not use any functions that install signal handlers or any functions that cause signals to be sent to the process. This option is mainly here to allow multi-threaded unix applications to still set/use all timeout options etc, without risking getting signals. The default value for this parameter is 0. (Added in 7.10)
If this option is set and libcurl has been built with the standard name resolver, timeouts will not occur while the name resolve takes place. Consider building libcurl with c-ares support to enable asynchronous DNS lookups, which enables nice timeouts for name resolves without signals.
Setting CURLOPT_NOSIGNAL to 1 makes libcurl NOT ask the system to ignore SIGPIPE signals, which otherwise are sent by the system when trying to send data to a socket which is closed in the other end. libcurl makes an effort to never cause such SIGPIPEs to trigger, but some operating systems have no way to avoid them and even on those that have there are some corner cases when they may still happen, contrary to our desire. In addition, using CURLAUTH_NTLM_WB authentication could cause a SIGCHLD signal to be raised.
CURLOPT_WILDCARDMATCH
Set this option to 1 if you want to transfer multiple files according to a file name pattern. The pattern can be specified as part of the CURLOPT_URL option, using an fnmatch-like pattern (Shell Pattern Matching) in the last part of URL (file name).
By default, libcurl uses its internal wildcard matching implementation. You can provide your own matching function by the CURLOPT_FNMATCH_FUNCTION option.
This feature is only supported by the FTP download for now.
A brief introduction of its syntax follows:
* - ASTERISK
ftp://example.com/some/path/*.txt (for all txt's from the root directory)
? - QUESTION MARK
Question mark matches any (exactly one) character.
ftp://example.com/some/path/photo?.jpeg
[ - BRACKET EXPRESSION
The left bracket opens a bracket expression. The question mark and asterisk have no special meaning in a bracket expression. Each bracket expression ends by the right bracket and matches exactly one character. Some examples follow:
[a-zA-Z0-9] or [f-gF-G] - character interval
[abc] - character enumeration
[^abc] or [!abc] - negation
[[:name:]] class expression. Supported classes are alnum,lower, space, alpha, digit, print, upper, blank, graph, xdigit.
[][-!^] - special case - matches only '-', ']', '[', '!' or '^'. These characters have no special purpose.
[\[\]\\] - escape syntax. Matches '[', ']' or '´.
Using the rules above, a file name pattern can be constructed:
ftp://example.com/some/path/[a-z[:upper:]\\].jpeg
(This was added in 7.21.0)
CALLBACK OPTIONS
CURLOPT_WRITEFUNCTION
Pass a pointer to a function that matches the following prototype: size_t function( char *ptr, size_t size, size_t nmemb, void *userdata); This function gets called by libcurl as soon as there is data received that needs to be saved. The size of the data pointed to by ptr is size multiplied with nmemb, it will not be zero terminated. Return the number of bytes actually taken care of. If that amount differs from the amount passed to your function, it'll signal an error to the library. This will abort the transfer and return CURLE_WRITE_ERROR.
From 7.18.0, the function can return CURL_WRITEFUNC_PAUSE which then will cause writing to this connection to become paused. See curl_easy_pause(3) for further details.
This function may be called with zero bytes data if the transferred file is empty.
Set this option to NULL to get the internal default function. The internal default function will write the data to the FILE * given with CURLOPT_WRITEDATA.
Set the userdata argument with the CURLOPT_WRITEDATA option.
The callback function will be passed as much data as possible in all invokes, but you cannot possibly make any assumptions. It may be one byte, it may be thousands. The maximum amount of body data that can be passed to the write callback is defined in the curl.h header file: CURL_MAX_WRITE_SIZE (the usual default is 16K). If you however have CURLOPT_HEADER set, which sends header data to the write callback, you can get up to CURL_MAX_HTTP_HEADER bytes of header data passed into it. This usually means 100K.
CURLOPT_WRITEDATA
Data pointer to pass to the file write function. If you use the CURLOPT_WRITEFUNCTION option, this is the pointer you'll get as input. If you don't use a callback, you must pass a 'FILE *' (cast to 'void *') as libcurl will pass this to fwrite() when writing data. By default, the value of this parameter is unspecified.
The internal CURLOPT_WRITEFUNCTION will write the data to the FILE * given with this option, or to stdout if this option hasn't been set.
If you're using libcurl as a win32 DLL, you MUST use the CURLOPT_WRITEFUNCTION if you set this option or you will experience crashes.
This option is also known with the older name CURLOPT_FILE, the name CURLOPT_WRITEDATA was introduced in 7.9.7.
CURLOPT_READFUNCTION
Pass a pointer to a function that matches the following prototype: size_t function( void *ptr, size_t size, size_t nmemb, void *userdata); This function gets called by libcurl as soon as it needs to read data in order to send it to the peer. The data area pointed at by the pointer ptr may be filled with at most size multiplied with nmemb number of bytes. Your function must return the actual number of bytes that you stored in that memory area. Returning 0 will signal end-of-file to the library and cause it to stop the current transfer.
If you stop the current transfer by returning 0 "pre-maturely" (i.e before the server expected it, like when you've said you will upload N bytes and you upload less than N bytes), you may experience that the server "hangs" waiting for the rest of the data that won't come.
The read callback may return CURL_READFUNC_ABORT to stop the current operation immediately, resulting in a CURLE_ABORTED_BY_CALLBACK error code from the transfer (Added in 7.12.1)
From 7.18.0, the function can return CURL_READFUNC_PAUSE which then will cause reading from this connection to become paused. See curl_easy_pause(3) for further details.
Bugs: when doing TFTP uploads, you must return the exact amount of data that the callback wants, or it will be considered the final packet by the server end and the transfer will end there.
If you set this callback pointer to NULL, or don't set it at all, the default internal read function will be used. It is doing an fread() on the FILE * userdata set with CURLOPT_READDATA.
CURLOPT_READDATA
Data pointer to pass to the file read function. If you use the CURLOPT_READFUNCTION option, this is the pointer you'll get as input. If you don't specify a read callback but instead rely on the default internal read function, this data must be a valid readable FILE * (cast to 'void *').
If you're using libcurl as a win32 DLL, you MUST use a CURLOPT_READFUNCTION if you set this option.
This option was also known by the older name CURLOPT_INFILE, the name CURLOPT_READDATA was introduced in 7.9.7.
CURLOPT_IOCTLFUNCTION
Pass a pointer to a function that matches the following prototype: curlioerr function(CURL *handle, int cmd, void *clientp);. This function gets called by libcurl when something special I/O-related needs to be done that the library can't do by itself. For now, rewinding the read data stream is the only action it can request. The rewinding of the read data stream may be necessary when doing a HTTP PUT or POST with a multi-pass authentication method. By default, this parameter is set to NULL. (Option added in 7.12.3).
Use CURLOPT_SEEKFUNCTION instead to provide seeking! If CURLOPT_SEEKFUNCTION is set, this parameter will be ignored when seeking.
CURLOPT_IOCTLDATA
Pass a pointer that will be untouched by libcurl and passed as the 3rd argument in the ioctl callback set with CURLOPT_IOCTLFUNCTION. By default, the value of this parameter is unspecified. (Option added in 7.12.3)
CURLOPT_SEEKFUNCTION
Pass a pointer to a function that matches the following prototype: int function(void *instream, curl_off_t offset, int origin); This function gets called by libcurl to seek to a certain position in the input stream and can be used to fast forward a file in a resumed upload (instead of reading all uploaded bytes with the normal read function/callback). It is also called to rewind a stream when doing a HTTP PUT or POST with a multi-pass authentication method. The function shall work like "fseek" or "lseek" and accepted SEEK_SET, SEEK_CUR and SEEK_END as argument for origin, although libcurl currently only passes SEEK_SET. The callback must return 0 (CURL_SEEKFUNC_OK) on success, 1 (CURL_SEEKFUNC_FAIL) to cause the upload operation to fail or 2 (CURL_SEEKFUNC_CANTSEEK) to indicate that while the seek failed, libcurl is free to work around the problem if possible. The latter can sometimes be done by instead reading from the input or similar.
By default, this parameter is unset.
If you forward the input arguments directly to "fseek" or "lseek", note that the data type for offset is not the same as defined for curl_off_t on many systems! (Option added in 7.18.0)
CURLOPT_SEEKDATA
Data pointer to pass to the file seek function. If you use the CURLOPT_SEEKFUNCTION option, this is the pointer you'll get as input. If you don't specify a seek callback, NULL is passed. (Option added in 7.18.0)
CURLOPT_SOCKOPTFUNCTION
Pass a pointer to a function that matches the following prototype: int function(void *clientp, curl_socket_t curlfd, curlsocktype purpose);. By default, this parameter is unset. If set, this function gets called by libcurl after the socket() call but before the connect() call. The callback's purpose argument identifies the exact purpose for this particular socket:
CURLSOCKTYPE_IPCXN for actively created connections or since 7.28.0 CURLSOCKTYPE_ACCEPT for FTP when the connection was setup with PORT/EPSV (in earlier versions these sockets weren't passed to this callback).
Future versions of libcurl may support more purposes. It passes the newly created socket descriptor so additional setsockopt() calls can be done at the user's discretion. Return 0 (zero) from the callback on success. Return 1 from the callback function to signal an unrecoverable error to the library and it will close the socket and return CURLE_COULDNT_CONNECT. (Option added in 7.16.0)
Added in 7.21.5, the callback function may return CURL_SOCKOPT_ALREADY_CONNECTED, which tells libcurl that the socket is in fact already connected and then libcurl will not attempt to connect it.
CURLOPT_SOCKOPTDATA
Pass a pointer that will be untouched by libcurl and passed as the first argument in the sockopt callback set with CURLOPT_SOCKOPTFUNCTION. The default value of this parameter is unspecified. (Option added in 7.16.0)
CURLOPT_OPENSOCKETFUNCTION
Pass a pointer to a function that matches the following prototype: curl_socket_t function(void *clientp, curlsocktype purpose, struct curl_sockaddr *address);. This function gets called by libcurl instead of the socket(2) call. The callback's purpose argument identifies the exact purpose for this particular socket: CURLSOCKTYPE_IPCXN is for IP based connections. Future versions of libcurl may support more purposes. It passes the resolved peer address as a address argument so the callback can modify the address or refuse to connect at all. The callback function should return the socket or CURL_SOCKET_BAD in case no connection could be established or another error was detected. Any additional setsockopt(2) calls can be done on the socket at the user's discretion. CURL_SOCKET_BAD return value from the callback function will signal an unrecoverable error to the library and it will return CURLE_COULDNT_CONNECT. This return code can be used for IP address blacklisting. The default behavior is:
return socket(addr->family, addr->socktype, addr->protocol);
(Option added in 7.17.1.)
CURLOPT_OPENSOCKETDATA
Pass a pointer that will be untouched by libcurl and passed as the first argument in the opensocket callback set with CURLOPT_OPENSOCKETFUNCTION. The default value of this parameter is unspecified. (Option added in 7.17.1.)
CURLOPT_CLOSESOCKETFUNCTION
Pass a pointer to a function that matches the following prototype: int function(void *clientp, curl_socket_t item);. This function gets called by libcurl instead of the close(3) or closesocket(3) call when sockets are closed (not for any other file descriptors). This is pretty much the reverse to the CURLOPT_OPENSOCKETFUNCTION option. Return 0 to signal success and 1 if there was an error. (Option added in 7.21.7)
CURLOPT_CLOSESOCKETDATA
Pass a pointer that will be untouched by libcurl and passed as the first argument in the closesocket callback set with CURLOPT_CLOSESOCKETFUNCTION. The default value of this parameter is unspecified. (Option added in 7.21.7)
CURLOPT_PROGRESSFUNCTION
Pass a pointer to a function that matches the following prototype:
int function(void *clientp, double dltotal, double dlnow, double ultotal, double ulnow);
This function gets called by libcurl instead of its internal equivalent with a frequent interval. While data is being transferred it will be called very frequently, and during slow periods like when nothing is being transferred it can slow down to about one call per second.
clientp is the pointer set with CURLOPT_PROGRESSDATA, it is not actually used by libcurl but is only passed along from the application to the callback.
The callback gets told how much data libcurl will transfer and has transferred, in number of bytes. dltotal is the total number of bytes libcurl expects to download in this transfer. dlnow is the number of bytes downloaded so far. ultotal is the total number of bytes libcurl expects to upload in this transfer. ulnow is the number of bytes uploaded so far.
Unknown/unused argument values passed to the callback will be set to zero (like if you only download data, the upload size will remain 0). Many times the callback will be called one or more times first, before it knows the data sizes so a program must be made to handle that.
Returning a non-zero value from this callback will cause libcurl to abort the transfer and return CURLE_ABORTED_BY_CALLBACK.
If you transfer data with the multi interface, this function will not be called during periods of idleness unless you call the appropriate libcurl function that performs transfers.
CURLOPT_NOPROGRESS must be set to 0 to make this function actually get called.
CURLOPT_XFERINFOFUNCTION
Pass a pointer to a function that matches the following prototype:
int function(void *clientp, curl_off_t dltotal, curl_off_t dlnow,
curl_off_t ultotal, curl_off_t ulnow);
This function gets called by libcurl instead of its internal equivalent with a frequent interval. While data is being transferred it will be called very frequently, and during slow periods like when nothing is being transferred it can slow down to about one call per second.
clientp is the pointer set with CURLOPT_XFERINFODATA, it is only passed along from the application to the callback.
The callback gets told how much data libcurl will transfer and has transferred, in number of bytes. dltotal is the total number of bytes libcurl expects to download in this transfer. dlnow is the number of bytes downloaded so far. ultotal is the total number of bytes libcurl expects to upload in this transfer. ulnow is the number of bytes uploaded so far.
Unknown/unused argument values passed to the callback will be set to zero (like if you only download data, the upload size will remain 0). Many times the callback will be called one or more times first, before it knows the data sizes so a program must be made to handle that.
Returning a non-zero value from this callback will cause libcurl to abort the transfer and return CURLE_ABORTED_BY_CALLBACK.
If you transfer data with the multi interface, this function will not be called during periods of idleness unless you call the appropriate libcurl function that performs transfers.
CURLOPT_NOPROGRESS must be set to 0 to make this function actually get called.
(Added in 7.32.0)
CURLOPT_PROGRESSDATA
Pass a pointer that will be untouched by libcurl and passed as the first argument in the progress callback set with CURLOPT_PROGRESSFUNCTION. The default value of this parameter is unspecified.
CURLOPT_XFERINFODATA
Pass a pointer that will be untouched by libcurl and passed as the first argument in the progress callback set with CURLOPT_XFERINFOFUNCTION. The default value of this parameter is unspecified. This option is an alias for CURLOPT_PROGRESSDATA. (Added in 7.32.0)
CURLOPT_HEADERFUNCTION
Pass a pointer to a function that matches the following prototype: size_t function( void *ptr, size_t size, size_t nmemb, void *userdata);. This function gets called by libcurl as soon as it has received header data. The header callback will be called once for each header and only complete header lines are passed on to the callback. Parsing headers is very easy using this. The size of the data pointed to by ptr is size multiplied with nmemb. Do not assume that the header line is zero terminated! The pointer named userdata is the one you set with the CURLOPT_WRITEHEADER option. The callback function must return the number of bytes actually taken care of. If that amount differs from the amount passed to your function, it'll signal an error to the library. This will abort the transfer and return CURL_WRITE_ERROR.
A complete HTTP header that is passed to this function can be up to CURL_MAX_HTTP_HEADER (100K) bytes.
If this option is not set, or if it is set to NULL, but CURLOPT_HEADERDATA (CURLOPT_WRITEHEADER) is set to anything but NULL, the function used to accept response data will be used instead. That is, it will be the function specified with CURLOPT_WRITEFUNCTION, or if it is not specified or NULL - the default, stream-writing function.
It's important to note that the callback will be invoked for the headers of all responses received after initiating a request and not just the final response. This includes all responses which occur during authentication negotiation. If you need to operate on only the headers from the final response, you will need to collect headers in the callback yourself and use HTTP status lines, for example, to delimit response boundaries.
When a server sends a chunked encoded transfer, it may contain a trailer. That trailer is identical to a HTTP header and if such a trailer is received it is passed to the application using this callback as well. There are several ways to detect it being a trailer and not an ordinary header: 1) it comes after the response-body. 2) it comes after the final header line (CR LF) 3) a Trailer: header among the regular response-headers mention what header(s) to expect in the trailer.
For non-HTTP protocols like FTP, POP3, IMAP and SMTP this function will get called with the server responses to the commands that libcurl sends.
CURLOPT_WRITEHEADER
(This option is also known as CURLOPT_HEADERDATA) Pass a pointer to be used to write the header part of the received data to. If you don't use CURLOPT_WRITEFUNCTION or CURLOPT_HEADERFUNCTION to take care of the writing, this must be a valid FILE * as the internal default will then be a plain fwrite(). See also the CURLOPT_HEADERFUNCTION option above on how to set a custom get-all-headers callback.
CURLOPT_DEBUGFUNCTION
Pass a pointer to a function that matches the following prototype: int curl_debug_callback (CURL *, curl_infotype, char *, size_t, void *); CURLOPT_DEBUGFUNCTION replaces the standard debug function used when CURLOPT_VERBOSE is in effect. This callback receives debug information, as specified with the curl_infotype argument. This function must return 0. The data pointed to by the char * passed to this function WILL NOT be zero terminated, but will be exactly of the size as told by the size_t argument.
Available curl_infotype values:
CURLINFO_TEXT
The data is informational text.
CURLINFO_HEADER_IN
The data is header (or header-like) data received from the peer.
CURLINFO_HEADER_OUT
The data is header (or header-like) data sent to the peer.
CURLINFO_DATA_IN
The data is protocol data received from the peer.
CURLINFO_DATA_OUT
The data is protocol data sent to the peer.
CURLOPT_DEBUGDATA
Pass a pointer to whatever you want passed in to your CURLOPT_DEBUGFUNCTION in the last void * argument. This pointer is not used by libcurl, it is only passed to the callback.
CURLOPT_SSL_CTX_FUNCTION
This option does only function for libcurl powered by OpenSSL. If libcurl was built against another SSL library, this functionality is absent.
Pass a pointer to a function that matches the following prototype: CURLcode sslctxfun(CURL *curl, void *sslctx, void *parm); This function gets called by libcurl just before the initialization of a SSL connection after having processed all other SSL related options to give a last chance to an application to modify the behaviour of openssl's ssl initialization. The sslctx parameter is actually a pointer to an openssl SSL_CTX. If an error is returned no attempt to establish a connection is made and the perform operation will return the error code from this callback function. Set the parm argument with the CURLOPT_SSL_CTX_DATA option. This option was introduced in 7.11.0.
This function will get called on all new connections made to a server, during the SSL negotiation. The SSL_CTX pointer will be a new one every time.
To use this properly, a non-trivial amount of knowledge of the openssl libraries is necessary. For example, using this function allows you to use openssl callbacks to add additional validation code for certificates, and even to change the actual URI of a HTTPS request (example used in the lib509 test case). See also the example section for a replacement of the key, certificate and trust file settings.
CURLOPT_SSL_CTX_DATA
Data pointer to pass to the ssl context callback set by the option CURLOPT_SSL_CTX_FUNCTION, this is the pointer you'll get as third parameter, otherwise NULL. (Added in 7.11.0)
CURLOPT_CONV_TO_NETWORK_FUNCTION
CURLOPT_CONV_FROM_NETWORK_FUNCTION
CURLOPT_CONV_FROM_UTF8_FUNCTION
Pass a pointer to a function that matches the following prototype: CURLcode function(char *ptr, size_t length);
These three options apply to non-ASCII platforms only. They are available only if CURL_DOES_CONVERSIONS was defined when libcurl was built. When this is the case, curl_version_info(3) will return the CURL_VERSION_CONV feature bit set.
The data to be converted is in a buffer pointed to by the ptr parameter. The amount of data to convert is indicated by the length parameter. The converted data overlays the input data in the buffer pointed to by the ptr parameter. CURLE_OK should be returned upon successful conversion. A CURLcode return value defined by curl.h, such as CURLE_CONV_FAILED, should be returned if an error was encountered.
CURLOPT_CONV_TO_NETWORK_FUNCTION and CURLOPT_CONV_FROM_NETWORK_FUNCTION convert between the host encoding and the network encoding. They are used when commands or ASCII data are sent/received over the network.
CURLOPT_CONV_FROM_UTF8_FUNCTION is called to convert from UTF8 into the host encoding. It is required only for SSL processing.
If you set a callback pointer to NULL, or don't set it at all, the built-in libcurl iconv functions will be used. If HAVE_ICONV was not defined when libcurl was built, and no callback has been established, conversion will return the CURLE_CONV_REQD error code.
If HAVE_ICONV is defined, CURL_ICONV_CODESET_OF_HOST must also be defined. For example:
#define CURL_ICONV_CODESET_OF_HOST "IBM-1047"
The iconv code in libcurl will default the network and UTF8 codeset names as follows:
#define CURL_ICONV_CODESET_OF_NETWORK "ISO8859-1"
#define CURL_ICONV_CODESET_FOR_UTF8 "UTF-8"
You will need to override these definitions if they are different on your system.
CURLOPT_INTERLEAVEFUNCTION
Pass a pointer to a function that matches the following prototype: size_t function( void *ptr, size_t size, size_t nmemb, void *userdata). This function gets called by libcurl as soon as it has received interleaved RTP data. This function gets called for each $ block and therefore contains exactly one upper-layer protocol unit (e.g. one RTP packet). Curl writes the interleaved header as well as the included data for each call. The first byte is always an ASCII dollar sign. The dollar sign is followed by a one byte channel identifier and then a 2 byte integer length in network byte order. See RFC 2326 Section 10.12 for more information on how RTP interleaving behaves. If unset or set to NULL, curl will use the default write function.
Interleaved RTP poses some challenges for the client application. Since the stream data is sharing the RTSP control connection, it is critical to service the RTP in a timely fashion. If the RTP data is not handled quickly, subsequent response processing may become unreasonably delayed and the connection may close. The application may use CURL_RTSPREQ_RECEIVE to service RTP data when no requests are desired. If the application makes a request, (e.g. CURL_RTSPREQ_PAUSE) then the response handler will process any pending RTP data before marking the request as finished. (Added in 7.20.0)
CURLOPT_INTERLEAVEDATA
This is the userdata pointer that will be passed to CURLOPT_INTERLEAVEFUNCTION when interleaved RTP data is received. (Added in 7.20.0)
CURLOPT_CHUNK_BGN_FUNCTION
Pass a pointer to a function that matches the following prototype: long function (const void *transfer_info, void *ptr, int remains). This function gets called by libcurl before a part of the stream is going to be transferred (if the transfer supports chunks).
This callback makes sense only when using the CURLOPT_WILDCARDMATCH option for now.
The target of transfer_info parameter is a "feature depended" structure. For the FTP wildcard download, the target is curl_fileinfo structure (see curl/curl.h). The parameter ptr is a pointer given by CURLOPT_CHUNK_DATA. The parameter remains contains number of chunks remaining per the transfer. If the feature is not available, the parameter has zero value.
Return CURL_CHUNK_BGN_FUNC_OK if everything is fine, CURL_CHUNK_BGN_FUNC_SKIP if you want to skip the concrete chunk or CURL_CHUNK_BGN_FUNC_FAIL to tell libcurl to stop if some error occurred. (This was added in 7.21.0)
CURLOPT_CHUNK_END_FUNCTION
Pass a pointer to a function that matches the following prototype: long function(void *ptr). This function gets called by libcurl as soon as a part of the stream has been transferred (or skipped).
Return CURL_CHUNK_END_FUNC_OK if everything is fine or CURL_CHUNK_END_FUNC_FAIL to tell the lib to stop if some error occurred. (This was added in 7.21.0)
CURLOPT_CHUNK_DATA
Pass a pointer that will be untouched by libcurl and passed as the ptr argument to the CURL_CHUNK_BGN_FUNTION and CURL_CHUNK_END_FUNTION. (This was added in 7.21.0)
CURLOPT_FNMATCH_FUNCTION
Pass a pointer to a function that matches the following prototype: int function(void *ptr, const char *pattern, const char *string) prototype (see curl/curl.h). It is used internally for the wildcard matching feature.
Return CURL_FNMATCHFUNC_MATCH if pattern matches the string, CURL_FNMATCHFUNC_NOMATCH if not or CURL_FNMATCHFUNC_FAIL if an error occurred. (This was added in 7.21.0)
CURLOPT_FNMATCH_DATA
Pass a pointer that will be untouched by libcurl and passed as the ptr argument to the CURL_FNMATCH_FUNCTION. (This was added in 7.21.0)
ERROR OPTIONS
CURLOPT_ERRORBUFFER
Pass a char * to a buffer that the libcurl may store human readable error messages in. This may be more helpful than just the return code from curl_easy_perform. The buffer must be at least CURL_ERROR_SIZE big. Although this argument is a 'char *', it does not describe an input string. Therefore the (probably undefined) contents of the buffer is NOT copied by the library. You must keep the associated storage available until libcurl no longer needs it. Failing to do so will cause very odd behavior or even crashes. libcurl will need it until you call curl_easy_cleanup(3) or you set the same option again to use a different pointer.
Use CURLOPT_VERBOSE and CURLOPT_DEBUGFUNCTION to better debug/trace why errors happen.
If the library does not return an error, the buffer may not have been touched. Do not rely on the contents in those cases.
CURLOPT_STDERR
Pass a FILE * as parameter. Tell libcurl to use this stream instead of stderr when showing the progress meter and displaying CURLOPT_VERBOSE data.
CURLOPT_FAILONERROR
A parameter set to 1 tells the library to fail silently if the HTTP code returned is equal to or larger than 400. The default action would be to return the page normally, ignoring that code.
This method is not fail-safe and there are occasions where non-successful response codes will slip through, especially when authentication is involved (response codes 401 and 407).
You might get some amounts of headers transferred before this situation is detected, like when a "100-continue" is received as a response to a POST/PUT and a 401 or 407 is received immediately afterwards.
NETWORK OPTIONS
CURLOPT_URL
Pass in a pointer to the actual URL to deal with. The parameter should be a char * to a zero terminated string which must be URL-encoded in the following format:
scheme://host:port/path
For a greater explanation of the format please see RFC 3986.
If the given URL lacks the scheme (such as "http://" or "ftp://" etc) then libcurl will attempt to resolve the protocol based on one of the following given host names:
HTTP, FTP, DICT, LDAP, IMAP, POP3 or SMTP
(POP3 and SMTP added in 7.31.0)
Should the protocol, either that specified by the scheme or deduced by libcurl from the host name, not be supported by libcurl then (CURLE_UNSUPPORTED_PROTOCOL) will be returned from either the curl_easy_perform(3) or curl_multi_perform(3) functions when you call them. Use curl_version_info(3) for detailed information of which protocols are supported by the build of libcurl you are using.
The host part of the URL contains the address of the server that you want to connect to. This can be the fully qualified domain name of the server, the local network name of the machine on your network or the IP address of the server or machine represented by either an IPv4 or IPv6 address. For example:
http://www.example.com/
http://hostname/
http://192.168.0.1/
http://[2001:1890:1112:1::20]/
It is also possible to specify the user name, password and any supported login options as part of the host, for the following protocols, when connecting to servers that require authentication:
http://user:password@www.example.com
ftp://user:password@ftp.example.com
imap://user:password;options@mail.example.com
pop3://user:password;options@mail.example.com
smtp://user:password;options@mail.example.com
At present only IMAP, POP3 and SMTP support login options as part of the host. For more information about the login options in URL syntax please see RFC 2384, RFC 5092 and IETF draft draft-earhart-url-smtp-00.txt (Added in 7.31.0).
The port is optional and when not specified libcurl will use the default port based on the determined or specified protocol: 80 for HTTP, 21 for FTP and 25 for SMTP, etc. The following examples show how to specify the port:
http://www.example.com:8080/ - This will connect to a web server using port 8080 rather than 80.
smtp://mail.example.com:587/ - This will connect to a SMTP server on the alternative mail port.
The path part of the URL is protocol specific and whilst some examples are given below this list is not conclusive:
HTTP
The path part of a HTTP request specifies the file to retrieve and from what directory. If the directory is not specified then the web server's root directory is used. If the file is omitted then the default document will be retrieved for either the directory specified or the root directory. The exact resource returned for each URL is entirely dependent on the server's configuration.
http://www.example.com - This gets the main page from the web server.
http://www.example.com/index.html - This returns the main page by explicitly requesting it.
http://www.example.com/contactus/ - This returns the default document from the contactus directory.
FTP
The path part of an FTP request specifies the file to retrieve and from what directory. If the file part is omitted then libcurl downloads the directory listing for the directory specified. If the directory is omitted then the directory listing for the root / home directory will be returned.
ftp://ftp.example.com - This retrieves the directory listing for the root directory.
ftp://ftp.example.com/readme.txt - This downloads the file readme.txt from the root directory.
ftp://ftp.example.com/libcurl/readme.txt - This downloads readme.txt from the libcurl directory.
ftp://user:password@ftp.example.com/readme.txt - This retrieves the readme.txt file from the user's home directory. When a username and password is specified, everything that is specified in the path part is relative to the user's home directory. To retrieve files from the root directory or a directory underneath the root directory then the absolute path must be specified by prepending an additional forward slash to the beginning of the path.
ftp://user:password@ftp.example.com//readme.txt - This retrieves the readme.txt from the root directory when logging in as a specified user.
SMTP
The path part of a SMTP request specifies the host name to present during communication with the mail server. If the path is omitted then libcurl will attempt to resolve the local computer's host name. However, this may not return the fully qualified domain name that is required by some mail servers and specifying this path allows you to set an alternative name, such as your machine's fully qualified domain name, which you might have obtained from an external function such as gethostname or getaddrinfo.
smtp://mail.example.com - This connects to the mail server at example.com and sends your local computer's host name in the HELO / EHLO command.
smtp://mail.example.com/client.example.com - This will send client.example.com in the HELO / EHLO command to the mail server at example.com.
POP3
The path part of a POP3 request specifies the message ID to retrieve. If the ID is not specified then a list of waiting messages is returned instead.
pop3://user:password@mail.example.com - This lists the available messages for the user
pop3://user:password@mail.example.com/1 - This retrieves the first message for the user
IMAP
The path part of an IMAP request not only specifies the mailbox to list (Added in 7.30.0) or select, but can also be used to check the UIDVALIDITY of the mailbox and to specify the UID and SECTION of the message to fetch (Added in 7.30.0).
imap://user:password@mail.example.com - Performs a top level folder list
imap://user:password@mail.example.com/INBOX - Performs a folder list on the user's inbox
imap://user:password@mail.example.com/INBOX/;UID=1 - Selects the user's inbox and fetches message 1
imap://user:password@mail.example.com/INBOX;UIDVALIDITY=50/;UID=2 - Selects the user's inbox, checks the UIDVALIDITY of the mailbox is 50 and fetches message 2 if it is
imap://user:password@mail.example.com/INBOX/;UID=3/;SECTION=TEXT - Selects the user's inbox and fetches message 3 with only the text portion of the message
For more information about the individual components of an IMAP URL please see RFC 5092.
SCP
The path part of a SCP request specifies the file to retrieve and from what directory. The file part may not be omitted. The file is taken as an absolute path from the root directory on the server. To specify a path relative to the user's home directory on the server, prepend ~/ to the path portion. If the user name is not embedded in the URL, it can be set with the CURLOPT_USERPWD or CURLOPT_USERNAME option.
scp://user@example.com/etc/issue - This specifies the file /etc/issue
scp://example.com/~/my-file - This specifies the file my-file in the user's home directory on the server
SFTP
The path part of a SFTP request specifies the file to retrieve and from what directory. If the file part is omitted then libcurl downloads the directory listing for the directory specified. If the path ends in a / then a directory listing is returned instead of a file. If the path is omitted entirely then the directory listing for the root / home directory will be returned. If the user name is not embedded in the URL, it can be set with the CURLOPT_USERPWD or CURLOPT_USERNAME option.
sftp://user:password@example.com/etc/issue - This specifies the file /etc/issue
sftp://user@example.com/~/my-file - This specifies the file my-file in the user's home directory
sftp://ssh.example.com/~/Documents/ - This requests a directory listing of the Documents directory under the user's home directory
LDAP
The path part of a LDAP request can be used to specify the: Distinguished Name, Attributes, Scope, Filter and Extension for a LDAP search. Each field is separated by a question mark and when that field is not required an empty string with the question mark separator should be included.
ldap://ldap.example.com/o=My%20Organisation - This will perform a LDAP search with the DN as My Organisation.
ldap://ldap.example.com/o=My%20Organisation?postalAddress - This will perform the same search but will only return postalAddress attributes.
ldap://ldap.example.com/?rootDomainNamingContext - This specifies an empty DN and requests information about the rootDomainNamingContext attribute for an Active Directory server.
For more information about the individual components of a LDAP URL please see RFC 4516.
RTMP
There's no official URL spec for RTMP so libcurl uses the URL syntax supported by the underlying librtmp library. It has a syntax where it wants a traditional URL, followed by a space and a series of space-separated name=value pairs.
While space is not typically a "legal" letter, libcurl accepts them. When a user wants to pass in a '#' (hash) character it will be treated as a fragment and get cut off by libcurl if provided literally. You will instead have to escape it by providing it as backslash and its ASCII value in hexadecimal: "\23".
NOTES
Starting with version 7.20.0, the fragment part of the URI will not be sent as part of the path, which was previously the case.
CURLOPT_URL is the only option that must be set before curl_easy_perform(3) is called.
CURLOPT_PROTOCOLS can be used to limit what protocols libcurl will use for this transfer, independent of what libcurl has been compiled to support. That may be useful if you accept the URL from an external source and want to limit the accessibility.
CURLOPT_PROTOCOLS
Pass a long that holds a bitmask of CURLPROTO_* defines. If used, this bitmask limits what protocols libcurl may use in the transfer. This allows you to have a libcurl built to support a wide range of protocols but still limit specific transfers to only be allowed to use a subset of them. By default libcurl will accept all protocols it supports. See also CURLOPT_REDIR_PROTOCOLS. (Added in 7.19.4)
CURLOPT_REDIR_PROTOCOLS
Pass a long that holds a bitmask of CURLPROTO_* defines. If used, this bitmask limits what protocols libcurl may use in a transfer that it follows to in a redirect when CURLOPT_FOLLOWLOCATION is enabled. This allows you to limit specific transfers to only be allowed to use a subset of protocols in redirections. By default libcurl will allow all protocols except for FILE and SCP. This is a difference compared to pre-7.19.4 versions which unconditionally would follow to all protocols supported. (Added in 7.19.4)
CURLOPT_PROXY
Set HTTP proxy to use. The parameter should be a char * to a zero terminated string holding the host name or dotted IP address. To specify port number in this string, append :[port] to the end of the host name. The proxy string may be prefixed with [protocol]:// since any such prefix will be ignored. The proxy's port number may optionally be specified with the separate option. If not specified, libcurl will default to using port 1080 for proxies. CURLOPT_PROXYPORT.
When you tell the library to use a HTTP proxy, libcurl will transparently convert operations to HTTP even if you specify an FTP URL etc. This may have an impact on what other features of the library you can use, such as CURLOPT_QUOTE and similar FTP specifics that don't work unless you tunnel through the HTTP proxy. Such tunneling is activated with CURLOPT_HTTPPROXYTUNNEL.
libcurl respects the environment variables http_proxy, ftp_proxy, all_proxy etc, if any of those are set. The CURLOPT_PROXY option does however override any possibly set environment variables.
Setting the proxy string to "" (an empty string) will explicitly disable the use of a proxy, even if there is an environment variable set for it.
Since 7.14.1, the proxy host string given in environment variables can be specified the exact same way as the proxy can be set with CURLOPT_PROXY, include protocol prefix (http://) and embedded user + password.
Since 7.21.7, the proxy string may be specified with a protocol:// prefix to specify alternative proxy protocols. Use socks4://, socks4a://, socks5:// or socks5h:// (the last one to enable socks5 and asking the proxy to do the resolving, also known as CURLPROXY_SOCKS5_HOSTNAME type) to request the specific SOCKS version to be used. No protocol specified, http:// and all others will be treated as HTTP proxies.
CURLOPT_PROXYPORT
Pass a long with this option to set the proxy port to connect to unless it is specified in the proxy string CURLOPT_PROXY.
CURLOPT_PROXYTYPE
Pass a long with this option to set type of the proxy. Available options for this are CURLPROXY_HTTP, CURLPROXY_HTTP_1_0 (added in 7.19.4), CURLPROXY_SOCKS4 (added in 7.10), CURLPROXY_SOCKS5, CURLPROXY_SOCKS4A (added in 7.18.0) and CURLPROXY_SOCKS5_HOSTNAME (added in 7.18.0). The HTTP type is default. (Added in 7.10)
If you set CURLOPT_PROXYTYPE to CURLPROXY_HTTP_1_0, it will only affect how libcurl speaks to a proxy when CONNECT is used. The HTTP version used for "regular" HTTP requests is instead controlled with CURLOPT_HTTP_VERSION.
CURLOPT_NOPROXY
Pass a pointer to a zero terminated string. The string consists of a comma separated list of host names that do not require a proxy to get reached, even if one is specified. The only wildcard available is a single * character, which matches all hosts, and effectively disables the proxy. Each name in this list is matched as either a domain which contains the hostname, or the hostname itself. For example, example.com would match example.com, example.com:80, and www.example.com, but not www.notanexample.com. (Added in 7.19.4)
CURLOPT_HTTPPROXYTUNNEL
Set the parameter to 1 to make the library tunnel all operations through a given HTTP proxy. There is a big difference between using a proxy and to tunnel through it. If you don't know what this means, you probably don't want this tunneling option.
CURLOPT_SOCKS5_GSSAPI_SERVICE
Pass a char * as parameter to a string holding the name of the service. The default service name for a SOCKS5 server is rcmd/server-fqdn. This option allows you to change it. (Added in 7.19.4)
CURLOPT_SOCKS5_GSSAPI_NEC
Pass a long set to 1 to enable or 0 to disable. As part of the gssapi negotiation a protection mode is negotiated. The RFC 1961 says in section 4.3/4.4 it should be protected, but the NEC reference implementation does not. If enabled, this option allows the unprotected exchange of the protection mode negotiation. (Added in 7.19.4).
CURLOPT_INTERFACE
Pass a char * as parameter. This sets the interface name to use as outgoing network interface. The name can be an interface name, an IP address, or a host name.
Starting with 7.24.0: If the parameter starts with "if!" then it is treated as only as interface name and no attempt will ever be named to do treat it as an IP address or to do name resolution on it. If the parameter starts with "host!" it is treated as either an IP address or a hostname. Hostnames are resolved synchronously. Using the if! format is highly recommended when using the multi interfaces to avoid allowing the code to block. If "if!" is specified but the parameter does not match an existing interface, CURLE_INTERFACE_FAILED is returned.
CURLOPT_LOCALPORT
Pass a long. This sets the local port number of the socket used for connection. This can be used in combination with CURLOPT_INTERFACE and you are recommended to use CURLOPT_LOCALPORTRANGE as well when this is set. Valid port numbers are 1 - 65535. (Added in 7.15.2)
CURLOPT_LOCALPORTRANGE
Pass a long. This is the number of attempts libcurl will make to find a working local port number. It starts with the given CURLOPT_LOCALPORT and adds one to the number for each retry. Setting this to 1 or below will make libcurl do only one try for the exact port number. Port numbers by nature are scarce resources that will be busy at times so setting this value to something too low might cause unnecessary connection setup failures. (Added in 7.15.2)
CURLOPT_DNS_CACHE_TIMEOUT
Pass a long, this sets the timeout in seconds. Name resolves will be kept in memory for this number of seconds. Set to zero to completely disable caching, or set to -1 to make the cached entries remain forever. By default, libcurl caches this info for 60 seconds.
The name resolve functions of various libc implementations don't re-read name server information unless explicitly told so (for example, by calling res_init(3)). This may cause libcurl to keep using the older server even if DHCP has updated the server info, and this may look like a DNS cache issue to the casual libcurl-app user.
CURLOPT_DNS_USE_GLOBAL_CACHE
Pass a long. If the value is 1, it tells curl to use a global DNS cache that will survive between easy handle creations and deletions. This is not thread-safe and this will use a global variable.
WARNING: this option is considered obsolete. Stop using it. Switch over to using the share interface instead! See CURLOPT_SHARE and curl_share_init(3).
CURLOPT_BUFFERSIZE
Pass a long specifying your preferred size (in bytes) for the receive buffer in libcurl. The main point of this would be that the write callback gets called more often and with smaller chunks. This is just treated as a request, not an order. You cannot be guaranteed to actually get the given size. (Added in 7.10)
This size is by default set as big as possible (CURL_MAX_WRITE_SIZE), so it only makes sense to use this option if you want it smaller.
CURLOPT_PORT
Pass a long specifying what remote port number to connect to, instead of the one specified in the URL or the default port for the used protocol.
CURLOPT_TCP_NODELAY
Pass a long specifying whether the TCP_NODELAY option is to be set or cleared (1 = set, 0 = clear). The option is cleared by default. This will have no effect after the connection has been established.
Setting this option will disable TCP's Nagle algorithm. The purpose of this algorithm is to try to minimize the number of small packets on the network (where "small packets" means TCP segments less than the Maximum Segment Size (MSS) for the network).
Maximizing the amount of data sent per TCP segment is good because it amortizes the overhead of the send. However, in some cases (most notably telnet or rlogin) small segments may need to be sent without delay. This is less efficient than sending larger amounts of data at a time, and can contribute to congestion on the network if overdone.
CURLOPT_ADDRESS_SCOPE
Pass a long specifying the scope_id value to use when connecting to IPv6 link-local or site-local addresses. (Added in 7.19.0)
CURLOPT_TCP_KEEPALIVE
Pass a long. If set to 1, TCP keepalive probes will be sent. The delay and frequency of these probes can be controlled by the CURLOPT_TCP_KEEPIDLE and CURLOPT_TCP_KEEPINTVL options, provided the operating system supports them. Set to 0 (default behavior) to disable keepalive probes (Added in 7.25.0).
CURLOPT_TCP_KEEPIDLE
Pass a long. Sets the delay, in seconds, that the operating system will wait while the connection is idle before sending keepalive probes. Not all operating systems support this option. (Added in 7.25.0)
CURLOPT_TCP_KEEPINTVL
Pass a long. Sets the interval, in seconds, that the operating system will wait between sending keepalive probes. Not all operating systems support this option. (Added in 7.25.0)
NAMES and PASSWORDS OPTIONS (Authentication)
CURLOPT_NETRC
This parameter controls the preference of libcurl between using user names and passwords from your ~/.netrc file, relative to user names and passwords in the URL supplied with CURLOPT_URL.
libcurl uses a user name (and supplied or prompted password) supplied with CURLOPT_USERPWD in preference to any of the options controlled by this parameter.
Pass a long, set to one of the values described below.
CURL_NETRC_OPTIONAL
The use of your ~/.netrc file is optional, and information in the URL is to be preferred. The file will be scanned for the host and user name (to find the password only) or for the host only, to find the first user name and password after that machine, which ever information is not specified in the URL.
Undefined values of the option will have this effect.
CURL_NETRC_IGNORED
The library will ignore the file and use only the information in the URL.
This is the default.
CURL_NETRC_REQUIRED
This value tells the library that use of the file is required, to ignore the information in the URL, and to search the file for the host only.
Only machine name, user name and password are taken into account (init macros and similar things aren't supported).
libcurl does not verify that the file has the correct properties set (as the standard Unix ftp client does). It should only be readable by user.
CURLOPT_NETRC_FILE
Pass a char * as parameter, pointing to a zero terminated string containing the full path name to the file you want libcurl to use as .netrc file. If this option is omitted, and CURLOPT_NETRC is set, libcurl will attempt to find a .netrc file in the current user's home directory. (Added in 7.10.9)
CURLOPT_USERPWD
Pass a char * as parameter, pointing to a zero terminated login details string for the connection. The format of which is: [user name]:[password].
When using NTLM, you can set the domain by prepending it to the user name and separating the domain and name with a forward (/) or backward slash (\). Like this: "domain/user:password" or "domain\user:password". Some HTTP servers (on Windows) support this style even for Basic authentication.
When using HTTP and CURLOPT_FOLLOWLOCATION, libcurl might perform several requests to possibly different hosts. libcurl will only send this user and password information to hosts using the initial host name (unless CURLOPT_UNRESTRICTED_AUTH is set), so if libcurl follows locations to other hosts it will not send the user and password to those. This is enforced to prevent accidental information leakage.
Use CURLOPT_HTTPAUTH to specify the authentication method for HTTP based connections or CURLOPT_LOGIN_OPTIONS to control IMAP, POP3 and SMTP options.
The user and password strings are not URL decoded, so there's no way to send in a user name containing a colon using this option. Use CURLOPT_USERNAME for that, or include it in the URL.
CURLOPT_PROXYUSERPWD
Pass a char * as parameter, which should be [user name]:[password] to use for the connection to the HTTP proxy. Both the name and the password will be URL decoded before use, so to include for example a colon in the user name you should encode it as %3A.
Use CURLOPT_PROXYAUTH to specify the authentication method.
CURLOPT_USERNAME
Pass a char * as parameter, which should be pointing to the zero terminated user name to use for the transfer.
CURLOPT_USERNAME sets the user name to be used in protocol authentication. You should not use this option together with the (older) CURLOPT_USERPWD option.
To specify the password and login options, along with the user name, use the CURLOPT_PASSWORD and CURLOPT_LOGIN_OPTIONS options. (Added in 7.19.1)
CURLOPT_PASSWORD
Pass a char * as parameter, which should be pointing to the zero terminated password to use for the transfer.
The CURLOPT_PASSWORD option should be used in conjunction with the CURLOPT_USERNAME option. (Added in 7.19.1)
CURLOPT_LOGIN_OPTIONS
(Added in 7.34.0) Pass a char * as parameter, which should be pointing to the zero terminated options string to use for the transfer.
At present only IMAP, POP3 and SMTP support login options. For more information about the login options please see RFC 2384, RFC5092 and IETF draft draft-earhart-url-smtp-00.txt
CURLOPT_LOGIN_OPTIONS can be used to set protocol specific login options, such as the preferred authentication mechanism via "AUTH=NTLM" or "AUTH=*", and should be used in conjunction with the CURLOPT_USERNAME option.
CURLOPT_PROXYUSERNAME
Pass a char * as parameter, which should be pointing to the zero terminated user name to use for the transfer while connecting to Proxy.
The CURLOPT_PROXYUSERNAME option should be used in same way as the CURLOPT_PROXYUSERPWD is used. In comparison to CURLOPT_PROXYUSERPWD the CURLOPT_PROXYUSERNAME allows the username to contain a colon, like in the following example: "sip:user@example.com". The CURLOPT_PROXYUSERNAME option is an alternative way to set the user name while connecting to Proxy. There is no meaning to use it together with the CURLOPT_PROXYUSERPWD option.
In order to specify the password to be used in conjunction with the user name use the CURLOPT_PROXYPASSWORD option. (Added in 7.19.1)
CURLOPT_PROXYPASSWORD
Pass a char * as parameter, which should be pointing to the zero terminated password to use for the transfer while connecting to Proxy.
The CURLOPT_PROXYPASSWORD option should be used in conjunction with the CURLOPT_PROXYUSERNAME option. (Added in 7.19.1)
CURLOPT_HTTPAUTH
Pass a long as parameter, which is set to a bitmask, to tell libcurl which authentication method(s) you want it to use. The available bits are listed below. If more than one bit is set, libcurl will first query the site to see which authentication methods it supports and then pick the best one you allow it to use. For some methods, this will induce an extra network round-trip. Set the actual name and password with the CURLOPT_USERPWD option or with the CURLOPT_USERNAME and the CURLOPT_PASSWORD options. (Added in 7.10.6)
CURLAUTH_BASIC
HTTP Basic authentication. This is the default choice, and the only method that is in wide-spread use and supported virtually everywhere. This sends the user name and password over the network in plain text, easily captured by others.
CURLAUTH_DIGEST
HTTP Digest authentication. Digest authentication is defined in RFC 2617 and is a more secure way to do authentication over public networks than the regular old-fashioned Basic method.
CURLAUTH_DIGEST_IE
HTTP Digest authentication with an IE flavor. Digest authentication is defined in RFC 2617 and is a more secure way to do authentication over public networks than the regular old-fashioned Basic method. The IE flavor is simply that libcurl will use a special "quirk" that IE is known to have used before version 7 and that some servers require the client to use. (This define was added in 7.19.3)
CURLAUTH_GSSNEGOTIATE
HTTP GSS-Negotiate authentication. The GSS-Negotiate (also known as plain "Negotiate") method was designed by Microsoft and is used in their web applications. It is primarily meant as a support for Kerberos5 authentication but may also be used along with other authentication methods. For more information see IETF draft draft-brezak-spnego-http-04.txt.
You need to build libcurl with a suitable GSS-API library for this to work.
CURLAUTH_NTLM
HTTP NTLM authentication. A proprietary protocol invented and used by Microsoft. It uses a challenge-response and hash concept similar to Digest, to prevent the password from being eavesdropped.
You need to build libcurl with either OpenSSL, GnuTLS or NSS support for this option to work, or build libcurl on Windows with SSPI support.
CURLAUTH_NTLM_WB
NTLM delegating to winbind helper. Authentication is performed by a separate binary application that is executed when needed. The name of the application is specified at compile time but is typically /usr/bin/ntlm_auth (Added in 7.22.0)
Note that libcurl will fork when necessary to run the winbind application and kill it when complete, calling waitpid() to await its exit when done. On POSIX operating systems, killing the process will cause a SIGCHLD signal to be raised (regardless of whether CURLOPT_NOSIGNAL is set), which must be handled intelligently by the application. In particular, the application must not unconditionally call wait() in its SIGCHLD signal handler to avoid being subject to a race condition. This behavior is subject to change in future versions of libcurl.
CURLAUTH_ANY
This is a convenience macro that sets all bits and thus makes libcurl pick any it finds suitable. libcurl will automatically select the one it finds most secure.
CURLAUTH_ANYSAFE
This is a convenience macro that sets all bits except Basic and thus makes libcurl pick any it finds suitable. libcurl will automatically select the one it finds most secure.
CURLAUTH_ONLY
This is a meta symbol. Or this value together with a single specific auth value to force libcurl to probe for un-restricted auth and if not, only that single auth algorithm is acceptable. (Added in 7.21.3)
CURLOPT_TLSAUTH_TYPE
Pass a long as parameter, which is set to a bitmask, to tell libcurl which authentication method(s) you want it to use for TLS authentication.
CURLOPT_TLSAUTH_SRP
TLS-SRP authentication. Secure Remote Password authentication for TLS is defined in RFC 5054 and provides mutual authentication if both sides have a shared secret. To use TLS-SRP, you must also set the CURLOPT_TLSAUTH_USERNAME and CURLOPT_TLSAUTH_PASSWORD options.
You need to build libcurl with GnuTLS or OpenSSL with TLS-SRP support for this to work. (Added in 7.21.4)
CURLOPT_TLSAUTH_USERNAME
Pass a char * as parameter, which should point to the zero terminated username to use for the TLS authentication method specified with the CURLOPT_TLSAUTH_TYPE option. Requires that the CURLOPT_TLS_PASSWORD option also be set. (Added in 7.21.4)
CURLOPT_TLSAUTH_PASSWORD
Pass a char * as parameter, which should point to the zero terminated password to use for the TLS authentication method specified with the CURLOPT_TLSAUTH_TYPE option. Requires that the CURLOPT_TLS_USERNAME option also be set. (Added in 7.21.4)
CURLOPT_PROXYAUTH
Pass a long as parameter, which is set to a bitmask, to tell libcurl which authentication method(s) you want it to use for your proxy authentication. If more than one bit is set, libcurl will first query the site to see what authentication methods it supports and then pick the best one you allow it to use. For some methods, this will induce an extra network round-trip. Set the actual name and password with the CURLOPT_PROXYUSERPWD option. The bitmask can be constructed by or'ing together the bits listed above for the CURLOPT_HTTPAUTH option. CURLOPT_PROXYAUTH was added in 7.10.7
CURLOPT_SASL_IR
Pass a long. If the value is 1, curl will send the initial response to the server in the first authentication packet in order to reduce the number of ping pong requests. Only applicable to supporting SASL authentication mechanisms and to the IMAP, POP3 and SMTP protocols. (Added in 7.31.0)
Note: Whilst IMAP supports this option there is no need to explicitly set it, as libcurl can determine the feature itself when the server supports the SASL-IR CAPABILITY.
CURLOPT_XOAUTH2_BEARER
Pass a char * as parameter, which should point to the zero terminated OAuth 2.0 Bearer Access Token for use with IMAP, POP3 and SMTP servers that support the OAuth 2.0 Authorization Framework. (Added in 7.33.0)
Note: The user name used to generate the Bearer Token should be supplied via the CURLOPT_USERNAME option.
HTTP OPTIONS
CURLOPT_AUTOREFERER
Pass a parameter set to 1 to enable this. When enabled, libcurl will automatically set the Referer: field in requests where it follows a Location: redirect.
CURLOPT_ACCEPT_ENCODING
Sets the contents of the Accept-Encoding: header sent in a HTTP request, and enables decoding of a response when a Content-Encoding: header is received. Three encodings are supported: identity, which does nothing, deflate which requests the server to compress its response using the zlib algorithm, and gzip which requests the gzip algorithm. If a zero-length string is set, then an Accept-Encoding: header containing all supported encodings is sent.
This is a request, not an order; the server may or may not do it. This option must be set (to any non-NULL value) or else any unsolicited encoding done by the server is ignored. See the special file lib/README.encoding for details.
(This option was called CURLOPT_ENCODING before 7.21.6)
CURLOPT_TRANSFER_ENCODING
Adds a request for compressed Transfer Encoding in the outgoing HTTP request. If the server supports this and so desires, it can respond with the HTTP response sent using a compressed Transfer-Encoding that will be automatically uncompressed by libcurl on reception.
Transfer-Encoding differs slightly from the Content-Encoding you ask for with CURLOPT_ACCEPT_ENCODING in that a Transfer-Encoding is strictly meant to be for the transfer and thus MUST be decoded before the data arrives in the client. Traditionally, Transfer-Encoding has been much less used and supported by both HTTP clients and HTTP servers.
(Added in 7.21.6)
CURLOPT_FOLLOWLOCATION
A parameter set to 1 tells the library to follow any Location: header that the server sends as part of a HTTP header.
This means that the library will re-send the same request on the new location and follow new Location: headers all the way until no more such headers are returned. CURLOPT_MAXREDIRS can be used to limit the number of redirects libcurl will follow.
Since 7.19.4, libcurl can limit what protocols it will automatically follow. The accepted protocols are set with CURLOPT_REDIR_PROTOCOLS and it excludes the FILE protocol by default.
CURLOPT_UNRESTRICTED_AUTH
A parameter set to 1 tells the library it can continue to send authentication (user+password) when following locations, even when hostname changed. This option is meaningful only when setting CURLOPT_FOLLOWLOCATION.
CURLOPT_MAXREDIRS
Pass a long. The set number will be the redirection limit. If that many redirections have been followed, the next redirect will cause an error (CURLE_TOO_MANY_REDIRECTS). This option only makes sense if the CURLOPT_FOLLOWLOCATION is used at the same time. Added in 7.15.1: Setting the limit to 0 will make libcurl refuse any redirect. Set it to -1 for an infinite number of redirects (which is the default)
CURLOPT_POSTREDIR
Pass a bitmask to control how libcurl acts on redirects after POSTs that get a 301, 302 or 303 response back. A parameter with bit 0 set (value CURL_REDIR_POST_301) tells the library to respect RFC 2616/10.3.2 and not convert POST requests into GET requests when following a 301 redirection. Setting bit 1 (value CURL_REDIR_POST_302) makes libcurl maintain the request method after a 302 redirect whilst setting bit 2 (value CURL_REDIR_POST_303) makes libcurl maintain the request method after a 303 redirect. The value CURL_REDIR_POST_ALL is a convenience define that sets all three bits.
The non-RFC behaviour is ubiquitous in web browsers, so the library does the conversion by default to maintain consistency. However, a server may require a POST to remain a POST after such a redirection. This option is meaningful only when setting CURLOPT_FOLLOWLOCATION. (Added in 7.17.1) (This option was known as CURLOPT_POST301 up to 7.19.0 as it only supported the 301 then)
CURLOPT_PUT
A parameter set to 1 tells the library to use HTTP PUT to transfer data. The data should be set with CURLOPT_READDATA and CURLOPT_INFILESIZE.
This option is deprecated and starting with version 7.12.1 you should instead use CURLOPT_UPLOAD.
CURLOPT_POST
A parameter set to 1 tells the library to do a regular HTTP post. This will also make the library use a "Content-Type: application/x-www-form-urlencoded" header. (This is by far the most commonly used POST method).
Use one of CURLOPT_POSTFIELDS or CURLOPT_COPYPOSTFIELDS options to specify what data to post and CURLOPT_POSTFIELDSIZE or CURLOPT_POSTFIELDSIZE_LARGE to set the data size.
Optionally, you can provide data to POST using the CURLOPT_READFUNCTION and CURLOPT_READDATA options but then you must make sure to not set CURLOPT_POSTFIELDS to anything but NULL. When providing data with a callback, you must transmit it using chunked transfer-encoding or you must set the size of the data with the CURLOPT_POSTFIELDSIZE or CURLOPT_POSTFIELDSIZE_LARGE option. To enable chunked encoding, you simply pass in the appropriate Transfer-Encoding header, see the post-callback.c example.
You can override the default POST Content-Type: header by setting your own with CURLOPT_HTTPHEADER.
Using POST with HTTP 1.1 implies the use of a "Expect: 100-continue" header. You can disable this header with CURLOPT_HTTPHEADER as usual.
If you use POST to a HTTP 1.1 server, you can send data without knowing the size before starting the POST if you use chunked encoding. You enable this by adding a header like "Transfer-Encoding: chunked" with CURLOPT_HTTPHEADER. With HTTP 1.0 or without chunked transfer, you must specify the size in the request.
When setting CURLOPT_POST to 1, it will automatically set CURLOPT_NOBODY to 0 (since 7.14.1).
If you issue a POST request and then want to make a HEAD or GET using the same re-used handle, you must explicitly set the new request type using CURLOPT_NOBODY or CURLOPT_HTTPGET or similar.
CURLOPT_POSTFIELDS
Pass a void * as parameter, which should be the full data to post in a HTTP POST operation. You must make sure that the data is formatted the way you want the server to receive it. libcurl will not convert or encode it for you. Most web servers will assume this data to be url-encoded.
The pointed data are NOT copied by the library: as a consequence, they must be preserved by the calling application until the transfer finishes.
This POST is a normal application/x-www-form-urlencoded kind (and libcurl will set that Content-Type by default when this option is used), which is the most commonly used one by HTML forms. See also the CURLOPT_POST. Using CURLOPT_POSTFIELDS implies CURLOPT_POST.
If you want to do a zero-byte POST, you need to set CURLOPT_POSTFIELDSIZE explicitly to zero, as simply setting CURLOPT_POSTFIELDS to NULL or "" just effectively disables the sending of the specified string. libcurl will instead assume that you'll send the POST data using the read callback!
Using POST with HTTP 1.1 implies the use of a "Expect: 100-continue" header. You can disable this header with CURLOPT_HTTPHEADER as usual.
To make multipart/formdata posts (aka RFC 2388-posts), check out the CURLOPT_HTTPPOST option.
CURLOPT_POSTFIELDSIZE
If you want to post data to the server without letting libcurl do a strlen() to measure the data size, this option must be used. When this option is used you can post fully binary data, which otherwise is likely to fail. If this size is set to -1, the library will use strlen() to get the size.
CURLOPT_POSTFIELDSIZE_LARGE
Pass a curl_off_t as parameter. Use this to set the size of the CURLOPT_POSTFIELDS data to prevent libcurl from doing strlen() on the data to figure out the size. This is the large file version of the CURLOPT_POSTFIELDSIZE option. (Added in 7.11.1)
CURLOPT_COPYPOSTFIELDS
Pass a char * as parameter, which should be the full data to post in a HTTP POST operation. It behaves as the CURLOPT_POSTFIELDS option, but the original data are copied by the library, allowing the application to overwrite the original data after setting this option.
Because data are copied, care must be taken when using this option in conjunction with CURLOPT_POSTFIELDSIZE or CURLOPT_POSTFIELDSIZE_LARGE: If the size has not been set prior to CURLOPT_COPYPOSTFIELDS, the data are assumed to be a NUL-terminated string; else the stored size informs the library about the data byte count to copy. In any case, the size must not be changed after CURLOPT_COPYPOSTFIELDS, unless another CURLOPT_POSTFIELDS or CURLOPT_COPYPOSTFIELDS option is issued. (Added in 7.17.1)
CURLOPT_HTTPPOST
Tells libcurl you want a multipart/formdata HTTP POST to be made and you instruct what data to pass on to the server. Pass a pointer to a linked list of curl_httppost structs as parameter. The easiest way to create such a list, is to use curl_formadd(3) as documented. The data in this list must remain intact until you close this curl handle again with curl_easy_cleanup(3).
Using POST with HTTP 1.1 implies the use of a "Expect: 100-continue" header. You can disable this header with CURLOPT_HTTPHEADER as usual.
When setting CURLOPT_HTTPPOST, it will automatically set CURLOPT_NOBODY to 0 (since 7.14.1).
CURLOPT_REFERER
Pass a pointer to a zero terminated string as parameter. It will be used to set the Referer: header in the http request sent to the remote server. This can be used to fool servers or scripts. You can also set any custom header with CURLOPT_HTTPHEADER.
CURLOPT_USERAGENT
Pass a pointer to a zero terminated string as parameter. It will be used to set the User-Agent: header in the http request sent to the remote server. This can be used to fool servers or scripts. You can also set any custom header with CURLOPT_HTTPHEADER.
CURLOPT_HTTPHEADER
Pass a pointer to a linked list of HTTP headers to pass to the server in your HTTP request. The linked list should be a fully valid list of struct curl_slist structs properly filled in. Use curl_slist_append(3) to create the list and curl_slist_free_all(3) to clean up an entire list. If you add a header that is otherwise generated and used by libcurl internally, your added one will be used instead. If you add a header with no content as in 'Accept:' (no data on the right side of the colon), the internally used header will get disabled. Thus, using this option you can add new headers, replace internal headers and remove internal headers. To add a header with no content (nothing to the right side of the colon), use the form 'MyHeader;' (note the ending semicolon).
The headers included in the linked list must not be CRLF-terminated, because curl adds CRLF after each header item. Failure to comply with this will result in strange bugs because the server will most likely ignore part of the headers you specified.
The first line in a request (containing the method, usually a GET or POST) is not a header and cannot be replaced using this option. Only the lines following the request-line are headers. Adding this method line in this list of headers will only cause your request to send an invalid header.
Pass a NULL to this to reset back to no custom headers.
The most commonly replaced headers have "shortcuts" in the options CURLOPT_COOKIE, CURLOPT_USERAGENT and CURLOPT_REFERER.
CURLOPT_HTTP200ALIASES
Pass a pointer to a linked list of aliases to be treated as valid HTTP 200 responses. Some servers respond with a custom header response line. For example, IceCast servers respond with "ICY 200 OK". By including this string in your list of aliases, the response will be treated as a valid HTTP header line such as "HTTP/1.0 200 OK". (Added in 7.10.3)
The linked list should be a fully valid list of struct curl_slist structs, and be properly filled in. Use curl_slist_append(3) to create the list and curl_slist_free_all(3) to clean up an entire list.
The alias itself is not parsed for any version strings. Before libcurl 7.16.3, Libcurl used the value set by option CURLOPT_HTTP_VERSION, but starting with 7.16.3 the protocol is assumed to match HTTP 1.0 when an alias matched.
CURLOPT_COOKIE
Pass a pointer to a zero terminated string as parameter. It will be used to set a cookie in the http request. The format of the string should be NAME=CONTENTS, where NAME is the cookie name and CONTENTS is what the cookie should contain.
If you need to set multiple cookies, you need to set them all using a single option and thus you need to concatenate them all in one single string. Set multiple cookies in one string like this: "name1=content1; name2=content2;" etc.
This option sets the cookie header explicitly in the outgoing request(s). If multiple requests are done due to authentication, followed redirections or similar, they will all get this cookie passed on.
Using this option multiple times will only make the latest string override the previous ones.
CURLOPT_COOKIEFILE
Pass a pointer to a zero terminated string as parameter. It should contain the name of your file holding cookie data to read. The cookie data may be in Netscape / Mozilla cookie data format or just regular HTTP-style headers dumped to a file.
Given an empty or non-existing file or by passing the empty string (""), this option will enable cookies for this curl handle, making it understand and parse received cookies and then use matching cookies in future requests.
If you use this option multiple times, you just add more files to read. Subsequent files will add more cookies.
CURLOPT_COOKIEJAR
Pass a file name as char *, zero terminated. This will make libcurl write all internally known cookies to the specified file when curl_easy_cleanup(3) is called. If no cookies are known, no file will be created. Specify "-" to instead have the cookies written to stdout. Using this option also enables cookies for this session, so if you for example follow a location it will make matching cookies get sent accordingly.
If the cookie jar file can't be created or written to (when the curl_easy_cleanup(3) is called), libcurl will not and cannot report an error for this. Using CURLOPT_VERBOSE or CURLOPT_DEBUGFUNCTION will get a warning to display, but that is the only visible feedback you get about this possibly lethal situation.
CURLOPT_COOKIESESSION
Pass a long set to 1 to mark this as a new cookie "session". It will force libcurl to ignore all cookies it is about to load that are "session cookies" from the previous session. By default, libcurl always stores and loads all cookies, independent if they are session cookies or not. Session cookies are cookies without expiry date and they are meant to be alive and existing for this "session" only.
CURLOPT_COOKIELIST
Pass a char * to a cookie string. Cookie can be either in Netscape / Mozilla format or just regular HTTP-style header (Set-Cookie: ...) format. If cURL cookie engine was not enabled it will enable its cookie engine. Passing a magic string "ALL" will erase all cookies known by cURL. (Added in 7.14.1) Passing the special string "SESS" will only erase all session cookies known by cURL. (Added in 7.15.4) Passing the special string "FLUSH" will write all cookies known by cURL to the file specified by CURLOPT_COOKIEJAR. (Added in 7.17.1)
CURLOPT_HTTPGET
Pass a long. If the long is 1, this forces the HTTP request to get back to GET. Usable if a POST, HEAD, PUT, or a custom request has been used previously using the same curl handle.
When setting CURLOPT_HTTPGET to 1, it will automatically set CURLOPT_NOBODY to 0 and CURLOPT_UPLOAD to 0.
CURLOPT_HTTP_VERSION
Pass a long, set to one of the values described below. They force libcurl to use the specific HTTP versions. This is not sensible to do unless you have a good reason.
CURL_HTTP_VERSION_NONE
We don't care about what version the library uses. libcurl will use whatever it thinks fit.
CURL_HTTP_VERSION_1_0
Enforce HTTP 1.0 requests.
CURL_HTTP_VERSION_1_1
Enforce HTTP 1.1 requests.
CURLOPT_IGNORE_CONTENT_LENGTH
Ignore the Content-Length header. This is useful for Apache 1.x (and similar servers) which will report incorrect content length for files over 2 gigabytes. If this option is used, curl will not be able to accurately report progress, and will simply stop the download when the server ends the connection. (added in 7.14.1)
CURLOPT_HTTP_CONTENT_DECODING
Pass a long to tell libcurl how to act on content decoding. If set to zero, content decoding will be disabled. If set to 1 it is enabled. Libcurl has no default content decoding but requires you to use CURLOPT_ACCEPT_ENCODING for that. (added in 7.16.2)
CURLOPT_HTTP_TRANSFER_DECODING
Pass a long to tell libcurl how to act on transfer decoding. If set to zero, transfer decoding will be disabled, if set to 1 it is enabled (default). libcurl does chunked transfer decoding by default unless this option is set to zero. (added in 7.16.2)
SMTP OPTIONS
CURLOPT_MAIL_FROM
Pass a pointer to a zero terminated string as parameter. This should be used to specify the sender's email address when sending SMTP mail with libcurl.
An originator email address should be specified with angled brackets (<>) around it, which if not specified, will be added by libcurl from version 7.21.4 onwards. Failing to provide such brackets may cause the server to reject the email.
If this parameter is not specified then an empty address will be sent to the mail server which may or may not cause the email to be rejected.
(Added in 7.20.0)
CURLOPT_MAIL_RCPT
Pass a pointer to a linked list of recipients to pass to the server in your SMTP mail request. The linked list should be a fully valid list of struct curl_slist structs properly filled in. Use curl_slist_append(3) to create the list and curl_slist_free_all(3) to clean up an entire list.
When performing a mail transfer, each recipient should be specified within a pair of angled brackets (<>), however, should you not use an angled bracket as the first character libcurl will assume you provided a single email address and enclose that address within brackets for you. (Added in 7.20.0)
When performing an address verification (VRFY command), each recipient should be specified as the user name or user name and domain (as per Section 3.5 of RFC 5321). (Added in 7.34.0)
When performing a mailing list expand (EXPN command), each recipient should be specified using the mailing list name, such as "Friends" or "London-Office". (Added in 7.34.0)
CURLOPT_MAIL_AUTH
Pass a pointer to a zero terminated string as parameter. This will be used to specify the authentication address (identity) of a submitted message that is being relayed to another server.
This optional parameter allows co-operating agents in a trusted environment to communicate the authentication of individual messages and should only be used by the application program, using libcurl, if the application is itself a mail server acting in such an environment. If the application is operating as such and the AUTH address is not known or is invalid, then an empty string should be used for this parameter.
Unlike CURLOPT_MAIL_FROM and CURLOPT_MAIL_RCPT, the address should not be specified within a pair of angled brackets (<>). However, if an empty string is used then a pair of brackets will be sent by libcurl as required by RFC 2554.
(Added in 7.25.0)
TFTP OPTIONS
CURLOPT_TFTP_BLKSIZE
Specify block size to use for TFTP data transmission. Valid range as per RFC 2348 is 8-65464 bytes. The default of 512 bytes will be used if this option is not specified. The specified block size will only be used pending support by the remote server. If the server does not return an option acknowledgement or returns an option acknowledgement with no blksize, the default of 512 bytes will be used. (added in 7.19.4)
FTP OPTIONS
CURLOPT_FTPPORT
Pass a pointer to a zero terminated string as parameter. It will be used to get the IP address to use for the FTP PORT instruction. The PORT instruction tells the remote server to connect to our specified IP address. The string may be a plain IP address, a host name, a network interface name (under Unix) or just a '-' symbol to let the library use your system's default IP address. Default FTP operations are passive, and thus won't use PORT.
The address can be followed by a ':' to specify a port, optionally followed by a '-' to specify a port range. If the port specified is 0, the operating system will pick a free port. If a range is provided and all ports in the range are not available, libcurl will report CURLE_FTP_PORT_FAILED for the handle. Invalid port/range settings are ignored. IPv6 addresses followed by a port or portrange have to be in brackets. IPv6 addresses without port/range specifier can be in brackets. (added in 7.19.5)
Examples with specified ports:
eth0:0
192.168.1.2:32000-33000
curl.se:32123
[::1]:1234-4567
You disable PORT again and go back to using the passive version by setting this option to NULL.
CURLOPT_QUOTE
Pass a pointer to a linked list of FTP or SFTP commands to pass to the server prior to your FTP request. This will be done before any other commands are issued (even before the CWD command for FTP). The linked list should be a fully valid list of 'struct curl_slist' structs properly filled in with text strings. Use curl_slist_append(3) to append strings (commands) to the list, and clear the entire list afterwards with curl_slist_free_all(3). Disable this operation again by setting a NULL to this option. When speaking to a FTP (or SFTP since 7.24.0) server, prefix the command with an asterisk (*) to make libcurl continue even if the command fails as by default libcurl will stop at first failure.
The set of valid FTP commands depends on the server (see RFC 959 for a list of mandatory commands).
The valid SFTP commands are: chgrp, chmod, chown, ln, mkdir, pwd, rename, rm, rmdir, symlink (see curl (1)) (SFTP support added in 7.16.3)
CURLOPT_POSTQUOTE
Pass a pointer to a linked list of FTP or SFTP commands to pass to the server after your FTP transfer request. The commands will only be run if no error occurred. The linked list should be a fully valid list of struct curl_slist structs properly filled in as described for CURLOPT_QUOTE. Disable this operation again by setting a NULL to this option.
CURLOPT_PREQUOTE
Pass a pointer to a linked list of FTP commands to pass to the server after the transfer type is set. The linked list should be a fully valid list of struct curl_slist structs properly filled in as described for CURLOPT_QUOTE. Disable this operation again by setting a NULL to this option. Before version 7.16.0, if you also set CURLOPT_NOBODY to 1, this option didn't work.
CURLOPT_DIRLISTONLY
A parameter set to 1 tells the library to just list the names of files in a directory, instead of doing a full directory listing that would include file sizes, dates etc. This works for FTP and SFTP URLs.
This causes an FTP NLST command to be sent on an FTP server. Beware that some FTP servers list only files in their response to NLST; they might not include subdirectories and symbolic links.
Setting this option to 1 also implies a directory listing even if the URL doesn't end with a slash, which otherwise is necessary.
Do NOT use this option if you also use CURLOPT_WILDCARDMATCH as it will effectively break that feature then.
(This option was known as CURLOPT_FTPLISTONLY up to 7.16.4)
CURLOPT_APPEND
A parameter set to 1 tells the library to append to the remote file instead of overwrite it. This is only useful when uploading to an FTP site.
(This option was known as CURLOPT_FTPAPPEND up to 7.16.4)
CURLOPT_FTP_USE_EPRT
Pass a long. If the value is 1, it tells curl to use the EPRT (and LPRT) command when doing active FTP downloads (which is enabled by CURLOPT_FTPPORT). Using EPRT means that it will first attempt to use EPRT and then LPRT before using PORT, but if you pass zero to this option, it will not try using EPRT or LPRT, only plain PORT. (Added in 7.10.5)
If the server is an IPv6 host, this option will have no effect as of 7.12.3.
CURLOPT_FTP_USE_EPSV
Pass a long. If the value is 1, it tells curl to use the EPSV command when doing passive FTP downloads (which it always does by default). Using EPSV means that it will first attempt to use EPSV before using PASV, but if you pass zero to this option, it will not try using EPSV, only plain PASV.
If the server is an IPv6 host, this option will have no effect as of 7.12.3.
CURLOPT_FTP_USE_PRET
Pass a long. If the value is 1, it tells curl to send a PRET command before PASV (and EPSV). Certain FTP servers, mainly drftpd, require this non-standard command for directory listings as well as up and downloads in PASV mode. Has no effect when using the active FTP transfers mode. (Added in 7.20.0)
CURLOPT_FTP_CREATE_MISSING_DIRS
Pass a long. If the value is 1, curl will attempt to create any remote directory that it fails to CWD into. CWD is the command that changes working directory. (Added in 7.10.7)
This setting also applies to SFTP-connections. curl will attempt to create the remote directory if it can't obtain a handle to the target-location. The creation will fail if a file of the same name as the directory to create already exists or lack of permissions prevents creation. (Added in 7.16.3)
Starting with 7.19.4, you can also set this value to 2, which will make libcurl retry the CWD command again if the subsequent MKD command fails. This is especially useful if you're doing many simultaneous connections against the same server and they all have this option enabled, as then CWD may first fail but then another connection does MKD before this connection and thus MKD fails but trying CWD works! 7.19.4 also introduced the CURLFTP_CREATE_DIR and CURLFTP_CREATE_DIR_RETRY enum names for these arguments.
Before version 7.19.4, libcurl will simply ignore arguments set to 2 and act as if 1 was selected.
CURLOPT_FTP_RESPONSE_TIMEOUT
Pass a long. Causes curl to set a timeout period (in seconds) on the amount of time that the server is allowed to take in order to generate a response message for a command before the session is considered hung. While curl is waiting for a response, this value overrides CURLOPT_TIMEOUT. It is recommended that if used in conjunction with CURLOPT_TIMEOUT, you set CURLOPT_FTP_RESPONSE_TIMEOUT to a value smaller than CURLOPT_TIMEOUT. (Added in 7.10.8)
CURLOPT_FTP_ALTERNATIVE_TO_USER
Pass a char * as parameter, pointing to a string which will be used to authenticate if the usual FTP "USER user" and "PASS password" negotiation fails. This is currently only known to be required when connecting to Tumbleweed's Secure Transport FTPS server using client certificates for authentication. (Added in 7.15.5)
CURLOPT_FTP_SKIP_PASV_IP
Pass a long. If set to 1, it instructs libcurl to not use the IP address the server suggests in its 227-response to libcurl's PASV command when libcurl connects the data connection. Instead libcurl will re-use the same IP address it already uses for the control connection. But it will use the port number from the 227-response. (Added in 7.14.2)
This option has no effect if PORT, EPRT or EPSV is used instead of PASV.
CURLOPT_FTPSSLAUTH
Pass a long using one of the values from below, to alter how libcurl issues "AUTH TLS" or "AUTH SSL" when FTP over SSL is activated (see CURLOPT_USE_SSL). (Added in 7.12.2)
CURLFTPAUTH_DEFAULT
Allow libcurl to decide.
CURLFTPAUTH_SSL
Try "AUTH SSL" first, and only if that fails try "AUTH TLS".
CURLFTPAUTH_TLS
Try "AUTH TLS" first, and only if that fails try "AUTH SSL".
CURLOPT_FTP_SSL_CCC
If enabled, this option makes libcurl use CCC (Clear Command Channel). It shuts down the SSL/TLS layer after authenticating. The rest of the control channel communication will be unencrypted. This allows NAT routers to follow the FTP transaction. Pass a long using one of the values below. (Added in 7.16.1)
CURLFTPSSL_CCC_NONE
Don't attempt to use CCC.
CURLFTPSSL_CCC_PASSIVE
Do not initiate the shutdown, but wait for the server to do it. Do not send a reply.
CURLFTPSSL_CCC_ACTIVE
Initiate the shutdown and wait for a reply.
CURLOPT_FTP_ACCOUNT
Pass a pointer to a zero terminated string (or NULL to disable). When an FTP server asks for "account data" after user name and password has been provided, this data is sent off using the ACCT command. (Added in 7.13.0)
CURLOPT_FTP_FILEMETHOD
Pass a long that should have one of the following values. This option controls what method libcurl should use to reach a file on a FTP(S) server. The argument should be one of the following alternatives:
CURLFTPMETHOD_MULTICWD
libcurl does a single CWD operation for each path part in the given URL. For deep hierarchies this means many commands. This is how RFC 1738 says it should be done. This is the default but the slowest behavior.
CURLFTPMETHOD_NOCWD
libcurl does no CWD at all. libcurl will do SIZE, RETR, STOR etc and give a full path to the server for all these commands. This is the fastest behavior.
CURLFTPMETHOD_SINGLECWD
libcurl does one CWD with the full target directory and then operates on the file "normally" (like in the multicwd case). This is somewhat more standards compliant than 'nocwd' but without the full penalty of 'multicwd'.
(Added in 7.15.1)
RTSP OPTIONS
CURLOPT_RTSP_REQUEST
Tell libcurl what kind of RTSP request to make. Pass one of the following RTSP enum values. Unless noted otherwise, commands require the Session ID to be initialized. (Added in 7.20.0)
CURL_RTSPREQ_OPTIONS
Used to retrieve the available methods of the server. The application is responsible for parsing and obeying the response. (The session ID is not needed for this method.) (Added in 7.20.0)
CURL_RTSPREQ_DESCRIBE
Used to get the low level description of a stream. The application should note what formats it understands in the 'Accept:' header. Unless set manually, libcurl will automatically fill in 'Accept: application/sdp'. Time-condition headers will be added to Describe requests if the CURLOPT_TIMECONDITION option is active. (The session ID is not needed for this method) (Added in 7.20.0)
CURL_RTSPREQ_ANNOUNCE
When sent by a client, this method changes the description of the session. For example, if a client is using the server to record a meeting, the client can use Announce to inform the server of all the meta-information about the session. ANNOUNCE acts like a HTTP PUT or POST just like CURL_RTSPREQ_SET_PARAMETER (Added in 7.20.0)
CURL_RTSPREQ_SETUP
Setup is used to initialize the transport layer for the session. The application must set the desired Transport options for a session by using the CURLOPT_RTSP_TRANSPORT option prior to calling setup. If no session ID is currently set with CURLOPT_RTSP_SESSION_ID, libcurl will extract and use the session ID in the response to this request. (The session ID is not needed for this method). (Added in 7.20.0)
CURL_RTSPREQ_PLAY
Send a Play command to the server. Use the CURLOPT_RANGE option to modify the playback time (e.g. 'npt=10-15'). (Added in 7.20.0)
CURL_RTSPREQ_PAUSE
Send a Pause command to the server. Use the CURLOPT_RANGE option with a single value to indicate when the stream should be halted. (e.g. npt='25') (Added in 7.20.0)
CURL_RTSPREQ_TEARDOWN
This command terminates an RTSP session. Simply closing a connection does not terminate the RTSP session since it is valid to control an RTSP session over different connections. (Added in 7.20.0)
CURL_RTSPREQ_GET_PARAMETER
Retrieve a parameter from the server. By default, libcurl will automatically include a Content-Type: text/parameters header on all non-empty requests unless a custom one is set. GET_PARAMETER acts just like a HTTP PUT or POST (see CURL_RTSPREQ_SET_PARAMETER). Applications wishing to send a heartbeat message (e.g. in the presence of a server-specified timeout) should send use an empty GET_PARAMETER request. (Added in 7.20.0)
CURL_RTSPREQ_SET_PARAMETER
Set a parameter on the server. By default, libcurl will automatically include a Content-Type: text/parameters header unless a custom one is set. The interaction with SET_PARAMTER is much like a HTTP PUT or POST. An application may either use CURLOPT_UPLOAD with CURLOPT_READDATA like a HTTP PUT, or it may use CURLOPT_POSTFIELDS like a HTTP POST. No chunked transfers are allowed, so the application must set the CURLOPT_INFILESIZE in the former and CURLOPT_POSTFIELDSIZE in the latter. Also, there is no use of multi-part POSTs within RTSP. (Added in 7.20.0)
CURL_RTSPREQ_RECORD
Used to tell the server to record a session. Use the CURLOPT_RANGE option to modify the record time. (Added in 7.20.0)
CURL_RTSPREQ_RECEIVE
This is a special request because it does not send any data to the server. The application may call this function in order to receive interleaved RTP data. It will return after processing one read buffer of data in order to give the application a chance to run. (Added in 7.20.0)
CURLOPT_RTSP_SESSION_ID
Pass a char * as a parameter to set the value of the current RTSP Session ID for the handle. Useful for resuming an in-progress session. Once this value is set to any non-NULL value, libcurl will return CURLE_RTSP_SESSION_ERROR if ID received from the server does not match. If unset (or set to NULL), libcurl will automatically set the ID the first time the server sets it in a response. (Added in 7.20.0)
CURLOPT_RTSP_STREAM_URI
Set the stream URI to operate on by passing a char * . For example, a single session may be controlling rtsp://foo/twister/audio and rtsp://foo/twister/video and the application can switch to the appropriate stream using this option. If unset, libcurl will default to operating on generic server options by passing '*' in the place of the RTSP Stream URI. This option is distinct from CURLOPT_URL. When working with RTSP, the CURLOPT_STREAM_URI indicates what URL to send to the server in the request header while the CURLOPT_URL indicates where to make the connection to. (e.g. the CURLOPT_URL for the above examples might be set to rtsp://foo/twister (Added in 7.20.0)
CURLOPT_RTSP_TRANSPORT
Pass a char * to tell libcurl what to pass for the Transport: header for this RTSP session. This is mainly a convenience method to avoid needing to set a custom Transport: header for every SETUP request. The application must set a Transport: header before issuing a SETUP request. (Added in 7.20.0)
CURLOPT_RTSP_HEADER
This option is simply an alias for CURLOPT_HTTP_HEADER. Use this to replace the standard headers that RTSP and HTTP share. It is also valid to use the shortcuts such as CURLOPT_USERAGENT. (Added in 7.20.0)
CURLOPT_RTSP_CLIENT_CSEQ
Manually set the the CSEQ number to issue for the next RTSP request. Useful if the application is resuming a previously broken connection. The CSEQ will increment from this new number henceforth. (Added in 7.20.0)
CURLOPT_RTSP_SERVER_CSEQ
Manually set the CSEQ number to expect for the next RTSP Server->Client request. At the moment, this feature (listening for Server requests) is unimplemented. (Added in 7.20.0)
PROTOCOL OPTIONS
CURLOPT_TRANSFERTEXT
A parameter set to 1 tells the library to use ASCII mode for FTP transfers, instead of the default binary transfer. For win32 systems it does not set the stdout to binary mode. This option can be usable when transferring text data between systems with different views on certain characters, such as newlines or similar.
libcurl does not do a complete ASCII conversion when doing ASCII transfers over FTP. This is a known limitation/flaw that nobody has rectified. libcurl simply sets the mode to ASCII and performs a standard transfer.
CURLOPT_PROXY_TRANSFER_MODE
Pass a long. If the value is set to 1 (one), it tells libcurl to set the transfer mode (binary or ASCII) for FTP transfers done via a HTTP proxy, by appending ;type=a or ;type=i to the URL. Without this setting, or it being set to 0 (zero, the default), CURLOPT_TRANSFERTEXT has no effect when doing FTP via a proxy. Beware that not all proxies support this feature. (Added in 7.18.0)
CURLOPT_CRLF
Pass a long. If the value is set to 1 (one), libcurl converts Unix newlines to CRLF newlines on transfers. Disable this option again by setting the value to 0 (zero).
CURLOPT_RANGE
Pass a char * as parameter, which should contain the specified range you want. It should be in the format "X-Y", where X or Y may be left out. HTTP transfers also support several intervals, separated with commas as in "X-Y,N-M". Using this kind of multiple intervals will cause the HTTP server to send the response document in pieces (using standard MIME separation techniques). For RTSP, the formatting of a range should follow RFC 2326 Section 12.29. For RTSP, byte ranges are not permitted. Instead, ranges should be given in npt, utc, or smpte formats.
Pass a NULL to this option to disable the use of ranges.
Ranges work on HTTP, FTP, FILE (since 7.18.0), and RTSP (since 7.20.0) transfers only.
CURLOPT_RESUME_FROM
Pass a long as parameter. It contains the offset in number of bytes that you want the transfer to start from. Set this option to 0 to make the transfer start from the beginning (effectively disabling resume). For FTP, set this option to -1 to make the transfer start from the end of the target file (useful to continue an interrupted upload).
When doing uploads with FTP, the resume position is where in the local/source file libcurl should try to resume the upload from and it will then append the source file to the remote target file.
CURLOPT_RESUME_FROM_LARGE
Pass a curl_off_t as parameter. It contains the offset in number of bytes that you want the transfer to start from. (Added in 7.11.0)
CURLOPT_CUSTOMREQUEST
Pass a pointer to a zero terminated string as parameter.
When you change the request method by setting CURLOPT_CUSTOMREQUEST to something, you don't actually change how libcurl behaves or acts in regards to the particular request method, it will only change the actual string sent in the request.
Restore to the internal default by setting this to NULL.
This option can be used to specify the request:
HTTP
Instead of GET or HEAD when performing HTTP based requests. This is particularly useful, for example, for performing a HTTP DELETE request.
For example:
When you tell libcurl to do a HEAD request, but then specify a GET though a custom request libcurl will still act as if it sent a HEAD. To switch to a proper HEAD use CURLOPT_NOBODY, to switch to a proper POST use CURLOPT_POST or CURLOPT_POSTFIELDS and to switch to a proper GET use CURLOPT_HTTPGET.
Please don't perform this at will, on HTTP based requests, by making sure your server supports the command you are sending first.
Many people have wrongly used this option to replace the entire request with their own, including multiple headers and POST contents. While that might work in many cases, it will cause libcurl to send invalid requests and it could possibly confuse the remote server badly. Use CURLOPT_POST and CURLOPT_POSTFIELDS to set POST data. Use CURLOPT_HTTPHEADER to replace or extend the set of headers sent by libcurl. Use CURLOPT_HTTP_VERSION to change HTTP version.
FTP
Instead of LIST and NLST when performing FTP directory listings.
IMAP
Instead of LIST when issuing IMAP based requests. (Added in 7.30.0)
POP3
Instead of LIST and RETR when issuing POP3 based requests. (Added in 7.26.0)
For example:
When you tell libcurl to use a custom request it will behave like a LIST or RETR command was sent where it expects data to be returned by the server. As such CURLOPT_NOBODY should be used when specifying commands such as DELE and NOOP for example.
SMTP
Instead of a HELP or VRFY when issuing SMTP based requests. (Added in 7.34.0)
For example:
Normally a multiline response is returned which can be used, in conjuection with CURLOPT_MAIL_RCPT, to specify an EXPN request. If the CURLOPT_NOBODY option is specified then the request can be used to issue NOOP and RSET commands.
CURLOPT_FILETIME
Pass a long. If it is 1, libcurl will attempt to get the modification date of the remote document in this operation. This requires that the remote server sends the time or replies to a time querying command. The curl_easy_getinfo(3) function with the CURLINFO_FILETIME argument can be used after a transfer to extract the received time (if any).
CURLOPT_NOBODY
A parameter set to 1 tells the library to not include the body-part in the output. This is only relevant for protocols that have separate header and body parts. On HTTP(S) servers, this will make libcurl do a HEAD request.
To change request to GET, you should use CURLOPT_HTTPGET. Change request to POST with CURLOPT_POST etc.
CURLOPT_INFILESIZE
When uploading a file to a remote site, this option should be used to tell libcurl what the expected size of the infile is. This value should be passed as a long. See also CURLOPT_INFILESIZE_LARGE.
For uploading using SCP, this option or CURLOPT_INFILESIZE_LARGE is mandatory.
To "unset" this value again, set it to -1.
When sending emails using SMTP, this command can be used to specify the optional SIZE parameter for the MAIL FROM command. (Added in 7.23.0)
This option does not limit how much data libcurl will actually send, as that is controlled entirely by what the read callback returns.
CURLOPT_INFILESIZE_LARGE
When uploading a file to a remote site, this option should be used to tell libcurl what the expected size of the infile is. This value should be passed as a curl_off_t. (Added in 7.11.0)
For uploading using SCP, this option or CURLOPT_INFILESIZE is mandatory.
To "unset" this value again, set it to -1.
When sending emails using SMTP, this command can be used to specify the optional SIZE parameter for the MAIL FROM command. (Added in 7.23.0)
This option does not limit how much data libcurl will actually send, as that is controlled entirely by what the read callback returns.
CURLOPT_UPLOAD
A parameter set to 1 tells the library to prepare for an upload. The CURLOPT_READDATA and CURLOPT_INFILESIZE or CURLOPT_INFILESIZE_LARGE options are also interesting for uploads. If the protocol is HTTP, uploading means using the PUT request unless you tell libcurl otherwise.
Using PUT with HTTP 1.1 implies the use of a "Expect: 100-continue" header. You can disable this header with CURLOPT_HTTPHEADER as usual.
If you use PUT to a HTTP 1.1 server, you can upload data without knowing the size before starting the transfer if you use chunked encoding. You enable this by adding a header like "Transfer-Encoding: chunked" with CURLOPT_HTTPHEADER. With HTTP 1.0 or without chunked transfer, you must specify the size.
CURLOPT_MAXFILESIZE
Pass a long as parameter. This allows you to specify the maximum size (in bytes) of a file to download. If the file requested is larger than this value, the transfer will not start and CURLE_FILESIZE_EXCEEDED will be returned.
The file size is not always known prior to download, and for such files this option has no effect even if the file transfer ends up being larger than this given limit. This concerns both FTP and HTTP transfers.
CURLOPT_MAXFILESIZE_LARGE
Pass a curl_off_t as parameter. This allows you to specify the maximum size (in bytes) of a file to download. If the file requested is larger than this value, the transfer will not start and CURLE_FILESIZE_EXCEEDED will be returned. (Added in 7.11.0)
The file size is not always known prior to download, and for such files this option has no effect even if the file transfer ends up being larger than this given limit. This concerns both FTP and HTTP transfers.
CURLOPT_TIMECONDITION
Pass a long as parameter. This defines how the CURLOPT_TIMEVALUE time value is treated. You can set this parameter to CURL_TIMECOND_IFMODSINCE or CURL_TIMECOND_IFUNMODSINCE. This feature applies to HTTP, FTP, RTSP, and FILE.
The last modification time of a file is not always known and in such instances this feature will have no effect even if the given time condition would not have been met. curl_easy_getinfo(3) with the CURLINFO_CONDITION_UNMET option can be used after a transfer to learn if a zero-byte successful "transfer" was due to this condition not matching.
CURLOPT_TIMEVALUE
Pass a long as parameter. This should be the time in seconds since 1 Jan 1970, and the time will be used in a condition as specified with CURLOPT_TIMECONDITION.
CONNECTION OPTIONS
CURLOPT_TIMEOUT
Pass a long as parameter containing the maximum time in seconds that you allow the libcurl transfer operation to take. Normally, name lookups can take a considerable time and limiting operations to less than a few minutes risk aborting perfectly normal operations. This option will cause curl to use the SIGALRM to enable time-outing system calls.
In unix-like systems, this might cause signals to be used unless CURLOPT_NOSIGNAL is set.
Default timeout is 0 (zero) which means it never times out.
CURLOPT_TIMEOUT_MS
An alternative to CURLOPT_TIMEOUT but takes number of milliseconds instead. If libcurl is built to use the standard system name resolver, that portion of the transfer will still use full-second resolution for timeouts with a minimum timeout allowed of one second.
If both CURLOPT_TIMEOUT and CURLOPT_TIMEOUT_MS are set, the value set last will be used.
(Added in 7.16.2)
CURLOPT_LOW_SPEED_LIMIT
Pass a long as parameter. It contains the transfer speed in bytes per second that the transfer should be below during CURLOPT_LOW_SPEED_TIME seconds for the library to consider it too slow and abort.
CURLOPT_LOW_SPEED_TIME
Pass a long as parameter. It contains the time in seconds that the transfer should be below the CURLOPT_LOW_SPEED_LIMIT for the library to consider it too slow and abort.
CURLOPT_MAX_SEND_SPEED_LARGE
Pass a curl_off_t as parameter. If an upload exceeds this speed (counted in bytes per second) on cumulative average during the transfer, the transfer will pause to keep the average rate less than or equal to the parameter value. Defaults to unlimited speed.
This option doesn't affect transfer speeds done with FILE:// URLs. (Added in 7.15.5)
CURLOPT_MAX_RECV_SPEED_LARGE
Pass a curl_off_t as parameter. If a download exceeds this speed (counted in bytes per second) on cumulative average during the transfer, the transfer will pause to keep the average rate less than or equal to the parameter value. Defaults to unlimited speed.
This option doesn't affect transfer speeds done with FILE:// URLs. (Added in 7.15.5)
CURLOPT_MAXCONNECTS
Pass a long. The set number will be the persistent connection cache size. The set amount will be the maximum amount of simultaneously open connections that libcurl may cache in this easy handle. Default is 5, and there isn't much point in changing this value unless you are perfectly aware of how this works and changes libcurl's behaviour. This concerns connections using any of the protocols that support persistent connections.
When reaching the maximum limit, curl closes the oldest one in the cache to prevent increasing the number of open connections.
If you already have performed transfers with this curl handle, setting a smaller MAXCONNECTS than before may cause open connections to get closed unnecessarily.
If you add this easy handle to a multi handle, this setting is not acknowledged, and you must instead use curl_multi_setopt(3) and the CURLMOPT_MAXCONNECTS option.
CURLOPT_CLOSEPOLICY
(Obsolete) This option does nothing.
CURLOPT_FRESH_CONNECT
Pass a long. Set to 1 to make the next transfer use a new (fresh) connection by force. If the connection cache is full before this connection, one of the existing connections will be closed as according to the selected or default policy. This option should be used with caution and only if you understand what it does. Set this to 0 to have libcurl attempt re-using an existing connection (default behavior).
CURLOPT_FORBID_REUSE
Pass a long. Set to 1 to make the next transfer explicitly close the connection when done. Normally, libcurl keeps all connections alive when done with one transfer in case a succeeding one follows that can re-use them. This option should be used with caution and only if you understand what it does. Set to 0 to have libcurl keep the connection open for possible later re-use (default behavior).
CURLOPT_CONNECTTIMEOUT
Pass a long. It should contain the maximum time in seconds that you allow the connection to the server to take. This only limits the connection phase, once it has connected, this option is of no more use. Set to zero to switch to the default built-in connection timeout - 300 seconds. See also the CURLOPT_TIMEOUT option.
In unix-like systems, this might cause signals to be used unless CURLOPT_NOSIGNAL is set.
CURLOPT_CONNECTTIMEOUT_MS
Like CURLOPT_CONNECTTIMEOUT but takes the number of milliseconds instead. If libcurl is built to use the standard system name resolver, that portion of the connect will still use full-second resolution for timeouts with a minimum timeout allowed of one second. (Added in 7.16.2)
CURLOPT_IPRESOLVE
Allows an application to select what kind of IP addresses to use when resolving host names. This is only interesting when using host names that resolve addresses using more than one version of IP. The allowed values are:
CURL_IPRESOLVE_WHATEVER
Default, resolves addresses to all IP versions that your system allows.
CURL_IPRESOLVE_V4
Resolve to IPv4 addresses.
CURL_IPRESOLVE_V6
Resolve to IPv6 addresses.
CURLOPT_CONNECT_ONLY
Pass a long. If the parameter equals 1, it tells the library to perform all the required proxy authentication and connection setup, but no data transfer. This option is implemented for HTTP, SMTP and POP3.
The option can be used to simply test a connection to a server, but is more useful when used with the CURLINFO_LASTSOCKET option to curl_easy_getinfo(3) as the library can set up the connection and then the application can obtain the most recently used socket for special data transfers. (Added in 7.15.2)
CURLOPT_USE_SSL
Pass a long using one of the values from below, to make libcurl use your desired level of SSL for the transfer. (Added in 7.11.0)
This is for enabling SSL/TLS when you use FTP, SMTP, POP3, IMAP etc.
(This option was known as CURLOPT_FTP_SSL up to 7.16.4, and the constants were known as CURLFTPSSL_*)
CURLUSESSL_NONE
Don't attempt to use SSL.
CURLUSESSL_TRY
Try using SSL, proceed as normal otherwise.
CURLUSESSL_CONTROL
Require SSL for the control connection or fail with CURLE_USE_SSL_FAILED.
CURLUSESSL_ALL
Require SSL for all communication or fail with CURLE_USE_SSL_FAILED.
CURLOPT_RESOLVE
Pass a pointer to a linked list of strings with host name resolve information to use for requests with this handle. The linked list should be a fully valid list of struct curl_slist structs properly filled in. Use curl_slist_append(3) to create the list and curl_slist_free_all(3) to clean up an entire list.
Each single name resolve string should be written using the format HOST:PORT:ADDRESS where HOST is the name libcurl will try to resolve, PORT is the port number of the service where libcurl wants to connect to the HOST and ADDRESS is the numerical IP address. If libcurl is built to support IPv6, ADDRESS can of course be either IPv4 or IPv6 style addressing.
This option effectively pre-populates the DNS cache with entries for the host+port pair so redirects and everything that operations against the HOST+PORT will instead use your provided ADDRESS. Addresses to set with CURL_RESOLVE will not time-out from the DNS cache like ordindary entries.
You can remove names from the DNS cache again, to stop providing these fake resolves, by including a string in the linked list that uses the format "-HOST:PORT". The host name must be prefixed with a dash, and the host name and port number must exactly match what was already added previously.
(Added in 7.21.3)
CURLOPT_DNS_SERVERS
Set the list of DNS servers to be used instead of the system default. The format of the dns servers option is:
host[:port][,host[:port]]...
For example:
192.168.1.100,192.168.1.101,3.4.5.6
This option requires that libcurl was built with a resolver backend that supports this operation. The c-ares backend is the only such one.
(Added in 7.24.0)
CURLOPT_DNS_INTERFACE
Pass a char * as parameter. Set the name of the network interface that the DNS resolver should bind to. This must be an interface name (not an address). Set this option to NULL to use the default setting (don't bind to a specific interface).
This option requires that libcurl was built with a resolver backend that supports this operation. The c-ares backend is the only such one.
(Added in 7.33.0)
CURLOPT_DNS_LOCAL_IP4
Set the local IPv4 address that the resolver should bind to. The argument should be of type char * and contain a single IPv4 address as a string. Set this option to NULL to use the default setting (don't bind to a specific IP address).
This option requires that libcurl was built with a resolver backend that supports this operation. The c-ares backend is the only such one.
(Added in 7.33.0)
CURLOPT_DNS_LOCAL_IP6
Set the local IPv6 address that the resolver should bind to. The argument should be of type char * and contain a single IPv6 address as a string. Set this option to NULL to use the default setting (don't bind to a specific IP address).
This option requires that libcurl was built with a resolver backend that supports this operation. The c-ares backend is the only such one.
(Added in 7.33.0)
CURLOPT_ACCEPTTIMEOUT_MS
Pass a long telling libcurl the maximum number of milliseconds to wait for a server to connect back to libcurl when an active FTP connection is used. If no timeout is set, the internal default of 60000 will be used. (Added in 7.24.0)
SSL and SECURITY OPTIONS
CURLOPT_SSLCERT
Pass a pointer to a zero terminated string as parameter. The string should be the file name of your certificate. The default format is "P12" on Secure Transport and "PEM" on other engines, and can be changed with CURLOPT_SSLCERTTYPE.
With NSS or Secure Transport, this can also be the nickname of the certificate you wish to authenticate with as it is named in the security database. If you want to use a file from the current directory, please precede it with "./" prefix, in order to avoid confusion with a nickname.
CURLOPT_SSLCERTTYPE
Pass a pointer to a zero terminated string as parameter. The string should be the format of your certificate. Supported formats are "PEM" and "DER", except with Secure Transport. OpenSSL (versions 0.9.3 and later) and Secure Transport (on iOS 5 or later, or OS X 10.7 or later) also support "P12" for PKCS#12-encoded files. (Added in 7.9.3)
CURLOPT_SSLKEY
Pass a pointer to a zero terminated string as parameter. The string should be the file name of your private key. The default format is "PEM" and can be changed with CURLOPT_SSLKEYTYPE.
(iOS and Mac OS X only) This option is ignored if curl was built against Secure Transport. Secure Transport expects the private key to be already present in the keychain or PKCS#12 file containing the certificate.
CURLOPT_SSLKEYTYPE
Pass a pointer to a zero terminated string as parameter. The string should be the format of your private key. Supported formats are "PEM", "DER" and "ENG".
The format "ENG" enables you to load the private key from a crypto engine. In this case CURLOPT_SSLKEY is used as an identifier passed to the engine. You have to set the crypto engine with CURLOPT_SSLENGINE. "DER" format key file currently does not work because of a bug in OpenSSL.
CURLOPT_KEYPASSWD
Pass a pointer to a zero terminated string as parameter. It will be used as the password required to use the CURLOPT_SSLKEY or CURLOPT_SSH_PRIVATE_KEYFILE private key. You never needed a pass phrase to load a certificate but you need one to load your private key.
(This option was known as CURLOPT_SSLKEYPASSWD up to 7.16.4 and CURLOPT_SSLCERTPASSWD up to 7.9.2)
CURLOPT_SSLENGINE
Pass a pointer to a zero terminated string as parameter. It will be used as the identifier for the crypto engine you want to use for your private key.
If the crypto device cannot be loaded, CURLE_SSL_ENGINE_NOTFOUND is returned.
CURLOPT_SSLENGINE_DEFAULT
Sets the actual crypto engine as the default for (asymmetric) crypto operations.
If the crypto device cannot be set, CURLE_SSL_ENGINE_SETFAILED is returned.
Even though this option doesn't need any parameter, in some configurations curl_easy_setopt might be defined as a macro taking exactly three arguments. Therefore, it's recommended to pass 1 as parameter to this option.
CURLOPT_SSLVERSION
Pass a long as parameter to control what version of SSL/TLS to attempt to use. (Added in 7.9.2)
The available options are:
CURL_SSLVERSION_DEFAULT
The default action. This will attempt to figure out the remote SSL protocol version, i.e. either SSLv3 or TLSv1 (but not SSLv2, which became disabled by default with 7.18.1).
CURL_SSLVERSION_TLSv1
Force TLSv1.x
CURL_SSLVERSION_SSLv2
Force SSLv2
CURL_SSLVERSION_SSLv3
Force SSLv3
CURL_SSLVERSION_TLSv1_0
Force TLSv1.0 (Added in 7.34.0)
CURL_SSLVERSION_TLSv1_1
Force TLSv1.1 (Added in 7.34.0)
CURL_SSLVERSION_TLSv1_2
Force TLSv1.2 (Added in 7.34.0)
CURLOPT_SSL_VERIFYPEER
Pass a long as parameter. By default, curl assumes a value of 1.
This option determines whether curl verifies the authenticity of the peer's certificate. A value of 1 means curl verifies; 0 (zero) means it doesn't.
When negotiating a SSL connection, the server sends a certificate indicating its identity. Curl verifies whether the certificate is authentic, i.e. that you can trust that the server is who the certificate says it is. This trust is based on a chain of digital signatures, rooted in certification authority (CA) certificates you supply. curl uses a default bundle of CA certificates (the path for that is determined at build time) and you can specify alternate certificates with the CURLOPT_CAINFO option or the CURLOPT_CAPATH option.
When CURLOPT_SSL_VERIFYPEER is nonzero, and the verification fails to prove that the certificate is authentic, the connection fails. When the option is zero, the peer certificate verification succeeds regardless.
Authenticating the certificate is not by itself very useful. You typically want to ensure that the server, as authentically identified by its certificate, is the server you mean to be talking to. Use CURLOPT_SSL_VERIFYHOST to control that. The check that the host name in the certificate is valid for the host name you're connecting to is done independently of the CURLOPT_SSL_VERIFYPEER option.
CURLOPT_CAINFO
Pass a char * to a zero terminated string naming a file holding one or more certificates to verify the peer with. This makes sense only when used in combination with the CURLOPT_SSL_VERIFYPEER option. If CURLOPT_SSL_VERIFYPEER is zero, CURLOPT_CAINFO need not even indicate an accessible file.
This option is by default set to the system path where libcurl's cacert bundle is assumed to be stored, as established at build time.
If curl is built against the NSS SSL library, the NSS PEM PKCS#11 module (libnsspem.so) needs to be available for this option to work properly.
CURLOPT_ISSUERCERT
Pass a char * to a zero terminated string naming a file holding a CA certificate in PEM format. If the option is set, an additional check against the peer certificate is performed to verify the issuer is indeed the one associated with the certificate provided by the option. This additional check is useful in multi-level PKI where one needs to enforce that the peer certificate is from a specific branch of the tree.
This option makes sense only when used in combination with the CURLOPT_SSL_VERIFYPEER option. Otherwise, the result of the check is not considered as failure.
A specific error code (CURLE_SSL_ISSUER_ERROR) is defined with the option, which is returned if the setup of the SSL/TLS session has failed due to a mismatch with the issuer of peer certificate (CURLOPT_SSL_VERIFYPEER has to be set too for the check to fail). (Added in 7.19.0)
CURLOPT_CAPATH
Pass a char * to a zero terminated string naming a directory holding multiple CA certificates to verify the peer with. If libcurl is built against OpenSSL, the certificate directory must be prepared using the openssl c_rehash utility. This makes sense only when used in combination with the CURLOPT_SSL_VERIFYPEER option. If CURLOPT_SSL_VERIFYPEER is zero, CURLOPT_CAPATH need not even indicate an accessible path. The CURLOPT_CAPATH function apparently does not work in Windows due to some limitation in openssl. This option is OpenSSL-specific and does nothing if libcurl is built to use GnuTLS. NSS-powered libcurl provides the option only for backward compatibility.
CURLOPT_CRLFILE
Pass a char * to a zero terminated string naming a file with the concatenation of CRL (in PEM format) to use in the certificate validation that occurs during the SSL exchange.
When curl is built to use NSS or GnuTLS, there is no way to influence the use of CRL passed to help in the verification process. When libcurl is built with OpenSSL support, X509_V_FLAG_CRL_CHECK and X509_V_FLAG_CRL_CHECK_ALL are both set, requiring CRL check against all the elements of the certificate chain if a CRL file is passed.
This option makes sense only when used in combination with the CURLOPT_SSL_VERIFYPEER option.
A specific error code (CURLE_SSL_CRL_BADFILE) is defined with the option. It is returned when the SSL exchange fails because the CRL file cannot be loaded. A failure in certificate verification due to a revocation information found in the CRL does not trigger this specific error. (Added in 7.19.0)
CURLOPT_SSL_VERIFYHOST
Pass a long as parameter.
This option determines whether libcurl verifies that the server cert is for the server it is known as.
When negotiating a SSL connection, the server sends a certificate indicating its identity.
When CURLOPT_SSL_VERIFYHOST is 2, that certificate must indicate that the server is the server to which you meant to connect, or the connection fails.
Curl considers the server the intended one when the Common Name field or a Subject Alternate Name field in the certificate matches the host name in the URL to which you told Curl to connect.
When the value is 1, curl_easy_setopt will return an error and the option value will not be changed. It was previously (in 7.28.0 and earlier) a debug option of some sorts, but it is no longer supported due to frequently leading to programmer mistakes.
When the value is 0, the connection succeeds regardless of the names in the certificate.
The default value for this option is 2.
This option controls checking the server's certificate's claimed identity. The server could be lying. To control lying, see CURLOPT_SSL_VERIFYPEER. If libcurl is built against NSS and CURLOPT_SSL_VERIFYPEER is zero, CURLOPT_SSL_VERIFYHOST is also set to zero and cannot be overridden.
CURLOPT_CERTINFO
Pass a long set to 1 to enable libcurl's certificate chain info gatherer. With this enabled, libcurl (if built with OpenSSL, NSS, GSKit or QsoSSL) will extract lots of information and data about the certificates in the certificate chain used in the SSL connection. This data may then be retrieved after a transfer using curl_easy_getinfo(3) and its option CURLINFO_CERTINFO. (Added in 7.19.1)
CURLOPT_RANDOM_FILE
Pass a char * to a zero terminated file name. The file will be used to read from to seed the random engine for SSL. The more random the specified file is, the more secure the SSL connection will become.
CURLOPT_EGDSOCKET
Pass a char * to the zero terminated path name to the Entropy Gathering Daemon socket. It will be used to seed the random engine for SSL.
CURLOPT_SSL_CIPHER_LIST
Pass a char *, pointing to a zero terminated string holding the list of ciphers to use for the SSL connection. The list must be syntactically correct, it consists of one or more cipher strings separated by colons. Commas or spaces are also acceptable separators but colons are normally used, !, - and + can be used as operators.
For OpenSSL and GnuTLS valid examples of cipher lists include 'RC4-SHA', ´SHA1+DES´, 'TLSv1' and 'DEFAULT'. The default list is normally set when you compile OpenSSL.
You'll find more details about cipher lists on this URL: http://www.openssl.org/docs/apps/ciphers.html
For NSS, valid examples of cipher lists include 'rsa_rc4_128_md5', ´rsa_aes_128_sha´, etc. With NSS you don't add/remove ciphers. If one uses this option then all known ciphers are disabled and only those passed in are enabled.
You'll find more details about the NSS cipher lists on this URL: http://git.fedorahosted.org/cgit/mod_nss.git/plain/docs/mod_nss.html#Directives
CURLOPT_SSL_SESSIONID_CACHE
Pass a long set to 0 to disable libcurl's use of SSL session-ID caching. Set this to 1 to enable it. By default all transfers are done using the cache. While nothing ever should get hurt by attempting to reuse SSL session-IDs, there seem to be broken SSL implementations in the wild that may require you to disable this in order for you to succeed. (Added in 7.16.0)
CURLOPT_SSL_OPTIONS
Pass a long with a bitmask to tell libcurl about specific SSL behaviors.
CURLSSLOPT_ALLOW_BEAST is the only supported bit and by setting this the user will tell libcurl to not attempt to use any workarounds for a security flaw in the SSL3 and TLS1.0 protocols. If this option isn't used or this bit is set to 0, the SSL layer libcurl uses may use a work-around for this flaw although it might cause interoperability problems with some (older) SSL implementations. WARNING: avoiding this work-around loosens the security, and by setting this option to 1 you ask for exactly that. (Added in 7.25.0)
CURLOPT_KRBLEVEL
Pass a char * as parameter. Set the kerberos security level for FTP; this also enables kerberos awareness. This is a string, 'clear', 'safe', 'confidential' or 'private'. If the string is set but doesn't match one of these, 'private' will be used. Set the string to NULL to disable kerberos support for FTP.
(This option was known as CURLOPT_KRB4LEVEL up to 7.16.3)
CURLOPT_GSSAPI_DELEGATION
Set the parameter to CURLGSSAPI_DELEGATION_FLAG to allow unconditional GSSAPI credential delegation. The delegation is disabled by default since 7.21.7. Set the parameter to CURLGSSAPI_DELEGATION_POLICY_FLAG to delegate only if the OK-AS-DELEGATE flag is set in the service ticket in case this feature is supported by the GSSAPI implementation and the definition of GSS_C_DELEG_POLICY_FLAG was available at compile-time. (Added in 7.22.0)
SSH OPTIONS
CURLOPT_SSH_AUTH_TYPES
Pass a long set to a bitmask consisting of one or more of CURLSSH_AUTH_PUBLICKEY, CURLSSH_AUTH_PASSWORD, CURLSSH_AUTH_HOST, CURLSSH_AUTH_KEYBOARD and CURLSSH_AUTH_AGENT. Set CURLSSH_AUTH_ANY to let libcurl pick a suitable one. Currently CURLSSH_AUTH_HOST has no effect. (Added in 7.16.1) If CURLSSH_AUTH_AGENT is used, libcurl attempts to connect to ssh-agent or pageant and let the agent attempt the authentication. (Added in 7.28.0)
CURLOPT_SSH_HOST_PUBLIC_KEY_MD5
Pass a char * pointing to a string containing 32 hexadecimal digits. The string should be the 128 bit MD5 checksum of the remote host's public key, and libcurl will reject the connection to the host unless the md5sums match. This option is only for SCP and SFTP transfers. (Added in 7.17.1)
CURLOPT_SSH_PUBLIC_KEYFILE
Pass a char * pointing to a file name for your public key. If not used, libcurl defaults to $HOME/.ssh/id_dsa.pub if the HOME environment variable is set, and just "id_dsa.pub" in the current directory if HOME is not set. (Added in 7.16.1) If an empty string is passed, libcurl will pass no public key to libssh2 which then tries to compute it from the private key, this is known to work when libssh2 1.4.0+ is linked against OpenSSL. (Added in 7.26.0)
CURLOPT_SSH_PRIVATE_KEYFILE
Pass a char * pointing to a file name for your private key. If not used, libcurl defaults to $HOME/.ssh/id_dsa if the HOME environment variable is set, and just "id_dsa" in the current directory if HOME is not set. If the file is password-protected, set the password with CURLOPT_KEYPASSWD. (Added in 7.16.1)
CURLOPT_SSH_KNOWNHOSTS
Pass a pointer to a zero terminated string holding the file name of the known_host file to use. The known_hosts file should use the OpenSSH file format as supported by libssh2. If this file is specified, libcurl will only accept connections with hosts that are known and present in that file, with a matching public key. Use CURLOPT_SSH_KEYFUNCTION to alter the default behavior on host and key (mis)matching. (Added in 7.19.6)
CURLOPT_SSH_KEYFUNCTION
Pass a pointer to a curl_sshkeycallback function. It gets called when the known_host matching has been done, to allow the application to act and decide for libcurl how to proceed. The callback will only be called if CURLOPT_SSH_KNOWNHOSTS is also set.
The curl_sshkeycallback function gets passed the CURL handle, the key from the known_hosts file, the key from the remote site, info from libcurl on the matching status and a custom pointer (set with CURLOPT_SSH_KEYDATA). It MUST return one of the following return codes to tell libcurl how to act:
CURLKHSTAT_FINE_ADD_TO_FILE
The host+key is accepted and libcurl will append it to the known_hosts file before continuing with the connection. This will also add the host+key combo to the known_host pool kept in memory if it wasn't already present there. The adding of data to the file is done by completely replacing the file with a new copy, so the permissions of the file must allow this.
CURLKHSTAT_FINE
The host+key is accepted libcurl will continue with the connection. This will also add the host+key combo to the known_host pool kept in memory if it wasn't already present there.
CURLKHSTAT_REJECT
The host+key is rejected. libcurl will deny the connection to continue and it will be closed.
CURLKHSTAT_DEFER
The host+key is rejected, but the SSH connection is asked to be kept alive. This feature could be used when the app wants to somehow return back and act on the host+key situation and then retry without needing the overhead of setting it up from scratch again.
(Added in 7.19.6)
CURLOPT_SSH_KEYDATA
Pass a void * as parameter. This pointer will be passed along verbatim to the callback set with CURLOPT_SSH_KEYFUNCTION. (Added in 7.19.6)
OTHER OPTIONS
CURLOPT_PRIVATE
Pass a void * as parameter, pointing to data that should be associated with this curl handle. The pointer can subsequently be retrieved using curl_easy_getinfo(3) with the CURLINFO_PRIVATE option. libcurl itself does nothing with this data. (Added in 7.10.3)
CURLOPT_SHARE
Pass a share handle as a parameter. The share handle must have been created by a previous call to curl_share_init(3). Setting this option, will make this curl handle use the data from the shared handle instead of keeping the data to itself. This enables several curl handles to share data. If the curl handles are used simultaneously in multiple threads, you MUST use the locking methods in the share handle. See curl_share_setopt(3) for details.
If you add a share that is set to share cookies, your easy handle will use that cookie cache and get the cookie engine enabled. If you unshare an object that was using cookies (or change to another object that doesn't share cookies), the easy handle will get its cookie engine disabled.
Data that the share object is not set to share will be dealt with the usual way, as if no share was used.
CURLOPT_NEW_FILE_PERMS
Pass a long as a parameter, containing the value of the permissions that will be assigned to newly created files on the remote server. The default value is 0644, but any valid value can be used. The only protocols that can use this are sftp://, scp://, and file://. (Added in 7.16.4)
CURLOPT_NEW_DIRECTORY_PERMS
Pass a long as a parameter, containing the value of the permissions that will be assigned to newly created directories on the remote server. The default value is 0755, but any valid value can be used. The only protocols that can use this are sftp://, scp://, and file://. (Added in 7.16.4)
TELNET OPTIONS
CURLOPT_TELNETOPTIONS
Provide a pointer to a curl_slist with variables to pass to the telnet negotiations. The variables should be in the format <option=value>. libcurl supports the options 'TTYPE', 'XDISPLOC' and 'NEW_ENV'. See the TELNET standard for details.
RETURN VALUE
CURLE_OK (zero) means that the option was set properly, non-zero means an error occurred as <curl/curl.h> defines. See the libcurl-errors(3) man page for the full list with descriptions.
If you try to set an option that libcurl doesn't know about, perhaps because the library is too old to support it or the option was removed in a recent version, this function will return CURLE_FAILED_INIT.
SEE ALSO
curl_easy_init (3) curl_easy_cleanup (3) curl_easy_reset (3)
This HTML page was made with roffit.
curl-7.35.0/docs/libcurl/libcurl-errors.3 0000644 0001750 0001750 00000032405 12262353672 015126 0000000 0000000 .\" **************************************************************************
.\" * _ _ ____ _
.\" * Project ___| | | | _ \| |
.\" * / __| | | | |_) | |
.\" * | (__| |_| | _ <| |___
.\" * \___|\___/|_| \_\_____|
.\" *
.\" * Copyright (C) 1998 - 2013, Daniel Stenberg, , et al.
.\" *
.\" * This software is licensed as described in the file COPYING, which
.\" * you should have received as part of this distribution. The terms
.\" * are also available at http://curl.haxx.se/docs/copyright.html.
.\" *
.\" * You may opt to use, copy, modify, merge, publish, distribute and/or sell
.\" * copies of the Software, and permit persons to whom the Software is
.\" * furnished to do so, under the terms of the COPYING file.
.\" *
.\" * This software is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY
.\" * KIND, either express or implied.
.\" *
.\" **************************************************************************
.\"
.TH libcurl-errors 3 "1 Jan 2010" "libcurl 7.20.0" "libcurl errors"
.SH NAME
libcurl-errors \- error codes in libcurl
.SH DESCRIPTION
This man page includes most, if not all, available error codes in libcurl.
Why they occur and possibly what you can do to fix the problem are also included.
.SH "CURLcode"
Almost all "easy" interface functions return a CURLcode error code. No matter
what, using the \fIcurl_easy_setopt(3)\fP option \fICURLOPT_ERRORBUFFER\fP is
a good idea as it will give you a human readable error string that may offer
more details about the cause of the error than just the error code.
\fIcurl_easy_strerror(3)\fP can be called to get an error string from a
given CURLcode number.
CURLcode is one of the following:
.IP "CURLE_OK (0)"
All fine. Proceed as usual.
.IP "CURLE_UNSUPPORTED_PROTOCOL (1)"
The URL you passed to libcurl used a protocol that this libcurl does not
support. The support might be a compile-time option that you didn't use, it
can be a misspelled protocol string or just a protocol libcurl has no code
for.
.IP "CURLE_FAILED_INIT (2)"
Very early initialization code failed. This is likely to be an internal error
or problem, or a resource problem where something fundamental couldn't get
done at init time.
.IP "CURLE_URL_MALFORMAT (3)"
The URL was not properly formatted.
.IP "CURLE_NOT_BUILT_IN (4)"
A requested feature, protocol or option was not found built-in in this libcurl
due to a build-time decision. This means that a feature or option was not
enabled or explicitly disabled when libcurl was built and in order to get it
to function you have to get a rebuilt libcurl.
.IP "CURLE_COULDNT_RESOLVE_PROXY (5)"
Couldn't resolve proxy. The given proxy host could not be resolved.
.IP "CURLE_COULDNT_RESOLVE_HOST (6)"
Couldn't resolve host. The given remote host was not resolved.
.IP "CURLE_COULDNT_CONNECT (7)"
Failed to connect() to host or proxy.
.IP "CURLE_FTP_WEIRD_SERVER_REPLY (8)"
After connecting to a FTP server, libcurl expects to get a certain reply
back. This error code implies that it got a strange or bad reply. The given
remote server is probably not an OK FTP server.
.IP "CURLE_REMOTE_ACCESS_DENIED (9)"
We were denied access to the resource given in the URL. For FTP, this occurs
while trying to change to the remote directory.
.IP "CURLE_FTP_ACCEPT_FAILED (10)"
While waiting for the server to connect back when an active FTP session is
used, an error code was sent over the control connection or similar.
.IP "CURLE_FTP_WEIRD_PASS_REPLY (11)"
After having sent the FTP password to the server, libcurl expects a proper
reply. This error code indicates that an unexpected code was returned.
.IP "CURLE_FTP_ACCEPT_TIMEOUT (12)"
During an active FTP session while waiting for the server to connect, the
\fICURLOPT_ACCEPTTIMOUT_MS\fP (or the internal default) timeout expired.
.IP "CURLE_FTP_WEIRD_PASV_REPLY (13)"
libcurl failed to get a sensible result back from the server as a response to
either a PASV or a EPSV command. The server is flawed.
.IP "CURLE_FTP_WEIRD_227_FORMAT (14)"
FTP servers return a 227-line as a response to a PASV command. If libcurl
fails to parse that line, this return code is passed back.
.IP "CURLE_FTP_CANT_GET_HOST (15)"
An internal failure to lookup the host used for the new connection.
.IP "CURLE_FTP_COULDNT_SET_TYPE (17)"
Received an error when trying to set the transfer mode to binary or ASCII.
.IP "CURLE_PARTIAL_FILE (18)"
A file transfer was shorter or larger than expected. This happens when the
server first reports an expected transfer size, and then delivers data that
doesn't match the previously given size.
.IP "CURLE_FTP_COULDNT_RETR_FILE (19)"
This was either a weird reply to a 'RETR' command or a zero byte transfer
complete.
.IP "CURLE_QUOTE_ERROR (21)"
When sending custom "QUOTE" commands to the remote server, one of the commands
returned an error code that was 400 or higher (for FTP) or otherwise
indicated unsuccessful completion of the command.
.IP "CURLE_HTTP_RETURNED_ERROR (22)"
This is returned if CURLOPT_FAILONERROR is set TRUE and the HTTP server
returns an error code that is >= 400.
.IP "CURLE_WRITE_ERROR (23)"
An error occurred when writing received data to a local file, or an error was
returned to libcurl from a write callback.
.IP "CURLE_UPLOAD_FAILED (25)"
Failed starting the upload. For FTP, the server typically denied the STOR
command. The error buffer usually contains the server's explanation for this.
.IP "CURLE_READ_ERROR (26)"
There was a problem reading a local file or an error returned by the read
callback.
.IP "CURLE_OUT_OF_MEMORY (27)"
A memory allocation request failed. This is serious badness and
things are severely screwed up if this ever occurs.
.IP "CURLE_OPERATION_TIMEDOUT (28)"
Operation timeout. The specified time-out period was reached according to the
conditions.
.IP "CURLE_FTP_PORT_FAILED (30)"
The FTP PORT command returned error. This mostly happens when you haven't
specified a good enough address for libcurl to use. See \fICURLOPT_FTPPORT\fP.
.IP "CURLE_FTP_COULDNT_USE_REST (31)"
The FTP REST command returned error. This should never happen if the server is
sane.
.IP "CURLE_RANGE_ERROR (33)"
The server does not support or accept range requests.
.IP "CURLE_HTTP_POST_ERROR (34)"
This is an odd error that mainly occurs due to internal confusion.
.IP "CURLE_SSL_CONNECT_ERROR (35)"
A problem occurred somewhere in the SSL/TLS handshake. You really want the
error buffer and read the message there as it pinpoints the problem slightly
more. Could be certificates (file formats, paths, permissions), passwords, and
others.
.IP "CURLE_BAD_DOWNLOAD_RESUME (36)"
The download could not be resumed because the specified offset was out of the
file boundary.
.IP "CURLE_FILE_COULDNT_READ_FILE (37)"
A file given with FILE:// couldn't be opened. Most likely because the file
path doesn't identify an existing file. Did you check file permissions?
.IP "CURLE_LDAP_CANNOT_BIND (38)"
LDAP cannot bind. LDAP bind operation failed.
.IP "CURLE_LDAP_SEARCH_FAILED (39)"
LDAP search failed.
.IP "CURLE_FUNCTION_NOT_FOUND (41)"
Function not found. A required zlib function was not found.
.IP "CURLE_ABORTED_BY_CALLBACK (42)"
Aborted by callback. A callback returned "abort" to libcurl.
.IP "CURLE_BAD_FUNCTION_ARGUMENT (43)"
Internal error. A function was called with a bad parameter.
.IP "CURLE_INTERFACE_FAILED (45)"
Interface error. A specified outgoing interface could not be used. Set which
interface to use for outgoing connections' source IP address with
CURLOPT_INTERFACE.
.IP "CURLE_TOO_MANY_REDIRECTS (47)"
Too many redirects. When following redirects, libcurl hit the maximum amount.
Set your limit with CURLOPT_MAXREDIRS.
.IP "CURLE_UNKNOWN_OPTION (48)"
An option passed to libcurl is not recognized/known. Refer to the appropriate
documentation. This is most likely a problem in the program that uses
libcurl. The error buffer might contain more specific information about which
exact option it concerns.
.IP "CURLE_TELNET_OPTION_SYNTAX (49)"
A telnet option string was Illegally formatted.
.IP "CURLE_PEER_FAILED_VERIFICATION (51)"
The remote server's SSL certificate or SSH md5 fingerprint was deemed not OK.
.IP "CURLE_GOT_NOTHING (52)"
Nothing was returned from the server, and under the circumstances, getting
nothing is considered an error.
.IP "CURLE_SSL_ENGINE_NOTFOUND (53)"
The specified crypto engine wasn't found.
.IP "CURLE_SSL_ENGINE_SETFAILED (54)"
Failed setting the selected SSL crypto engine as default!
.IP "CURLE_SEND_ERROR (55)"
Failed sending network data.
.IP "CURLE_RECV_ERROR (56)"
Failure with receiving network data.
.IP "CURLE_SSL_CERTPROBLEM (58)"
problem with the local client certificate.
.IP "CURLE_SSL_CIPHER (59)"
Couldn't use specified cipher.
.IP "CURLE_SSL_CACERT (60)"
Peer certificate cannot be authenticated with known CA certificates.
.IP "CURLE_BAD_CONTENT_ENCODING (61)"
Unrecognized transfer encoding.
.IP "CURLE_LDAP_INVALID_URL (62)"
Invalid LDAP URL.
.IP "CURLE_FILESIZE_EXCEEDED (63)"
Maximum file size exceeded.
.IP "CURLE_USE_SSL_FAILED (64)"
Requested FTP SSL level failed.
.IP "CURLE_SEND_FAIL_REWIND (65)"
When doing a send operation curl had to rewind the data to retransmit, but the
rewinding operation failed.
.IP "CURLE_SSL_ENGINE_INITFAILED (66)"
Initiating the SSL Engine failed.
.IP "CURLE_LOGIN_DENIED (67)"
The remote server denied curl to login (Added in 7.13.1)
.IP "CURLE_TFTP_NOTFOUND (68)"
File not found on TFTP server.
.IP "CURLE_TFTP_PERM (69)"
Permission problem on TFTP server.
.IP "CURLE_REMOTE_DISK_FULL (70)"
Out of disk space on the server.
.IP "CURLE_TFTP_ILLEGAL (71)"
Illegal TFTP operation.
.IP "CURLE_TFTP_UNKNOWNID (72)"
Unknown TFTP transfer ID.
.IP "CURLE_REMOTE_FILE_EXISTS (73)"
File already exists and will not be overwritten.
.IP "CURLE_TFTP_NOSUCHUSER (74)"
This error should never be returned by a properly functioning TFTP server.
.IP "CURLE_CONV_FAILED (75)"
Character conversion failed.
.IP "CURLE_CONV_REQD (76)"
Caller must register conversion callbacks.
.IP "CURLE_SSL_CACERT_BADFILE (77)"
Problem with reading the SSL CA cert (path? access rights?)
.IP "CURLE_REMOTE_FILE_NOT_FOUND (78)"
The resource referenced in the URL does not exist.
.IP "CURLE_SSH (79)"
An unspecified error occurred during the SSH session.
.IP "CURLE_SSL_SHUTDOWN_FAILED (80)"
Failed to shut down the SSL connection.
.IP "CURLE_AGAIN (81)"
Socket is not ready for send/recv wait till it's ready and try again. This
return code is only returned from \fIcurl_easy_recv(3)\fP and
\fIcurl_easy_send(3)\fP (Added in 7.18.2)
.IP "CURLE_SSL_CRL_BADFILE (82)"
Failed to load CRL file (Added in 7.19.0)
.IP "CURLE_SSL_ISSUER_ERROR (83)"
Issuer check failed (Added in 7.19.0)
.IP "CURLE_FTP_PRET_FAILED (84)"
The FTP server does not understand the PRET command at all or does not support
the given argument. Be careful when using \fICURLOPT_CUSTOMREQUEST\fP, a
custom LIST command will be sent with PRET CMD before PASV as well. (Added in
7.20.0)
.IP "CURLE_RTSP_CSEQ_ERROR (85)"
Mismatch of RTSP CSeq numbers.
.IP "CURLE_RTSP_SESSION_ERROR (86)"
Mismatch of RTSP Session Identifiers.
.IP "CURLE_FTP_BAD_FILE_LIST (87)"
Unable to parse FTP file list (during FTP wildcard downloading).
.IP "CURLE_CHUNK_FAILED (88)"
Chunk callback reported error.
.IP "CURLE_NO_CONNECTION_AVAILABLE (89)"
(For internal use only, will never be returned by libcurl) No connection
available, the session will be queued. (added in 7.30.0)
.IP "CURLE_OBSOLETE*"
These error codes will never be returned. They were used in an old libcurl
version and are currently unused.
.SH "CURLMcode"
This is the generic return code used by functions in the libcurl multi
interface. Also consider \fIcurl_multi_strerror(3)\fP.
.IP "CURLM_CALL_MULTI_PERFORM (-1)"
This is not really an error. It means you should call
\fIcurl_multi_perform(3)\fP again without doing select() or similar in
between. Before version 7.20.0 this could be returned by
\fIcurl_multi_perform(3)\fP, but in later versions this return code is never
used.
.IP "CURLM_OK (0)"
Things are fine.
.IP "CURLM_BAD_HANDLE (1)"
The passed-in handle is not a valid CURLM handle.
.IP "CURLM_BAD_EASY_HANDLE (2)"
An easy handle was not good/valid. It could mean that it isn't an easy handle
at all, or possibly that the handle already is in used by this or another
multi handle.
.IP "CURLM_OUT_OF_MEMORY (3)"
You are doomed.
.IP "CURLM_INTERNAL_ERROR (4)"
This can only be returned if libcurl bugs. Please report it to us!
.IP "CURLM_BAD_SOCKET (5)"
The passed-in socket is not a valid one that libcurl already knows about.
(Added in 7.15.4)
.IP "CURLM_UNKNOWN_OPTION (6)"
curl_multi_setopt() with unsupported option
(Added in 7.15.4)
.IP "CURLM_ADDED_ALREADY (7)"
An easy handle already added to a multi handle was attempted to get added a
second time. (Added in 7.32.1)
.SH "CURLSHcode"
The "share" interface will return a CURLSHcode to indicate when an error has
occurred. Also consider \fIcurl_share_strerror(3)\fP.
.IP "CURLSHE_OK (0)"
All fine. Proceed as usual.
.IP "CURLSHE_BAD_OPTION (1)"
An invalid option was passed to the function.
.IP "CURLSHE_IN_USE (2)"
The share object is currently in use.
.IP "CURLSHE_INVALID (3)"
An invalid share object was passed to the function.
.IP "CURLSHE_NOMEM (4)"
Not enough memory was available.
(Added in 7.12.0)
.IP "CURLSHE_NOT_BUILT_IN (5)"
The requested sharing could not be done because the library you use don't have
that particular feature enabled. (Added in 7.23.0)
curl-7.35.0/docs/libcurl/libcurl-easy.html 0000644 0001750 0001750 00000004432 12272124467 015353 0000000 0000000
libcurl man page
NAME
libcurl-easy - easy interface overview
DESCRIPTION
When using libcurl's "easy" interface you init your session and get a handle (often referred to as an "easy handle"), which you use as input to the easy interface functions you use. Use curl_easy_init(3) to get the handle.
You continue by setting all the options you want in the upcoming transfer, the most important among them is the URL itself (you can't transfer anything without a specified URL as you may have figured out yourself). You might want to set some callbacks as well that will be called from the library when data is available etc. curl_easy_setopt(3) is used for all this.
When all is setup, you tell libcurl to perform the transfer using curl_easy_perform(3). It will then do the entire operation and won't return until it is done (successfully or not).
After the transfer has been made, you can set new options and make another transfer, or if you're done, cleanup the session by calling curl_easy_cleanup(3). If you want persistent connections, you don't cleanup immediately, but instead run ahead and perform other transfers using the same easy handle.
This HTML page was made with roffit.
curl-7.35.0/docs/libcurl/curl_easy_setopt.pdf 0000644 0001750 0001750 00000442541 12272124470 016152 0000000 0000000 %PDF-1.4
%Çì¢
5 0 obj
<>
stream
xœ•YÛnG}×Wôb < ÄöôÜY, 'Š£ ±¼ °ÆpØ' Î0s1ÃØ_ÙÜS}™ E'XÈ0)N³«ºêÔ©Sß™ËséǼæû«×1{n¯\ö|õû•P™yÉ÷ìÍ
ú`µ½Òß,öXœú8yß” eÖž>¶²«Ý“ã?-XY¬éÁbé….wÝØù)«ú¬dW/þ½úájérO`÷ ÆSçiHöýˆ~¼rÞÝ,^Á_<!S >6WÎO·‹Õoo=—n̖£Ç.yøÂAö_†7 jÙ¶nX¦üb´ˆí²jSJ½íÄ% YŠˆ'Êîã¯ïîß?Þ=Ϋ%ʲó÷¢ÊË~#Ù?hç×ô ßý“–{:Ð7??ü˜×Xð2"ôˆ}¥ý¸fô›öÕ¸|ÍY“íe'›§Å×ËŸøùííã7wïWw÷ï¾äjÀ“P\ Ô“ƒD-ë[¹a]Í:Y–6±lWÓ†1÷éËÈJšr?tZ>8Çnû!wß©×*½*w~Àc׳ɓ»Œö@âE¨öðy”¸Â<ý,gRî%iXü6:§~²? Ûýé`ê\mQ=³n'Yv84õ¡)²Néïj ášÈ,½± ÄÊó°Ðú€ ¡¡jÅ<ŽÒÔ8}¢U¯‚GÂõôz¯|ª{–gË‘ågiƒújº5Š-ÆízÜзA Š”§©;Ÿ‹ºQˆ`Bmà!d5ìð›qƒˆû¾›Ž i—\”¬‘ªFŽE·£È…HFM² ý¥³:Ly ›Êm]–*Ì"á‘Ÿ&æã#`µ>±ì<~êáÛ‰MÀx_ ì]¦Ž¾:)V¹á< à¡;à«i<˜ œf/g—uc5©Œ¬¥u(5{›4 m ˺zVeüÒ8N移Îãã^ °n¢ÒW¹*ëC]Tt¦Ë»FHc ¾Ü4åa¤ÖjîsLû¸Ö•zý›Ì»©ÉöÞfÄ…óDŒÓE©j¡Þn?v_ð6ðçt×›1*èv yզБD¾Cî6Ý‚»^¬[ bs¤ Qí¶™ÿÉ
D™T€pcßùº–³™¥v૽i5@ñ¶/K ¬ek<,ªCß±Ï / #…NVö’VŸ° 7P(àE×Te¯&,•LX
Ј>K6©Ð”&c!zA¶)Oc¿Ò° êoØ!
Ó)%Ôær?QÙZ}õÁ¹7ô1¡¤cæ´¢¤€ª9HA±Ñ ðÚíòz¯èºÉªv+›– dƒ{pEoˆ¼hU~&”á'²E2vðP{7¨“ÌH/0„OQ±4ç!V #oÄ&JÖ„)«º£ éˆ#·´$¿Jž
[§ã”}ƒX¤–þFRÀÖ²;JY'¿fmÍŠ-;Ç… •&NVu¬í×ü½—x;ÆI|SlUl|×çÞ@xŽµú@.Áw8K$2=е2·ïÛÎö&ä~?: &¹†³‡F‘g©5 œվ•¡>g6é3ë,ÿDÊBñ)í~S|~p6r«c€’ÏúRì КSaÚ,üØ!ã£Ú “þì(hÃ2ð‰
!ŒÓ™ÍHÎc× ‚ÀdÖMd9ó
kØW¯€ ÕëPzÂ≶Ð<ðÜï‘ Ä™“ׇB7A
,öj²æô5~é[]sÊ ^ê&C*`µÎI½l´—Æ ÎPƒóƒCb
_7„O)÷c^‘ :]m•·¡6´Ï8°¡ÐÌ}!¾œæØ]4d[Õ5/QG¶h*@äö\RKBÓ—’ŽoÂ÷çÙF²Û¼)ÖrcÉÇðàFvYJZK'àyd¤#(×ÒÜ‘Ž/̓!“"ˆtˆÞH°
Q‘Aä Ðd"æ•{mB²’¦Âu®8»«ÚN·ITÛ 6•‰|Í /3 ejÀÈq’O‹”t„ :R tUeÃ࣑Ä`תãÏÓV/&á/Êl öUW r\÷ÑõÌ#Y¢P,p³’r#•Û{ gŽ{5“u
uç :uñH…†¨N4S£Ì¶©÷/äœpÁ þT?(¬UaÊqf#‘r£n^lÆ®FÔn›þ =¾°%9àYl¨Æyi¸‹x ƒðqûýÍi8cç—»ûv¯Æ¨Ç3ú˜Ì|4©aÑÇ_n ÞÜ?ªÉt|ŠÔ˜â|”ZÑŒº…!è¿góÄ}´)ÚC‰bÍFH‚,± lÖ5TKQQ{Ô?[×P8E×¢`d£>k¹™0c…Q5¿ÈažFzB‹[7
´“°pC>©î<°\µy_1Euu^—¨Çõ#·jåýó3q– šTS—)‰Ç€6«³n ‹²4^*g†ùfZZ“ü nW£.±·ÑÊI¤Ž '/±¼]/¼$‚ÚŒœ¦gCˆ2ß÷†öN.³ý U΀£Kû¶âlb WßÞ><Ìl@HB(…±ÌF`˜…èLðÁ65Š‹jjZœ¦®§Ä©Š½¢Ì+:L^ŽJæ•ŽU®é^\Ïú¢á×™8M‚Ú1Öp¿½ÔKÌL˜j°:YÙÊälL
è¢Y—ö?ïÓýÇ!ŠDŒ:E @múܪWA ûº%Í`=P(
3L‘Ù4Ò“œ@Þ*Wh¾ÂãÑ4¦ Ž;´2XÔ JÚ=Š^ˆƒs ýóëF UÉkñ Mî
b§86³K*wö{T®¦>4mž Ô
¶xûööÍ Ÿß~÷ó»oÔEÎœ€„ï
_5ò%@Šü0ÜÙ ¿¿½„Íì†Q•îLF»9LÓ5¨W„–*8Æ¢¼iÖ’4"œ‘–½û¢wè•ø‚éãëzsbà( bÄ þ©‰§‘¥…™î†>ÊZ¸Á_uC£k}ÈmOLtŸh½µð9Šey×+Az~ÿD#^` %Ãh7)Ò£ØõÍ“:$Ê´‘hõöºi“u{rÊâ“¡ŒÄ˜¡ØAøûiÈi¢· XÞ?-4yjš˜2Ds†0¼aºñÂ91Œ}f¤ˆé%ሷw÷ï ¾¹Pºûpûø8ˆ¬¼Ÿ&$™4=̶jYDÿwÛ.×èM—!Óîzjo™š¯1\£'›¦Ì%P!®ˆlê‹ IY~ƈÙW_æÔûC‰wåiº)ò7Ö¿Ã JÇuºãØ(<¤ƒÆÐ,„I ¹]Îà²ô1nxÁpÛüEÁL—e:*ŠrÎoÓ|¨ôEí#a‰/•`Åj”ƒŽè„$vH²^À5ã4¼„!‘ú˜*â?ÁP¢ÿ» âO5wÂd ŒˆnI¨ š¡¡Dˆ ¡„“¤ÞegóGœð`¬-ͽŸéBniEO…¹evß;ªEíi_”ÝR·”)25xjð#g<¹ŒÿÇ»·ï~ +àæÇÿý"¾„~`ž¢v=„Dµ6
Ý:ékÅáêv Dl>m§½Í ÆT—DV_b+0šÐxÝϦÍ_2@Kt¿rfÝXü…‘asà è8ÈÙXSŸ²¬/д]5èM[§k3G2 çÛ[-º¦*ˆüw4daifî‰= Æ:änÄÓÈ%Çý”‡ÃáV˜.–Ý®!&õYü¡]öˆQÇñ80ç˜\–µZRR>ÀQ¯U>ð¾+ö’”´½§]~T"}Øí'ª.[eæÔ\_í%<±€ ‹ZFÙ¤ãpý£ÊqÖõÐȈ‘T¾ÐøŒ2¹¬
Ó/C×užœ›ÍFOÒè]®ýk["Ônl†\[²èD AvM4!zÎ6Øâ‡)\üd¸ðÎ*æ=ê‹þôÒZÐG·««áç“$Àäendstream
endobj
6 0 obj
3007
endobj
14 0 obj
<>
stream
xœYívÔFý?OÑü²&ÇjÔ’Z þ“cŒIœöp²»cÃik4 ÅIHŒ÷xÞqow«õ1˜ÍžÝ
9,uWÕ[·ª”OÄ¡Œ8òW÷g²=¿ É]3sÈÝìÓŒ©‡¤û#Ù’ ¼É ,Ö3}†‘Ð%aìÑ(&‹íŒ¹ u8Y<Ì–V²«ó©h ?6i[Víµå]ÏIžÝÊsÛåuœÐz-ŠÈÉ“oÏo¿Í`Àö²XÍ »L_~¶&í&kÞÌÊ‚à¿pŒˆbe hÈmšävî ™µËò–ˆ©çÅQ…4häÒ†T¹HR:·¹ Ѐ1ë¤,šl•Ö€ŠÅ4ŽÜXBµÊŠ» M…Zb 8Eš]U•uKÚ’¤…¸ÍS…šÍ<gƒ>:m-’M]å®!//®H^–÷»ª9”á&›î††Y‚Ø
l벞€€¸ãˆûÒyé Þ!MvWˆ¼¡Ê¸ë“Åù̺JÛ^ÏÀSætDõ ù‘Æai¼¿<óvññâÍÕÙ/s75‚À:>W÷ ôŽc@ô 'Òá fF¶@8Å!¤G£‹7ÚÊåÛ`DD}æ².+ 1¤KI8ºT\r=FÃÚÔÕ¥aiXKÜT?dMJ2ÔFÑ’ÛÇñõ”F[?Ê$ÃÞX‘•h…ü‹ M™(¹q„hz¹®«l Ô´Ô]’—Mº"Y!o×®u‡z× ?Ôè)¯òíA“X2…'±I×s—ã®o;š Å@s® 䜺¾áûçT —fßzâ[u2®…¦tÅà4;ÑáÛHKmÝÝé’ï/dÐ(ŠLÉßöÆ V
yôU‰Y’œ%¸[Vi-$ %æ¶V ‡S 3
ù ~ è¢ßÀÑŽ#æÑwƒs]Ȭ$e]€„‰h¤˜
4gyLûb²:&»4<Í ê@õ; ·cƒ¾Iü <qÓJá߈ªJ‹CØ,ÚZÔ
ùJ¿J›¬N)9+ˆX2ÙÂÉ®‘Ò…›GÚå"5Ü]‹×ñ\5Î8²Þ/~ýx±8ýñ{âÅ (LGèÚ÷"†¿IEô>¬wE¢x©ûç^2©÷‡‹W ¿JÞ|õþâdqöæb¿D9ÍV„ ARBæÒZÈÊX§¢ÝAÀd‘ù£™ÀÀÒ®©¿Z¼%«r%Eµ„,/ÅJOQ¥ib„ëa„4Ì} ]£S\é u¦ã¡Ñaü
YÜËP¥k™¶º\í46`†L%f½V|Ý<‡3ÜzhŽÌH¤,˜{zÕ°~²{+h³Üýjqzyvõ»|&5¶Ÿ™—ÖºŽž?OUŠ/B’„&åö¹Ô÷ç¨òÍóìØ€±–´¢í—vZ¨.
5pŒ^^˹ƒè7^<!ä£2=Ç°§YJI†eÎ×åV%¥.Ë–¬ ôI[ÖØf&X£÷F# ~¶ß
p£ž¢^^ÞŸ^Iþ×Ç—€2Ю/éw»´QIØŠú^׎¤Fæ˜`v3íëÚšhÆ¢hˆ*ý2ŠjÒ½EÒ‚zeª'ÉFÔø;%Î-ÚÍÿn@1nôÌýŸUmʶü™þY¥w£X†¬Ùr ÄÛˆKûÅ b4JÖÒº<žûŽvää÷Ó9ýÛÛËÓ«+S˜¢‚ ŽGí‰u"&;Gž®1?#âѬÚÊù® ÐÝÝX\ ƒ2éd)_îpÀú¥ÂRÓ(=“wš¤OÎWÐ۴ΰ
` šŽ½1ÒÈûy3F .ÙQ?2Ç3í¡lL°3 ª´›üºÞztn'Ty›ŠBiqчÚï>2,7.æý– t£HOíþtÄ=n@Þ’‹Ac
sø¦ Aëú #ÿdõµ=©¡ÑþÂY¬ú"Ð÷÷Ä Ñv¤JÌ ¤âê›éÕx]à½( »`œHûET“¹é¥N“âáhÏP<,˜^¯©KaÿóØþ‡ó-¾™*÷ûnl•µ~ÖŤ@—ëow¯¾ýródIøþÕoÉxbàÑP
Ý|?÷Cäß mtüQ ·ÉÓ¦q4Ôž¬]î0<÷–Ób·UûQYLõe’ñö6?£#k!ZU/‘س ;=¹Æ.~,Œ¶‹ÒÓËï ™¬òÁ øÁÄR¤°˜`–G{#„¬‡a_•cÕôŠis:ºÙCBõTÓÑá¤k>¿ank:ÆÊÔŽŠñª ÔK²[Ôé¾ÿþ#˜È‘ï2à îùL¹¡ÊCê…ã¢<ºÂ]âùºw ¸˜ÍL»D’î¹0éÇÿö´È+½NNNÇÿÉÑUv—íÍ èR>ú,D)¤ÜéW|«ªQcOŒñŒ›{‘£´Þ;ÇGŠô£s·¹(î÷Îɯ†uî®Õæ¿°÷å |¤Aóœîáà äáP7KûÙ‡½ö8<Ú+OLA_ÍDR¨_¬8UeÊÕM~JÆjO¾õM@MÌßÉÁüm){v@0ã |8PM¸µ†ï>ø:O[\¼÷ Æ‘?Q]×óûÏDÓ®¦]—ííáÒÿjWWe“î×}â\^_ãß›küsƒ¥ô{E hì
Š–þ@†›DTi7¯S½ô*ÍÆæúú [óᨋÁ{µ·ª&½SË÷m9, Õ§çý¯sß›;_÷B#ÖÞòn6ó¤,š¶Æ‘®”„Úò+óþ§ìÎË#UxGá~ø O1›LK, jK}¬häw ýUࡃvÿ/C}2 µ0˜EX¢KH.šµgö[‹ý6&’7t+ â:L ô¤X›®üÑébö¿þ+r¿ endstream
endobj
15 0 obj
2758
endobj
19 0 obj
<>
stream
xœYÛrÛÈ}×WLùE Kœ`fpMžd[[ëµ|‰LW²‘R*ˆ Šˆ € €Ör¿Á îé™@i]v*¥ŠÄ\»OŸ>Ýø…\°ÿìç²:ùËUÊݟüv"ÌCf?–{±€þ°XŸÐ ÁRÉÒ\ñ,g‹êDHÅØ- N®ƒå¾ÝÞê¢;ÜvºovýM nfl[ÞáƒÙ\Æ!Ã4x[ÔûbËž =û÷âØ2‡-y ã®*a‹Ë“àåùåå‹ÙéÉ<äI(Ùby¢R®r•Â‘«“àüålñŸÉS•áCsæ™}øæ=> ̓œ§i"탋×ïß}ćÃ5ç*á*ÍS6Ò zùéêòý‡Åí?®^/.~úôî%NÂ9p›£$~ð‡Âo•ó,¦}Oâmt +Ø®)ë^·¬oàËz_/û²©Y¿)zVýr£;ø¢ÙºÙns«Pr©aĬõPÖ÷l×6}Ó vú¯t‹ÜÞ"Éy$EnïÙ•èÛÞïu°å¦hÙó]ßâ4!$3g3s7°-Cå.ò8"/ÛµðãŒÙ/u¥«»3öen E”M¹bÏ÷nWE_ÜÌþfýꡔň Úo±)»Á ÷ºïزØnõŠÝ zXѱ®Ç…±M«Íí2þˆa”ËÀz¸/kõR—OE)À'v;Ñš8ÊÈa2˳È>\õhB®d&ìôSõªCÞiÖ“-R0•’“ Â'Vçl>Fû±fmümŽLØX™¥äR:«E ¥[ÚúndÔˆKáœXvG“a{¨ q4;5f ÇÕ~Û—»m y(ûÍÑRs¥" ÇÒƒÞ¸ )®b…— ֕ϲÐÚî:8+gJÅ\‰<è *Œq¤àyæüBà(rävËê¦G+ÿ¡Û†AÔTe]€8»Òý¾åê}uñv¼;ô=Ų†Ù X_|6 NJ
«(º µhÎ^¯M ôÓòÜãJðP Â~Q5ûºg«r=“ŒÉ²`[@oÛTæ$vÀ®è:râ¡Ù· Üg¬ìOÍ¥%¸2IsÒ!]nÛ•÷5cQ3ݶá\ -ÚÙ˜L,dÌc‡I¾À
d¡<õms•E€á!V,ƒÀŽÅ]Óöf“¾-ê vмÇT°xî|‰ÄxA´x{qu5‹lð¿¿:w 0ÏÔÜœG"„€6eD>‘’ò'´dÊEÆÃ3bAG K° ŠáÆ ß~°ñ›ø“QÆ£ÌEÉù§Á0³2gÜ‘Èâã{Ø”Ë
îV3c’eÔÅ Ú²Š¥ã&x95Ÿñ
pͲ©kmI aÙT k L?j}lÄ$åîxC4ã)Nâ2\%¹c¬uƒhj‘ÙJ÷E¹í¬=áÖc¬=¯Hµ*C–V1¤)ž(\ ñ”ë Z÷u«¬¢«]˜%1xŽ ‹ Yð('ó鞬 )ÜZàݧËKü¼×„+“íÕ+½†.r8jæ e¹-à bbÇÉD—Z&㌿̱ævÙ)ÀÁ…z WL?½¾¼`ÏÙý45¢2Ãcæ® DE<Þ7‰¢Z ëˆWvo XòX: <_Œ3‹äó)..D(’iP%° p °®9†Ÿ
]üb~ž©4@Û E,ˆ+¡Ö.ÚF¤ˆEp¿¯40œÁ.Nóüêi J³Ïÿ÷ÊOFW&¼9ô£ ØDDÄ&"ý]±ü<Å †ƒeiÕ âß@¾ìš®+ïû 7`dYÛƒÙ :€§žw¿4CVñÙß?ó¾R = ŸÎØÝ Thž‡2Ø÷˜ Ú0Ë™ç„f‚r1ä ³æJwÖ*JkŠ§ø#èOªÆÁPG°†¨È… ·8$Ö«lPªûóÜG¤´Cºn_w {Ç!M
m`.s¿õ›fßAÒè(l«â÷²ÚW.6ks $‚Ô‘øÁ‘ó˜nÔ¬6>QZ!Ïα!Kì]‰OáyI
y”oØF+`F .#‡q§KŒ”ÌÜhñœrÖíÛóÚ´õñõ¿.ØM€K컽etŽL2bØJ$onfF" ³6ñXl8RxÐS£¯‰p*½Ù2³ÝŒÑž†›K.ÉBÅ6àilRŽ ÜlN©>• -¼83øóÅù«‹«i8¥ ³
¤Æˆª
(ÆÎlBì4¸ÔÙtL Soœ9 Âßï`Ô±`´[+*ã„Ÿ‹OžMÈ„çÖDD唪@âÏcAy¢8"úÀ]Æ‘%R¬¾!’ÃaMø„0ývÀª†rÐd.$àWi Ð;÷Ž˜ÇŠÙkA
‘¿^
JÞ(8<¦³ &U²ßë,²Pt<æk r!I¢§u\ŒŽ
X7Ã×E¦X¢Ì3Ê×%U™î˜p€SD>Hï…(úÈ°¬wûÞŸpÕÔV¿BôCIpTl•uÐïÇ, ¥B8±%raÑ%ï8Õ¾#Á ON)5ŸZ‰ÁŠáyHºý&X0 z:Ž ¨Û¥ÏÅ9âjœÔIê«Öï ª{_”PqðC
âAESÒƒ¢#ú¶„øx ·"“¸p¥KµRtTº8(S‰Ôõ«r©Ñ°ƒÝ]}:ÒqxÀÔ¯¿cUú5Ðàr AÇÑHU$6Ž(Ng¦¡%dÐbö@ˆŒº «V’½º¼48 u¶¨ÜÎÀ;vË·Ÿ>.¦®P ž8õµŠH(%?Í
¤‚/ž¿ÏÑPr†¾U`nãS‡”bbêkL »6†-(rôLÄÁï;Ý–º^BNh‹n£;ª ö‰° fÃŶkØ纼æ(¡£!NI½ö
“5[äû"âX^‡ ÅŽ‰±Iâ(Jä´™Arž
ý pŨY†
…Ç›)пR=)lçNØ”ÍÈþÔ‡uðêÜ•§VŽ%ƒ2X¸gbzRX!Š¾‡b b1¾DWŽhð™Ëqάû¶Yí—$“@ãñ”PAâÂCùvƒíÍpÚÜ ±3HßE¾ŽÚœý:¦[Œ›$tZßµ º#
ª)§¼N=ÌGMAȾ]ß´®þA‹èªiÆ[®5ŠÁKÛ®" cÞ¬ç(AI£SºâhÔi4=@ꃖ`¿+µZì ¸NÑ,ŽñµŽš´‡€6è.kÅ㟮€˜jGG~¶kõ Xbßêíá”g%‡šS¯áÂf>Ä „bLí ˜®ýHDKÄi Rl[~&!–#cºän£ßüäm.Iuµgû䕤Dß
q¯A@Þ°nˆœ˜ç¾ä—+€$|žÜï¶
Dë;ס®é™ýy«þ„ʸ™Yq ¡A(À‰·>ßÒmblÖ ålŠÁXج–)ëìrß=cC™Kò[‹8¡Õ]?y%a–†% µ[c¬ä¨ZŽR¶Æ\5•v-* ^1hªØ–¸ ³s±j|¼úÓMh({U2±O[·ç/Þ_ I)ï 'ᆉkÞ>dv-H¤T•^•sÛ\Ú^v= Ò* *ZÒ¡çuÖŽ_ù m 7‚Ôî}ÀäØ`:º ˆv!Õènt§‹W·/~½¥· VmPOß^MÞ†VfDƒ¤}sd¤Þ¡_dÞ3,›• ^cøȼ ÎW+C3¾$“= <ɵ¬çØ •
úÃ%7˜[ŽDŒ„iJ9Š_Æ9H
¦„x TÌDÆtÝŠ@áO‹“¿Ãßµ+M5endstream
endobj
20 0 obj
3141
endobj
24 0 obj
<>
stream
xœ¥YÛrÛ8}×W`òb*e!xŸ}r§Ö3ž8›ÐOñVŠ– ›ŠÔT´ú‡ùè= IÉÎlf·œŠm}9çtûwæsÁ|ú²ß—›Ù« {èf>{˜ý>ú!³ß–ö:Ç‚”>È×3óŽ`‰dIð4cùf&dÀýˆåûÙgo¹k«/ªè_:Õ7ÛþÎ îæ¬*ïéÁ|!#Ÿû~âýVÔ»¢bÏ®žÿ3ÿe†AÌòÕÌçQ hsï]ÛlXÂEÊýsÖ?*¶ÞÕ˾lj¶,jÖª~×ÖìÍíÇë/ //Þ¾»}ÿæˇyþ¯Ù[À¼åL†Oã7À¾ÞÅ-=ôéÀUÒ,µ>]²ýc¹|¤3j¶/+Zì:…#ŠUY?è=e”ñ$ŠÙBHm¥¶pMöeÇ–M]+c\ß°{µl6Šmi—gŸ”¢=^}¾ók’Â2{þèý‚qŠ^ïÂ
ÄYfׯ›®hamËVª/ʪãf}f×/dìs°… õ¯w ¹ crÀ¸µ\ˆaëŸ÷£ôba žÐ‹¸2¹hÕÀ+,—`»mÕ«îœ š ÛìºÞÅ…â¥o-}ɳ$ ÷Ñ™ãý»Xö¬Ø4»ºgÍšŠ¾À;E¯_\Uu_,¿Úh
²g!ƒ”aè"àí‹ÑVÁ£Ø—æ ßdfÝÃ*xªìMHï©+WªU+}Ê 5RrKÇdm×9¼pfX·#õ¥qÚÕZûIo³ÅÞmáÉ Û!gÞß^_kƒWM}¦ Ç#©ƒ%²;…6D}7\;ã"‹};lŽ»ÂƒØÜÔËJimC†“Q‰6ªØUxƒŽ'?P®F×3iŸP g=交ßÚø ÝEŽEp‘Ñ÷¹+å‹ãº‰‘Û¾pu¦‹d¤’'nãçO¤’Ð'†Ü¾‹¤¥‹œ] '/`ù ¨8©×¼¥ËNB»-ºŽ¾ë¤«Ô±¯áF“ „8XñÄ9¾Æ§Þ!À˯nÞ _YHBL[
0Gœ›‹Ç Ï‚t47‰S*:'ñìsfâ3ª‹Ì—‡\@ì
¬ª·»~0Y§*¥~À%mÈõÅs©šÉ ¤a lÕ²\ Xa<1TÃ=-Ïž$bÈÖ$
µOw”«]Oë[U lŠ™‹ù(ì=MÒÏ %¿ÐìüYªŸ›ŠÔù©ñ Ù]°osâî2ñŠª\é7ŠûjÈè;oY`)Bj® •tË@J :ßk&·w ŠÍ^žÝÍm*’Ë \_Û{Ïæ!“H¼–*ŽªÌ+E¢@)ÕH¸·Œßn?å:‰
mÓ4‡ Ó ?–C~äîQàeŒŽR %'D¨}h’M_ntµèyþò³—KØ^gV$¤G©º†}íò4I½}íP¸©€Ö¬.6êôJ"“\ÈSиzO2à™ÒÑS¦Ký Ixçý”‹0M—qAb‰Î |\ŽP#”ÃÔ• VZz,‘ð8Èêí…S&±$Å`J~1å¹I €gèNÚ
¦„çuå”ðÊ” A„m³Ú-Aze
9c²/…Š##ž"áÕÍ›üzšd›>7âî}(¦ém+[r?Mw”¢,FvÑ<¿)úå£2 ³nª
ñ͉0öö”éÛ¶é›þ°U?ÛÐ;m#“˜ûa8ÑNe£ÚvØýN_ÃW
ý—
ìX7ˆç½|¡Wêœ0šwuŽ‚Ç Àû$ÊœRyªÙeUªºßÞÍÿF z8
V”ð( OØ 5 ¨? S@lñ®¸÷¤±:HT<ÑZ†ŽaŸŒž¦Va¼ºY ‹ [ÕJ:#C ¡Õ¨«pB[´ÒÏgæ A;Ø–.A«y µe™×Üë c?ö¥…¾UñDŒë;U9{GŠ
µlQ1ÖY£aLº Öäý9kmrI“ÔØ393‘¢Ä)ƒ¼Ã„,kRçúbÒ Ã
DA»Š1î KÌ]…GuM
)L( œLSñûNu ¸\oJ»‰ ï‡éÀGI¡½= ÚõÈ fÏØò?šÕuð¹ ŸÝkHÈ4¶}Ô~ÔÕû{eýá6'5øá¨N¢‰?U}¹Ðj¢ØQ³Ò—ËB›O¹Ò@‘½>hÑçô,ñž!8 :õÚ !ò¶hpTžpˆÖ¦F…òù"ò}ïλ1h]¬V<̱íf0Þ»íÔü욧Yp‚Ÿ./ý ÙD< ô¡ÅÇö¤ŸÚf.,9|ƒ€‡±ê+\õtÈbH§ä/žîФì¬DÌ8,:b8øÇJ…Ñm®¯( ꆚ
S¸Æ6Ëðñ÷àõDibÍ ÑŸŠÍ³ðOQ˜Ö$Ï¡0á€3W³ Aõ9”_ø´0E´ø±ƒÍ2p¤÷°Û í(èaÙ,ûJ#ØÂT¼¶a(;SçZÚ}Gú5ýD<¡ñSþ‰€?§ä2HþÚ ™0«+ɸëa5íû±ÄѦíŽ4Éà¢"ϹÚQ$‰™$ÔJµS¦âò ¿ìj
ÓÖ
R#† Ò¤
OüAM“++}/Ý ±õ“bÓñ'µó”µeíiò„`‘ÓCƒéù°3üC%nü´Tm_ XÛ¦+
Ô¦®íƒa,]¯¥L刂JŽ¨ÇvÕ´ï¤qA—±nÚ½ù ̼‚ÊQ7‘8•ú§¹²cä–CM$©^Ñ8`ŠþÈðÄ1€yM߯G|5Í€³Íi£ôʵiÀÛùkån=³Á—ºP²H³#¸pјÀ…íýÿT—O‚Ý#¬@[q6£ö>Ž 04íסé§O]ETåWƒQ”ÙB8êiõbªÞü$ 4¡ efðG)ð‚Œ~Q™ )ŒÅr©¶¤À¨(Q™ùñ®aâZàóOSy‹ÌÁ½ŠâÖê}.ß¿ÕýžK"$ŠŒ{ ÄZTF¦Ø
9 $¡kÕHY]ç |¸{x ’ÿµØA÷ÕøOS@wt„‡©–¼ýŸ+# Yž9KG†®úûé|Ð ÆKY2Qj‘i?{FÆðöåæW3WêvKRTçL°Ó%ïæI€s³À»¸ºÆê¾±s\Ji[!ÍVµ…Ai£NM!¸Áí¤òÊŠÂ+Ÿœòæâ}N¿˜H"1ÆÞ?–•²óC@ÄzÀ6ì¦Ðe¸¹¸9ž¦«ö|ÂV)ÚÑÖzPò"êÍÎÎ ³÷•‚z]Üt%~1U ÕOÀM ¢»†rƒØ9íäç&Åjá$¼=Eh‡Ø–pé®Ü”ò-²(?Õ{ô–U™d§ˆ²‰Ê|‰ªçî²A: …jP;›…1Ü|ŽÖXŠ ”-rò#m¢wlU¶jIé
‡½xRŒç °~Òö˜á2JWȉ` $éÕȵ2ÍZ –¥Tã½]ìxôƒþ ÊâxÔ„»â@w\Ÿªu¥þ¨4ª·Ô4L”4GÇ
ƒ‰®£Gk9º;tSpÆ?U ÉM÷{V›§Ü·rAÊ£ï¨…å ‘‘ºéëwÇœ±Y4”i ÄM:Mü褦„qˆ‡¹ñ“Ig8éû3?ÇTÏ
:ÍÜ-Ó€ô™oòõOGŸúO*!¤@¡“.PýQA!ÎÎaô©]ã ñ\7^LW©oÓ=ÈŒF P}a:
DÙ¿¨¿ÉLH’^ ¿ˆ_¾“B@ tûæÅ C¯äÞé£Ë|ö|ýÆ"À,endstream
endobj
25 0 obj
2943
endobj
29 0 obj
<>
stream
xœÕY[oÛÈ}÷¯˜·¥Ö„3¼o Ç d›Ú®£-ºˆ ƒ¦¨XDjI*®úò£{¾¹‘”%;Ýf Šq,
g¾ëùÎþÆ|.˜OÌÏb}òê&a ÛŸ}<ùíD¨/™ùQ¬Ùë¤ôÁlq¢Ÿ,‘,Éžfl¶>2à~Äf' ¼bÛ¬îʼÝݵeWoº[/¸°Õòž¾˜LeäsßO¼¿äÕ6_±ƒ«'ÿ˜ý|‚¦AÌfs˜…½[ïjÓ-ëŠåóy9gËŠ%\¤ÜÇòÙ?OhéTÄ<¥>xç¿Ü¼»ºžÝ½¿:ÿóDf<Ëdâჟ~¹<Ÿ½½ºT'L]œ¨g%=é]ç´›OŸf<à*>< µsmËr¶©—UW6¬«ñËb[ʬî!ïØ:²Å/%[Ô«U=‘÷E{Ëê#Û4uWw»Mùƒ2àÕMf¢*ÉÃTŸöÁÃönß[ïóDø^½œ³ï‹Õ²¬ºÍ©¶^¦’³\E²‹Oä@(pª/ù‘JŽWvw
ùb~ª~Òz²‡m¶
='dƒĸím궼üImÈe¤bÕW<‹"k2= éo7WÖ©b³8õ…Ù\ÐFø(F6ÌgùvÕ"ZË–mò&_—Wü²Pœ½]0üÔ T–%r)‘ã´Ï“X'Æ¥ácÙµ¬ÈW+ÔÈýÎÖ Ë*cH‹
‘PE · ª“Ö³û‰ôu®¶ »/uSªŠºªÊ¢_ÈÙŒ>ÅÿîóâÓwÊÝ “\XG•©¯n„o55ßÚL!ÖY½ÊF3y"²Loák§òfB."á}Ü®‘z¶œãßåSaåD„º´ÿ• 3û¢ðÒnYlWy£½¦>ð%ymëo`£9*Ce$uuÏì×ë‹»·×ç¿ Û+DÄS“F‘¨ú¢“aÉRåÊuWÀç™÷¹ 4˜L³44_¬v¬hʼCÞLđΖaÇvY%º]"{¡iÀ…-&kòTz r•òÁSŽœMß;?¿¸ž™ XwbÆÂ6L¨ëJ9ôÓìš=>”Õ°¨Ò UÃÀ»8ê KLæZ*Üí†=.»v}u3‰üÔ¼Ù«‹ë÷c·hrVæ
:ºaŸ•1"F
ëLÙ´ä¿Á6êšÔU½>æ´eŸX§ ÕþcÙ”•®JÉU€aìÐm\вïϼm{€šª [ß·®l@ Luø<ÌT|~Úv[´ÉgZ‚Hd&ø>Í´•ÆV/\/®ó k·›MÝ 0©ËLá¶hxT1Ù¡ë»*ŸÞã 2¬·iDð–Í˶h–›©FDmÆ8KM¤¨ˆj KÊ Æ’Ó〠=5yL“ï €Íëªd u2eÛ–iu.h_ [ø lÏÏû¨J ·YP-aiIÇsvƒÒh*3»YB4²9òo½~;”±L…
,%’¶ûwÙÔ0xÑÔk2P×Ið¨o"@3@/¶Éd(Ûv[eÛZ+0Êí .烡V£û>RÄ’mÕ”E=îmŒÜ$H_èm2D¡ÉïWÀ¦©]iÆps_öÎ#ß”j¦É› ŽÇÈïÐN êbE(7Âr‘*ZÕèàîá›HW¡ ÅÅÝùÕ/ïÞ\Îðóòòâ|F–DúäᘣAÐòqb‚ s‰‰„òp¤˜¼àëÐá?xKly õÓ;šcRO賞ÜH$þôH^¨…Œ£ß
Ý”~·C™ÜÔ(2óŽ8ÑÙ»›‹³7“@µQèýjý¿x³‡‰3[ÇÞ©ö”oØaô JÓãòx`]IÝcÛ\"—¥ ¢h¾ÃÁ…=§ØU·Thœå+4ý|g!a¡ôv„ÄöUUµ]W®78N—§Ýu˜žÙeÄÿ ƨƒ24ÀdJ ›²Æ‡R'ýlÆÎF}1c,ë[ñ¯azˆXRä”o@¡mÕÕ[Ê1A$6°s•_ša aHÖ t„¡êS Ð+¡j¶å ØÓ¡À•ÂÅ .¦é8 ˜j–íÍßåæú/ˆ¡)°}ÚèÝG=JÏú‹¹ÌÜîðcI¹‰„TÜ“‡¶Ÿ¥^¾Ú–4ežIÖƒ˜gRö.ê~Ñܔ՜3«0èøù‹-Öõ3Ô ®± ¢5¨$ƒ«ë‹KŠÃEïý9_Ô —?XtÄ T±mðãúAˆ¡ ÁŠ8 f¥öaÈSHˆF4 òÔÔ·Ó.OeÔ
MÿSÖvͶÐúD‚€7ì{úW³™9q&µQ&¨çýjJq¬£5Ãr¨H[O ÕÉÙ µFšÍéÁ.T"г=¸¬Ú ¥k®Ük <¹6ƒ36÷Ê LýÀÙ÷© š)ORß·ö‘H]d×°ċÄ)¬§IzLŒ$ÜGaÙ3K‘áfeÞhÙ
¸ú5‚u ‰
=[ 5žõ‰aç!‚A¡$JŠ½y W”?ì‹€˜Ù`Æ?/`0_-ݦó¥¡iJ?½½f÷y;Ö"œ
é®ÀL¢ãt}P9~d:ù÷à¦lëÕ版Œbð—Àj‹’÷ÉN€HıÓ檃@
}ŸæoÛîy𲇲Möëi`ÒÞê!DHa ÜLµhQâÒëz¾\ì”7Öl„¸)[âqµ1qí'%Ý·hûPoWŽß©Ë
Í0eèÜÙ÷Jõ!$uqÔ~| $a=¥I³»×¤8Îö™PNØû:P#fA"êÂB™‰É]¶ èî²¥ÙMÂDå™SìwˆS|Ì&7 Õ<€Þ"ÀÑÀ¢‘Ð<\’¤'L="KœU£m¨_ííú‘¹"\c;…´×ZAÊ?°¥ÕÓÐr٣ʧz0Ðmìö›C˜&ö ñ‰««´ð‰B#—ÕŒ #ŒŽDÎõn¯Ìž\Ü@µûq‡ðU•"?s¨¢UÁOW¡+4š]yFy)ú÷D{®-eˆAç¿t±BFìk/Ó¿Áàþ›fµ.c‡”Wß{CØEò³0 Àîi¥8.s:€_6;4 LôŠz^ÚŠØ8/Œ+t}*üxï‚náæ~…à¢;">™F¾ïÍ ´WŠNÞ—ùDöÿyYüÁ°ÖÁ]’±gin5ÒJ³áôGÚÜË×ËÕnx # Ñ|ëõéû…}«|ðh+kÉôG˘N™;ƒªhú£bwE½"6¤•Šì•æÁ;süå.Í×7šáZéƒFµTÿ9éê ýz–Þú(=]nßLùØ~&qÚ !†sËh¡zSVŽQÄàò2s”ÂX"bbÀMÂìëÔ`ÕÌl½ÞJãÛþÒ×Ü+Ðl©J !Vo>¤ #‹îÝAN(Ÿ$ ß»a^;ҡߧâ³u5ºRÅ7½2~:»$0ÁÀN’Ð{—gQg|%HÈËã+ˆ•}a|É8ùÆ—À iD|`|ÙFÓó T¢×ú£ùZÇ¿n~A°ô38 émÇ S#; cÏD(öFØï¼ÇƒV’òͱA=‰(Uc,„VöÛŒa•¯ß;þ&M «*ÄÏ£ýõÊ ð¨ ÐôîzD ]ÌNþŠ?ÿÙT®endstream
endobj
30 0 obj
2988
endobj
34 0 obj
<>
stream
xœíXÛ’ÛD}÷WÌ2µžÌŒîð”ˆ
„l0N•¥¶Æ²¼‘4Ž.kœoà£éž‹${CÿJßþh™Zˆú¦…Œñpþpðµw7OišÜ÷T±!_fe‘×Ýþ‚lT¿.s²)áLYN¾×Ê9j焈)‹# B®xX?øÉc*|ÆO\5‡õg‡÷x8Çx¤‰w¸žm q±ê;O`]éëV»¢ ±ºÍ»–d²,ó
Y ]¤IQ·].7DmI 4Ê5D<ßh+8$ŒCA—hk½»i¸x@™o½`"‡¢Ûa˜8¿ëCïæ"4.È’’ŸvE™ÄDÒ uT`ÔƒÆFv’€ ë ãØ5²n·yÓ€ýÞQ–ðÆyt7çt&¼¼97—G}… ži‚ ãÅŠ队º`€ :K¼zC6}ƒ··@+XŒ'i4BŸŠˆ {Òa?†œLB÷"o
µiìw'»ý˜ÆQ¸E‡qw@CaéïíòšÔªÛ-t ü0¦!Öâ¤
DÓþ
¡LÖ£ÙúZî3êBå 6'á…›cž¦ö¥:L·qšFîÕ[¯î Á ;RÈ
©ñe[*Æ֪M|È 2·Í3Uo(žûhÉ™ã.SièÙD3« Á,ÀF~ßMÊ;e aÒÄ;» IhÂÝÞ{ÅbßJÔ3—¾~¬}fuñy¼ãÃƧ!M¬ÑÖˆrÎxäî»(€öòÞëô?½¶ž`S?tKUGdÖÚ–GÒ·§YºžóÔÐ`-Z›8QL#ÿ”ª†Ý{Ùâ~Y*`ŶQ•Jî÷e‘I#œJ?Âà¬eöNG#ðà‚[ùõèT¹!;5ÿüŽ…0€€¸Å§ª©¼ÅÀ3ËáÐ>Û×Î3ÇŽ¹DBÆíd;¥òÈ©ûj
¯A¤ÖÇ.oﳈC˜Ó±žX}¾G#.’!ÉC–±DÒ;ÎoìÌÀÄ‘÷û>Ï4 Ï:<)çb<76j_—
„µÀ2UŒ.¡M)£QÂ\®œ{âÌi-––Ù#1
B[[œõ`·Õ Ì͉NPîsãç‰_S&“8±†aZE¶Æ#Ž4 ˜)›yšd¡¶ö Ærf.)úâž@†ó!?n¼1H'p÷û) &xˆØÇÎÛ·Þ 3ZŒ È=‹}t; -¾oDÓÓdÄøÄXcNÃî‡÷ÑZD >ÜèDîMý®6º M”•C
²Œ<ÔúZk ™”&‰ïÝöÓ;}fP‘„“†s²ìÁ.›ÿgI>”LTJx÷!o¹ölm‚‚iåJÁ öy1 j ½íq"\åQÀ]µè ꎡ_äS(¤C"j?µÄ;%˜&JÁ…¶Ò·->äÆÐ&¯$„š]Ï).Ô¨m
Š d\èäØMå9ò
®bFɊʶ‡÷ °Ý*ÕJ5¹vB zEüDZZúœ?š¶»€½[XŒeC94œæ-pèI‹ÌØ‚Þ6²"Ußvxk¤Áì@î ¿Ã.Ö0´ÔPÀ[æ]ßÔXÕ%ô õBë”7uý!ð|x'õE{æh&KCja ½VMg²pª¼¾ô\[Ý.¤XB/o ?¹Z®.ŸÝ<ùåæéã—/ŸØfÂ7}†®‹¶N> Ã#0<Ž5ßf]D#H1ÕDÈnN£tìl…k
_lÉX7X¯×m':U ¦ëܳÌò ÎÐkp Ú0Á¶{{Û¸aW !Z˜è] Mg˜ÃXÒ×%~ %ºÍ±U¶Qû¦Ýˆøé¼gwª±"@9ûbŠ¸)Ä«/ÇnåÕô+¾˜Àö+g3 ‡êä;ð Ïl¢3üSÉw“–.X€\$ò1ƒRݺƒNКè,\&J"Äv øAsä‚fÿüürùâÕó«aü3 ù¼éï?6øé Xm·7Ý8ü<»7 ˆ¹¸<qÑ/†Š59¥ÿÈÉvúûèà°‡©ïaêû O}Á f§’Ïžúb>@}®GÏ\±F½¡ÿô¬'øß{˜à›aOÀkøÔÉÀ'RôÉðíÓ#›!‚ˆ"€#=%Â'¦¹‡9îaŽ{˜ã 渇9îaŽûÍq :Þ0ÆÁ1>
stream
xœÕYÛr¤F}×WÔ>™v¨YŠ;Þ'G³–w.ZM;ìˆÑ†-á¡¡è‘åoðGïÉʪZíËëÆDŒ$.UY™'OžL> ϕ£úg±;ûûM" †3O<œ}>“ê¦Ð?Šøç¤ta³=ãw¤H|‘d›fb³;“~àz‘Ø<}tŠCßÜUùð|7Tc· oàv%šúžn¬Ö~乞—8oóö7âäÓ«ÿn¾?Ãë ›faa§.›ª†A Ú†~ ¸š*Ê¿õppÞ+‡fÒMC»A’© »ª Éô8 ñÐ*ìOºqf,õ]?PxuÈ£÷yñIEí© P‘Än(Ôwzá?/ ´ÿ^ÿðîÛÍÕûwŒ]^¾˜#%DTô2Ž»±~’Îff}˜]VÛ•¤µ³ÔÉÍ(¾¬ü1˜7‡Jt[œÙç}¾«È—õÀÁóÕ8´Ñ8´Ã¾*êß `æH°ùéõåÍÕ»×ï_©G¦ðÇ®Ÿü…ð{® gÙÿ# /þ« ˆýÔäì±ÛlØñRÂk.£Ž·““QÏdü"è6ÞR3ŒÿJ¼}iî1ÏÂ.6ô"h•ˆ¿å “¦†3A…beâ¸ÌONS ƒ½ÂßÂf6™º‘ô ¹·Ž=jêçiä3•ÿQáÔÈ—ýîòâÕåÍÜÓ€
Ò =é&¡ÏnY‚¯Ã ˱ËG q¶íš¦ã(d‘óT·„¥±Ÿ÷Õ7ºd¦l$p99¶©îF»öƒpšlîêR|½ {µ‚”pp¨1àœ³ PQÃ,µErëyYúq.ô í®ÚÝŸc}ªPI’ñú‡¡êË|ÌoWÿPûønB‹,P™J×îr34Îwã‹Ð¸I ËC¶ÿ•.uA¢ªYäšX\ÌP’6WÏ뢯67YQÍ6溊6^3à GâØÎ9ED§É’N3%ÊÎíªV|§)„ÓŒOANah ošè2È^Ë[Uá¨Sy†³QªîW’ÐéùpœvªÒW!›¼(ª=qË°ïÚ¡–"×µ#œi\WúS¸%%‡$ÞRˆ¤Œ·Õ~±¡‘ƧJÚc{Á¡sí9ÊšQ'“€‹Žôø ^
sÆÜ —ˆµ2‘: 5j"Õ@æ}•ïÖO}=’/Í\åç
œö< Yf§34Ôs€ù6d ½„óa·ý䊬š•Är©n5Ž}Vú ˜4}錜ÓÂ[_ÿ¤•\DÛÑ ˜)¹í\rfÄú@÷³¢ÕƒR¡0&é«n‹æPR\˜ûôXCXv²"_ŸLèMgíïŒÈ
ÿëû®|f_§’} ¸é4‡tý•.>M#U«é÷ÌËœ±˜Á”Ž–XjÝ=Ù}‹Í›Ÿ[çÛñæ5l¦q}.>e
ýgÛ’€+/ ý‹¥]×>hýŽÊà —?>g&„ûáÉû阆jhlG¡"üóÅ[g€%p?½ìü²W!hbVéé9—Dlžä;¯;U e”è:N*–Ø&ÿBë'蛈y²k׊ÞÔàÌH ÷I'xÅ T> ´êõb ,õ )i#Á I-T9*3ªèv»œhSi3ÚQLª=|r„|¬.gs/Ñ$}ë "›¡ŸÚNͶ©Ò=Ñðèh¶&Aµ2‹Ž$ÙR\gLS^0 RFÇ3Êãñdé¬7º]-âȽë J~>
stream
xœµXÛrÛF}çWÌ›A9ÁÌàºûäØòF‰"ye(I•µÅ¡„h ÔÅßàÞd¥v«R*‰.3}9}úô|!>eÄÇ óYlg?\Æ䦟ùäföeÆÔMb>Š-ù1ƒ¼mfú FbNâTÐ$%ÙvƸ ~H²ûÙ'¯ØwõJæý㪗C»®=q='uµÆó%}êû±÷kÞìóš<ûôü?ÙÏ3‘%üf%¬ùöêòìâC¶zwòã<¥i0á]ýëýÕùÛìôâ\=¾wÀ‚B½Ç8¾ç}ÈçÙŸà\Mi‚Ýp•Ó 5¦ö=ÉÉ®šAvdháŸÍ¾)†ªmÈp›d›Åìá I6m]·s ÀîaàÝWÍ
ÙuíÐ;ùeÁ—©‰O|Ûý ìòûéÙ9¿ÀåPp¹bÆã Š)¶îfë¹ð}(‘À“_•—*<‚çÇ È––ݶjr0`AÖsŽxNCo?@XëZgWŠ
¬ #kIäœamñØ{È‹¡~$íFÙ¥…)Úº´>ér#T– µ%6„Aq ,„¿g³%£\'þÍ É篴õ,¤Q”šZ2VTu¾®¥+v•U(i zy½—½æœ¥}sÉ"š¸²8=±ÊNþÈT$ !~S£êÀÁˆx —
€ ¬éêÍ'ëþtòæÝÉåêôü¥Åoe^©^{mg¾ë Àò˺úìèEBoPï€Ù`]jÀ[mM`Ú¶¤“ AH“#£Ã ?žÞf¬œ«”B!²`Ä]vª
–4;ºÎTmM‹µz‰…w/;mîÅN6°%§÷Ü$a½í€ö}UC·ºÑ";ŽŸFT ±¹|@9Dçâ»à]®Ábˆ ¨š»z÷ƒËE ÍÛ·8ð¦Ý>¯«ác›¯{Õ.Ê †Ž•¼Ä¾ù½2 ’ògË௥u$§¼ºÉEj—~Î& o° ´l
©r¯F½Ä4±ö#ßíêªÈ58Z²mËj£¥ÜZZO@)ÞUÀj(üZ¨-ÈÎ+e(§)® Œî& Àß´õÅ,v7ê£ #íEï¸2 øìR„Ãqê…vü Hä[i8 ä)ÌÑõ£ÖÌTšâF†Í2vä˜ïFó@YóÀÒ*‚“Êi¬ÃOLãÄZixÍn«B2Ú+êZ=‹È§Q’x›\}ýÈkä(Þ…€vä»Q²k•gzÚ ´4`Ô0ÈíNõd ó㺮ú[ ň•ž½Xì«iÁ‚ õ-H4p®4M½Cñ‹žv8ØŸÊ UÛ^¦¢1:_F7I¼rP³Úqä(û1g[Pû“ŒbóŠ õ>È`ÔãÉDv4
º
€d@i¥Bš¶w†U
faÞqÜõ&;Pköê!ð G£™@; á±[é6ã1¶€Q×–ûBI+´9¨ 7dyØZ¨ž!õL„b&~†¿TJ€Ä,‡!ÝÀ@Î+%`´K!§¾;†¸/FŸòx”K‰Æ¹LO T«èew§úe–ÚøÈÎ*¥D72ƒ–½¹(§Án´ÞwÈ ä»F% ZF
kâM d ±£X*ŒjŸjs“@×ÓT0ÖÈ„ÍT€3‘â|i¼o§ÞÇ£èkp¢=Pôec»þîyF´Xm¥mÍš[Xœª*ݘ9¦mf-ÙO…xä3KÒ0dëgz© Tže-žj>u¡iÜÉzά7m³ :5¡@+H£QÚÉ’|Ûî¡X€¶?7* eÒP°ÑÝãP7ÒŽõ†ðŒ®©@' ”ØÃŒÌA#õL
Ϩx¾ŸÊekxÛ *¨ Šg/ÿòáùhc‘ê2È·»Z.@Šj,Mk"·Ò…sYÇ7Ír÷=Šq„5Yç—å-Õqó²ÄßÊ þwî( ZT©ÉiÏŒ/Àn騲¡5
I¤…ì†êtRÙ/µ>|öþ²‡î #¹ÚŠAæyìBäk1ñ ‚«e¾,ªuè§Z²¥``(&gZÌvÀ•‹¼‡q H? ¡¿ú H Œ©{=LÔ&½ Å;ÎÕêˆTq¹ÁÝçCíáy%idùÇ Ïgªî ÄX™‹b¢4t}-Öw¹ÑM¯CÕ÷M5,µ¯IJƒ‘z¼ÐÖR:>xÚRì\Ëü€FìÅ¡| )-o›2çZµ¿O •öÀËŽW
·m£‡YÆ…;«äf›‡alÉà—=‘Óé¨ObÅ}§OâxfÂCeÝÊÎl†o'
œãdóW‘ÎXÕž>¬»P¦¯”ÔÇ9Î4:>
stream
xœYÛrÛF}×WLy·ÊdJ c÷ì“#K%ŽåˆtR[ö "‡"Ö À í7ø£÷ô\p¡d+»å¤X0ƒéîÓ§O7þ` Ì£öwµ;yu ³ÛæÄc·'œ}“ÙŸÕŽý°À ]XlNÌÁbÉâÔçIÊ»!}î…lqòq²:ÔÅReÍòQmµo?MüOSVä7tc:“¡Ç=/žü’•‡¬`O>=ý×â§?b3ü¿Xcϳ×o¯Þ/–gWï~[^\O½‡?¹úeùaq‘,/>¼;[\^½Ó g0 gYé „¤ &ï³éâß°WSž„° WñœŸÐ¡'MÃ2¶¯ò²U5k+ü±9”«6¯JÖn³–í²vµU
þPlSEE»‰$áÜÐí•ê½îóò–íëªÚ‡½úžž|uZïE÷“85k´Y«jº·}š¬¶Y;۷µ~ƒLxœ$öéSº4óáô Mœež9þ µlY¡ÊÛvûiúóR2°ÅÛ“‘9á¦(ØR+Åàr¼æï÷Å™^Våìõüìò’틬ÝTõ®aUYô!1<·¨VLßAeh÷Lû=ƒýò"»)”>+Ë7c·Ï|ßçiØÁ ¿|su>׈:¿ž;sûRA[ð ø<ŒÝKîõÛ á
Mð0ò,&ͺ·‹¢@˜’ z žW_Jµf÷[Uº„`÷´1õCÙ?mS)kØÍ”ÌO=99äEËÙï´¶Ýæ
Ë
WY£N5î_] ÏÙ+#I iíµIy§ê)m&£ˆ©Êe^nª>áz›“‹(µ ÷,ª‹‚Õª=Ô¥~ö õœv"Û¨ w»É[†\æÚn§aPgIä ÈÖY›ân`DU:ïëÇ¢óë„|¡º…7É%2öFGÙxÖ†A½Äó’.OC“¤ºIùµ>Ѷ ™ÇöYí¨€V‡f…4æa—öô5¥)g¯
óG ûšF6š¸ueÄæçF½Ç£H
ã8–SŠRÏa°ñ½{Õ°$}œä–•LÕuUƒä„Gl¦Ê¥†ªÕš[Îq½øî¨Ì/¦"¡*ŸL®–ïοc î‰ š\]ÿ<.øƒJ'cÞ’¬\«€”ÜïØú±¨àÆ$ HTà}ÓTàOLf¨0‰ Š úJòûÕ°ŠE=÷ 9ªÆqŒðFî±c„Pjúés<°D
Z¸Qí½R&]¶UÓj/¯I…Àúj‰'t Å ÷SÙïa¨¥ª?wk4m£x$Òw‡X˜2NTVáOÕp*aqWÃ
b¡$òf¤U+«j·Ã¡/jf$‡Îü E¤QeûªV+• åäc:‘<|L(ë1 Ä=|~UÝvÆ$<žèǹÐTbŸ v _àB É\¡û&º KÖ‚òÈ]ˆ hí4Pÿ*+
Cdǘ‰ 6ž'iÚ¬Ã̦®vŒÎžÅŽ:z[™@aÆÂÔ¾"íâÂ.õs¡¤²7 8eþ8äHo£Ã Ù|þ–ä0Q¢Ã×Ìíd ÍÑ.7ì¡:~@E'‹o²Õç¡2÷áíÛS̺*_šPÆ´QNû]0Ûfà…@FÂA;C @ÓcóÓ¾ÄÀ‡¾ãJ§“âšå½TËãé•:bäIêTÞänÓ'ƒÀQâN†qß0Q&1Pã´cLû†5A®” |:‹p$™úä’ _O… rÔ»ßΗ—ZmÝk:ôÀO Õ²j ¥ iK'÷´’$¤ÉÈwˆˆ|ÙYzªé¢¬z·oi˜Å Â, ¥²jZhî¼ÙªõéS¨ z:üzñ§Çž’—¶ ]ŸÿúÆ–*r@ñ@änëÀ»DÒû Ð4 :5ÒU_Å ÞœÏÏË«‹åWóÛ F£E©yž õ” (tÔxQõ!‡Žê%k=V{ ]”È.¥&êϯx#Ûí Ó3Î Eô
—#ÚãÓ‡ú– /.øe&¼ ~a†ìµ;hÑÝcؘð¤KâÉÝjˆà´«C '¤.™ õV›©&5?œd‡¢íK»J……@¥‰†‚Gy]By5$5L#-(/M&÷Í÷ÆÓAÀ}\ǤߴY+‡r(Ø?¿J’0‰z?Ò_ßáâêZÓñtÓ\B„“øs–˜µ3áŠþÀ‹ÿ¬þƒ›„èüw¸ JƸ¿Aî*•aï#… צ§r¤Î×Ô°SÛN¦ä†N °Úí°ž ÈË'ûëq0Q_×¹ÕÐ2&
¨])‰zkÖ<4ÚYØË€è*8äõ¸°]¾[œ#I]®…ȵÿo #zqú¿Ïa>õxê2®Î|öÊÏŽKú© $³¦Sà°Ê×fþB;PãÉùÍŒmк]éç”Ù?ÊÚÝœbû.%h{0|MRÇ6Þ*ûh觼«XÃÆ
}PÇ©ƒÆ
ìÖ9êVµX€Àw)‹„k*ÜÆ/ê ¨]#R´½š}¬¸
YŽX rC&O¨®|xNßëú Šf¡²Ñ¾$Ô;ü¯í{=̪Ðáœ/Íônñ^ GÎ_u •¡Åù;»)ªÕg'k…;ºím³¼lƬ
ßDqøÊ»z=€çLËz¯
6s’UqX»Ñ@Š K±/5êíÍC«¨>gÅp‡þƒû‰K½û™õ37z¯‘0
µ›¶ 5d`²ü¶4ï1LADÿ–ƒ.:L\úÞ–tŒ¯„)ÌÑY”é˜ê“®¶YY*¨Á5X3ÿB.1X¢!”´Ö SPâ-îÚ
ªçq¡Ÿ5<#iB‹kððôåI`t?õ;¼ŸĠa‘½¼TÊ4˜Ýô˜ðº"¶-ÄõÅ™ôÑÌ•IžãÖTxHAáö¥xí(;hLXƒziþÛVfjÏ(P¼Y÷ƒdªEÜ‘.ðÜ!ÓÍ4oÔ6WŒ$ăçšØ64
z’%:Ü…z<Š8”$<`ýtMD¯dz ®´¢6ý´¢ÑYÕ1Š©‰fš>¹t¶¼ T:¤æqórÄs¤*ì§qvªCù_5Šh{§QW’T£óHO~‹œê6Mîi&¨'Es¤œ±¥ik•íì,
›l³Î6Ý—Ï£À¤€ýtñqB -ó÷šëJO²JœSª ÔÂ7xoAE=»Ëí‹ÍzÔèˆ#)Ú|§¨4¾fÍVŸör3XA7,“cûAZx<Ìøœú dßš mæê³þ,r éi|‚Z&º¯%ÍHjøiW5ÓÈ4´‡›Í*¹°VÍ ‚J
úTH sE¾?”peS•èu €¢òµKzíPŠjo BC†½×ô~«5Œ4ˆš¾ gqr¿›iízˆ BKtv~ùÛùQòJtøI×Ä¡ÕTƒðØÐ@.YGÛÙ)28
ú¤áÒ~ÓÍ$:BjêÑë5z4O
~½±%Ÿ5æh?ꪣ´_ÆHö»½N]õ ‡TKåSF¿·ÕÁ0Òª+ˆ“× FËïôÊüØGbø]òË:4gqß‹{Ò ·ÝÚ¡Zƒ½Ú†Å
€à´‹ùLÃ÷~'Â÷£OB²ûŒ¥J=¡Ó,àC[ ‡ÏG²(Ôe—ÕŸi‰9‘v"ÕÙ/öË‚Dˆû ¸›ÚèæœÃÙ¯×(ÄzÒ!¸KóDÉbN:źCø( løܨ ' ÍCƒnCÒ\k^ÄO#õ×UY‚ßôB $»)]:_œüŠÿ1—" endstream
endobj
50 0 obj
3181
endobj
54 0 obj
<>
stream
xœÕYÛrÛF}×WLå%`Jc÷}“m)QâH^šÎÖ®´¥É‘ˆ˜ ´Jû
ùè==\(ʲ³O[¾É¸ÌôtŸ>}ºñó¹`>ý²ÿ.6G¯¦ »oŽ|vôÇ‘Ð7™ýg±a¯gx ¥ ³»#óŽ`‰dIð4c³Í‘÷#6{8ºö»z}«òæñ¶Qmµmo¼àfÂÖÅœnLNdäsßO¼_ór—¯ÙÁ§'ÿžý|ÄìfK¬ùæãôÝÕûÙíÅåìlúîìt"‚ˆû"ò~;{« >\6[ ‘rÂB¼‡‹RQÞéŒNf¿ã€xä$•\YÊN„¤Ç“D?6[
Ãïv¥Ø®Qõ2os¶Š²U5.æ-{(Ök6Wl›7Z²¶¢U_M…o½#EÈ£@˜ýÙí‡ l›FfOÁ³$0l6ˆ[…ÿÜíÊE[T¥‰â&o+eâ|W×ÕD",™/½‡¢¼gÛºj«öq«þfƒ“¹è&@]ôûIí°u…—º n¼EU6-ûL6f OâØ:¥*–&˜ ` õÁü¡ó²¹SõmQÞÑQÔÊçI›SUÇX3Óv´ûaÛÖ&U¸¤‡G!Ji÷;.:7¥Ç‡Ý‚®qv>6qªZ;þ äŽ\.òziˆÙmîÀ¾ÔN»´µ?”ë*_ ›øÃc]UºÇ —“Õ4* ®•6º3 h”Ú#e•Ò.¤ëÓ+ú‹¯Ìs.!q¥~&äÒnÀ°™Ád yè"Õ[Ó» Éh\f‰GÇO¦)eÒþ~̦ BçûcÆÆ™‘¨Oµœ98Ð<î6¥›ÂAeL®oíîÙ Â1:P2ÚçΦӑI½³bÔ[_ÄÙ –‰#ƒHX2P`Õ†ix²Õ?”»Í ×E“¦ö‰C±ä¢áMÓª %û Ü=dì‚uíñ <1gàݵ–ÆÔ˜g]HÉD‡u„±¬Z檫4kÂ)ƒê:,A¢ÓµW¬óùZ ÷g^å
ûª+P¸Ô ôòõNq«^H’Ô%±7U0£Ü‹k”‚å ¬{óöê—1žÔjû†Ly,L¹Gª
CÁC!_¬éõc»"¿Ã;–êxÏ<@ Y&ú"}ÈÄ¿\¼ß3j È,ŽàI?v6>V;ö «!ÌëŠ=¢éËËQÅPšOÅVûhZÔðµÁ«ê'¬ƒNö] ´Œ&Œ´<½x·ÏÕÀ :lû¶ÐÁˆVAº¢FFAÊ2œ¡©6Š¡6 «n¢Hiê)ôª“©´RjùƤ*óiD P““Š²\
2
ž¦é+Ñé+“k«³Ë·M[!‘ãð/k+òg¿¤ „(ì²h¤©n¼ÏGœðq]÷ɲ!5 ê%JSS¸p´UcÖ2 ;õ%Ⴘ4nçÍX¼0+R(Ýç
ša,O€ÂëV-q©þý(ÓAx®<AêÂ÷4ÓãˆG®ÀIÔ©(:œéèšd}c¦w©”u™J–at0“:#Ï'™o “ÐFiâŠi3‰ OU&e!÷Ó¬_ÉðG—H¦p‹Nþ £lÔ€AŽ£ž–¯J(SO]ï ±Ÿu
ùióÙEá§×~1çИe†°Ç)7lCwe[íncl–Kןæ&IšX)ˆF=s¹A;FSí6ÊЩàCÞ ü©%}žØ Ÿ ©’rй¼\î+2dó³øv«Á›{-ˆ€ŽNÜ‹üÆ*¢¾ó•ÜuLÏ)"lùê=£;سQï5ýù%Ô¼ ‘@ûš¿ µñßЫú2ùŸzÕH¼Ä§qÈcW¬h^0bS*«)Ü’ˆÞ ]ƒúÆR뾈®â&f +(Ÿ§z¤–tToiTC ]!è8#ˆi2µ=¤ˆãC=d˜jUä’:ê4”ñt9‘ñï¾|±›l<1D†´ë‰K´æ¢ç~mßå•}6“ò€…(±~˜9)
ÈdÎBÒÙO¤#\ñ%¯X µ¬?PbàÚÐM%®i«¼|R@N’)žE}½ EIJ D‡
Æ·Ö‹/0Ç“Á%È#~¹v$!~ꇗÿ_µã™`ŽYÔöpÃPB-ˆ´O Q×>û#Îþîû õ$‰³Ø¶ ²0 †ìl:@iû²íjÊ=˜öa_=Å÷1Ö/Rµ ^|=1?ÞÇóó³é·UtqÔGÐP£©zD»nt§Ç†¸”öîÀ†Óî\ä¬ÒÞä¤Ðì®vdTë’úV›"Õ4ù=£(i —Ò s£&ÓÈ £ì$8½ÑF/§ÖÛ» i8¬úû®1ÛÖšûÀóKT±ºÚ<Ñ ˆlÀ×æ“ :|Ю~8Ô_†¨Hb~h8N§†~n$"ýàò€«´‡6d*Ò~Zcs[È&cáC1¦êIÍnÖëÎжGWÓÛÿ:cóâ ô‡è-²Ä;]·«jw¿‚/hDd¦¶ÄPA÷KŒòI’¾7qÿþ˜-[VÊÌ%–ªYÔÙZ">Û±UÉf ¬ ˆ’ÈÍMAøzŽUëy«Wá`'íŽ"uCµu(<‚!–
ú ½Š ÕÀªÆµ9Ʊ4fñã ‹ƒ\^5‘$ZÐ!E‚¸+ϳšÐX?
- 9YÜÖyg]è“^Œp'ÁÍ44CüýNzxÿ¬ìTÈl(º¨y»M¿3N’Ê.u|ß~I P|ÒC÷HHO)3j AV‹"oa å…å.½Í°HÈŒ‡®$¿8,"..úBY1já»R©%r°Õ“V+—òbm§ßK´G•æs[Jb*†i¯»üÐÎ9ä ûlÖHOÕ¬Z¹j•O„ù¦à}.¨6ÖL™ŠJlúä£R˜ Q")H\:G×yõÁ»êDg#X›³Ó´‡Úì}bˆiÔ>a†r´ÜmÍב¨KéH§Hëçj÷µG;6ÊÐS“£»´Ó÷ü~Bn”q
W—ägò]ΖőÞ2!\SŽºIoyfç}lÔXà‰”°çÀê
ÅogÓ×W ÎÆ–gÚþàùž)•ŒôöìµþdAÈøøãs Ñ÷ÇAàÐ FÒ¸@A!…J™k Ð\rwÿªó¤îÊÖãŒ^@´‘Ü}z>öÓA% ûìDÄh¦š >?¡f°WMæ«à`j+iNw‰Ÿ‡h
úÑ+XOú¼¨“î
}ílvôwüú/ï9Aendstream
endobj
55 0 obj
2947
endobj
59 0 obj
<>
stream
xœ•XksÛºý®_É—Rw,à›þ–ÛSß:‘*Óítì; ˜„D6|(|X×ý
ýÑÝ>’´3 OF
,vçœÝÕ7Â(' ÿ†Ï¤\]îrlWŒ WßV\½$ÃGR’_cXâƒø°Ò{8 lD
#—+n;”y$>¯ž¬¤oŠ)Ú÷—Vvõ©{¶œç5)òW|±ÞØ £ŒÖgQõ¢ ?]½þ=þml ŸÄéÊÊÄé$+ºŽÿ¹²]߯
} ³î¤Ë$šoDóNÒZ¶¤ª;ÒÈ®o*"*"›¦nÖZ9ÔÁ=ÉŠ{6õ|¢@Û šeø"¤¾ë³hxV_ñ¨Ï<ó´?à³²±pxv
)Å»:7ø~¹õФϨëÃfNùàõÛ`[ ‹xæ Œ,Pk¤¬HW÷I&SJ®ë!ªâÔ†¬Ž±}—FaH6ÜV›ÕƤ®:Yu-ÉqaÝJ’ˆV¶*}˜Ñ ÒP9þéq¿ÝÅ/ñõÍ~¿p ×i£ÖNŒ®F4ôL,®ãªãÚ–r{wC~!¢%'шRv²ÁMpÄÈ<øC¾h<ÅÎièº|²éhÉ¢0$ ‚è²¼%m×HQBdm'EJê¾»0wÇÊ2¼þ¨Þá³AÍ™c<´±’#vän~n€ˆÔû?\¸tv÷ó uQÞî DÏÃg  zú1uÏÖW 4ã"ÒÒˆ=e0ð mèŽ4^ ´št38@¹Ï±—Ð-ŠªüÿÆâ÷>Ç4x vûD¿0°=4u©Veæz/€ùCKÓF¨ÎÄ $§íO(K ŠÏìš7ÄNH=ÛÜ?
ðÍËã—‡ÇÝn»o®_vûÅEØ >¸ P ºÉvJk"4Þó§í½f¼ã« b6€Â:Øçõ¬xCÍÃiŠÒG g_g
+fC×+Ä•7Ö›ê’>¦Y~7 ¸.õ&¼OcëI6¨{zn]ö @uóýDáPîŒØSKhyóÿe]6Cg_©Þ¸ÕÝß{ÝØW¨Ë*)yl¿÷ °èQß™ê³:ñ
šó[>?´°;}É«C=ÍàÓÑ â¡eõC]5
r ´¼
Ϻ A×2àV5Á xuf†¶Œ²™m=#÷yÞ0µ4²ƒåøfà‰¡£ñ¾A\üHà1‚ølÙ@ÑbYÇöMÀ<©Ë}šªpxßÊZb (#Ï2äÃãÔ<yܶD¥,°RA· _±5€–+Õ¼u§¾§e ]PÉ{ìÛqrRKþ%4.Cáè8S£ Ô-Âù|^«_\\nQ©‘ÞJ“º¼œwaÃ&D ¦ùnÓ<ã
Ü)x0üd3ƯàÊÙçܾâWW6û W¨6Ù ¨ÿ#ü
î²yႪæŒ:Á›ÿØâL¹µ× èR‚qÇg7ñê¯ð÷ ³p¨endstream
endobj
60 0 obj
2377
endobj
64 0 obj
<>
stream
xœ˜ÛnÜ8†ïû)x7ê›-’¢Þ›É.&¬7«¹JYb»µÐ¡#±Óñ;ä¡·ŠIݶ{&À b˜bU±ø×WÅ|&!e$Ä?îß²]m?$äq\…äqõyÅÌ"qÿ”-ùg ¤ø‹|·²{I8I2AÓŒäíŠqACIòÓêcP ‡æUŒOŒJ÷ý)ŸÖ¤© pa½á2¤a˜ï‹îX4äů׿翮ÀÁFÄ$¯V!MyjßiR¤hÆž úq¬ EtOƃ*ëÝÑ{EŽ£HW´ê† Šq<3še!A?T¤èð¯±/¨à ÉË2*’N¾‚§qÿ2 ŒSÎ ŒÐ‘`Áñpè*ÒôuG èºï ¨ü
šô;4°á1£2“døÙnãÇ ÷ý¨oÈ® L¸»¾iú5h–Ê(8ÕÝ#9 ½î˾oÈi¯:Rö]§JKxV5|Y3¨a…&ƒú|¬EŠ#Øët]Ð9$Hþn•ÿø1Øk}¸Ýn1;·s^xœb^~:NëXTe²(¾í¡Q´ì[cMì®Y€Åë»ë¶¸ØÎŒÌÅüÃeñ§¶¨›ëvýAü vÆöò8ßo'M¼Ñpkj„ô“¾kžÈÝû7÷ë Vœ& •”¦4NCæ$vs?K,¤Iœe^bœYsÿ¾Fªÿ}Ÿß“Ñ
îU¹/*j„e-¬EDyâ}¾íqãaÎoÄB'í`hç€ ¤1
»Ðƒ¬ê¤Šë`/™—6Æ™È8áUŽ’ÏÌ Z#BR<ôGm< ~üíÃ;2>uºøJ ¥Å¨@ÙŠ|xû/.ÒèaÆMî~Îß’j(v¢«w¶ óË*†=äb,ÙàµnÂꯚ|
ÞT*xK¨`4ü´¦x+¦(e¡‰ÅC„&É@#° ]›ìzmó
«Þ’Œœê¦AؘÓUjgå“¥Aql´5ö §ª@îK —´+‰)¤V
mÝ¡aÀãá–¤¡ÁÈ/y~ïn7µ·'”óØ:øÜð5ORÊ lguk¨ÈX:iÏ ®œ¼ÑáÙ¹4æQ„Þ¼ÕNHe⵬&éd .à÷ªKJòpÒ&Ç NYÀÇTŠÌs*Ëe"‘4ŠÒ3p ‘Œ{'b£ot–nóiï¤ÏÍ‹L(þdÒ ìDôb;Kæíý‚ù”Ôå|ϽoõÖ¸‚ c8Ù ˜ð¸Ž¯¤óˆM4•Ù‚·i˜†[²Ü€ÖŒˆ ßî9©‡øéš çAe¦- ¤p7
ÛGÑÁ/è%Ò<³\ ß2M®¸¶´±íÅâœ8õ
¨·ƒ¢6Î&È„ó‰&__Yð$£rœY‡èÌY,®„ŒPz.`WÛ*MIÂAÏ0‡Ð€Ø} ¸¢(]©ÖÍ…Ú·Š\x ({¼Œ hGž‚_”•GŒ œ9!r‹ÝÃr,ˆ÷ºUM¶
”MNú•mxM="plb*NÎUÜ*ÀÛ£”†óÀÃçA©n?dntÛÈ„ÆÒ§:ðؘg;„€Å÷³ä†2fÖPãDÃÑ\Ê7;„
Jµ¾.ZÀBœêÐsZ€,c3…ì7pŸ»¡oáRa©`¼)u?·5‘ØÙƒ@žu »L"¦ÚÅ.&Ré£Sæ…ÒÔ3”JOŸqXÒ'ôðaf(5äê)@ïÐu*JîvSö±kµµÖ‹`Ì9X
´ 'UئL¥ñbê€éÝ&6®ª/-Î1†Ê_ëR~ Ç–ôYÝðê¦Ú-gLŠy´ ªvS‹ãMYuóñpvzï‰y…)
cï‰æË4rÁçãqÅÊÞ ’Om§Ô®íÀ+ ó:Ìtýq(MŽvb숪(÷ E8q
F¾J TWÙ ÐD>‘gJ€Èm÷á1tKßCÇr™£TLƒbß}{<f’²°ä@ûøû{ŽGþ£Ò¶b¡CtPÚÊÙ™v™{ŠÀ°"]Óž;Ì_õ¸!“©¯t¯ÛÆGaSyÈÃYl84uYkȪö¿ZÿY ¸*Mfà¸7é"0੆;?ŽÛ—âÁÉ0!/ÊaJÔdÀôãÖiç£ÁÄ ˜ùbÆp óPr‰ÝoôEìvfûNìr¨ M]Ù¿Ä.‡éË㸆]‰ß@}Cƒ §)°Ë%§¼è²Ól æ³4ñôsÁâ¡\Ï”%óˆç Ä ùa»rd”§®é‹j¼ÀöR‰V?ÊÌ%JMÄËÅ%F¯¸0dÚÂË«]~µÀ¦Æüà˜ŸÐþüB‰ºÛ<S˜4K.h+Ÿ³vÔ‹9€Å‹YüÏÏ1ßuì'+Û
ƒù ±è™óê ¶ƒ*ªV™‡—;Œ»5´¶¼5ÔÂâ㩲®r5{[§“Wbp“´á%ß“Ð^ËþwTlóì¿…TÎâ:84V!|_g¿¾üª ¨yÈìFóHŸvpüÝÏùê?ðçÿðÙ‹¡endstream
endobj
65 0 obj
1939
endobj
69 0 obj
<>
stream
xœµXiÛFý®_ÑßL-F-vóN``xO`dz¶²ñÂ^”D¸ËC&©9þƒt^õÁC£Ig< É®ãÕ«WÕúÌ\.˜KÿÌßM9[¾‹ØM;sÙÍìóL¨—ÌüÙ”ì»>ˆéÁj7Óg‹$‹Ç [•3!=îlu7ûèlŽMñk–¶¿¶YW ºOŽ÷iΊ|M/æ ¸Üu#çMZ Ó‚ýzþïÕ38Xx![mas× ¾Y.mÖ|sHÛönžð$‘aìÔÍöïxÉ3uD¸ #„‡C’'¤ˆœû´<ßÔå²ÉÒm™ñî¾c ¶Úç-k²®É³ùê?³ð@
›™$üP›qnÕË€û — —qûæeÛÑKW’\H!çB9ßgläôK‘±]S—¬ÛkŸ2Šx,#¶R¤ŸÑXˆt4 ÷½$¶÷ƒCÁãÐ7/\îG
§.3¶Í›lÓÕÍÃÄRðÐ÷c‰ÿ2Xòy"Æ–B]É}V±”QHU
«iµe}A%”>¡Ï€a{È6ù—l{Át$£´$ÝÇ(6Ý>¯n JÚí±¼Ò %.—nhAry˜ø*W ˆˆº=þkÔÉ&+Ò.ŸT3öyä‰M.1Go3¦jçqAO¨ê\†¾©ŸS
‹C‘×£c}Ãu_¬Þˆ'¹Û;)^ôù>*Q %Šû >:|5÷ÔßM µ‚V“’ Ž±v†ÀDr.å/C@1w}ëiȪÈÚž ¬©ën”Õ
Ku=B”5Ž†zÂS§‡oլɨ6g,uÄ,zž®Ûº8v¦Šå±íØ:ê¿~`‡&;dÕ–è‘*6Ï×”ÃÝlõ·NºÝæ]^W’]Ý Â‚šm‘¶ð_+WëlN<߹ɫŠ Ö;fĺÒ'Ûdö«GÄñ©àüYÅñ¸ôüIŸø<$s¿§8‚{AÞ£3Š3)f/9šÒVO÷úPœ;*NQßÜD9 …ô%!HæOhDŽFmù.1³Áyÿfu=6šÔ;:¬Õ¤W}ÊèkÄúù˜¡îÆC«‚Ý×x¢DÕÚ¬Ž
…XËc•oR*;»Ë»=<Vpo†2Í †hoñ: xzEJcÕs—hÙ÷ÜÕ\B3\ôÜ®z=ŽzÊó ¶J
u˼ë€"·w¯(XŠçå¡£\J]Ü÷dÝ ñ]ÑwóXx\+\䨨740ëò€Ž±S‰.Üèü”ˆÀ «<š> zrÔÁÒÓÓƒ0çìUT)
ç‚ûÂJ;^ú+¸kl7lªªý0üSƒ”é« h”c£ubw,Šö ƒ"á¶Fq+C34ˆGà°––ꯢŠ P.Šog¬â)Iá²) kaYÓªI§ø¸{Ðs öU™Ó¢¨µ…@¾?)5îZöP ©ÌØe`Ÿw4;O&=tƒ^z=sò\
ðÀ¾HÄ©$|ÁÚãfO] _
²Ü`vf†
Ltq€®´L»ÍÝÈmàjèàÒ’1¢ƒ^^Î~È eZæ7ûŽíÓ“éqß·‘›5ÉÕCrQ_v¡ÕgÝÁ<ü(µpÐꀻÂ{… ÄýXmTÃÛìo²ŽTb¡7ÌOr:Ö4ÅeZøSÚ±«¹‚I©¼Ó–Jã‰&Ps¥^8Ð!ŒLlƒš[ßÔU±líh”FE-%H„¦7Ût#N»'3B³
3ÎTTµ¹Vê õ’}Yœ“ÖWhû€88Ûö^/xŽ^RsÝS¯._¿eKvù
HS†‚gžÐƹ H§H©)ê‹ñ”Û9ÚÎDÏã^ÏÜÄ4öc•4RÞ¬?NˆÃñðôø$|SŒ) ¦mœØ•¿l¥„iƒ£GÃíúíµw2Ü ¹O
7úúüp+³¶Mo2võROµ<k( œn’=ÒV=B—V…Ói%¿(á†vZÁ)°'yíG:
¬£Ôº ƒ^j6Zýf¥Á9oUÆt+pRìbL“a«u™T\-óm‡½Dú°–z’ êƒ7]¹Ô-#òÔÊ5æ 6¸Çl*††7µw©Ñô| Ø!v›ŽR£µ*/Òu‘
c—TÆÔº£8æ{ ›Ì_
w)NÖÀÉ}IJ\Ѽ“¿»"°¯øKƒzXŠ¦1°‰`ÉIlBÎÕ›×ú‹ÝÈæ vWŒ¾ïéMtª+Lè)Ϻ¾'’SuØ'çÅv«ˆÀ ˆ0ÿiNòÜfÄôBw€Ô—%%Ðë#žøa¢µEì6£ìã8qÞ硓4zÛšîÈ\uÿfŸmþ«Âúùꥪ(mÏÊ.mabQÿç‹AC=Ürz
…q½Ý¿¾zyµú—½<Ø$ȘÁ:Rß_~¿Ð à —ëéæí¬®ÞþÔ3eƒ¡]ÖaÎl4Â袒—éáëÚæ:k@’¶û®>°â”‹>2úc.ÃvcEv…];êW@Uysi¤ "†úÊÀ—W?}÷VÏUn~ hÐ>?,®ûh¤àbØP‡dwC` mß ã¡*dÜ0§ÍŸh¶
u×ë®oñÿ0³qJ`©™ –ß‚QÏI@Þ«–i§±#–4ûÑÁãèíÁöBAvõP¨,}å²V§%
ÂpJUKOAŸüòéL½DOÜ”–ÙâLKJú…#þÃŽtýqG>\|
!„XmùL¢ ®†â¤'sÂäBkF{V4âö—¶§B|B+ þ;†¼o|Éò Ëé>£½¹’öÅÿ³\dÂ,où-¤ŠôèùêòÃêI“'g0>
stream
xœµXÛnÛÆ}×W
„*¬gxP´nì )bÇÇQ‘‡ô ‘£ˆ-/
9Š¢—~A>úì=’²å¶çR° rf_Ö¬½ö ~">eÄÇ?û›×³å}B>ö3Ÿ|œ}š1ý’ØŸ¼&?®`AŠV›™ÙÃHÂI’4ÍȪž1 P?"«Ãì½—ï»êƒýñC/U»S¿xÁ/sR•k|1_ðȧ¾Ÿx7¢Ù‹Šœ]=ÿ×ê'p™Y—àjÄdU̼·/îæ«_'áð¬^Ï|e1º÷V[IvBmá_§H»!‚À ÒÉO{Ù+Òïd^~•=Q°îk%‰jáêJ96[ "D>ã<£iCžàÓ‡ íÏ’ôîãÓ”ÇÜqþ›‚lº¶&‡P¤(;™«¶;â.@×ä3@-f©ÙèÑÕh‘ÑÄ2ûÂƇiàŠEqê
ÆÇ0L àµ8’¦Ud-I[—JÉ‚’•Ý^B¦â·9ÌYÂ<ÙÑÿ×}[í•ÅJGŒˆtm;‰š´~ÚËî³>’ $¸ÅÅ“ Æi†ä³„r–eüL^>M¢Ä>oM2c2<â>}>›#œš¬“•P¥ÞâÎ&ÉG6àn7ÂÙ(N‚OÀkçà šš†Ã¹9Çæ ò|vb#`4vK½~;=©8äîE[Ë'0ƒõÌÇÊH @fí'4ˆGÈ.vÓ1°!F¦cìäN¿~_"kÕ@ô¶SeÛPíû4 ܽڰӌስ ›”•Í™4¢ÖLAÉz-‹B¤4yü|ÿú‚”Šä@š5¦¥È¡¯ðÎ"ó]%Æ@P{.Þ Ø÷ænõáç·×÷wï®Nk6K)cÜ-m;óÖU;ÂÀC “E”aCï½ÁþíœkI ¼Ë›k+ ƒ+¨©È9Ú
8-ÌóªGc õùîùr‰ˆü ç@ 8™Äû"ê]%iÞÖK©òeÙ÷{IP_€×#1—è0¬E” Ñ,ömRŒ>‰ñß—õq6ž²m_Ûc¸
hÉJ€'ÙªÙ ,ÿ€ª]?¥Y2‚«é‹¤!CÖž
²÷öåê²qÚeÉ“ «ÿS2H'qxqküTAqxâŠÄùÿ#³T °–Ë¿÷ }5ÂŒ&iäm”ÎÔ˜D'Çh?uBQ[Jæ)++F>Á: ¢•cLµq ©TFÃÔy`8xhªVœñ ª²Weó‘lÚîÁ‹fAç‹êC¯6ƒ6èdÖÕØ8l«-é‘O‚,M„âŒKÈNgß5Zz%Ea@Хģ˜f,r™„ö&QL‘ÕQ;Ô ºýCxAœòô4ºS-Éö”ч²ªP¦\È&„«†n Ä'žW@£9n§
ôÍœ“÷_ $Ckñ_RH惢%áS
Éi™ãïÔÒíœe@UŸŸÑ°ƒú0°Ùt¦‚¨%põ-þF9|¾}гŠkÛÿ']|àFÿ³¢aN#Ó¶øÙ¶
½0=§…¦žaŠ…¶d»‚ ±ï·T e£ó‡®ìûéc¿jó}
$ï—.x«{ýÙêj
‡]r ]mhû¦Ýi°yG
ƒ¡ÿõÄGf-@ÑRlè²Wó Xâ̻¼{@(˜‚Òð)чÏPi³À9ÆåúŽ –†v`ËR)°¸ùÒ{N® Jû²ßÂÛ[¨Ñ r© U¬uÒ)§¡ëí0ÊöV”aª83d£¥õmÞîÀÀ˲R€Ÿ€>qýEɦ‡Ðª¢Cí öRtù–’k‘oÉWY(½„ *Ù‡T¨E÷ÚÔ¡ë×3ŒÎ0ä€âª° 93¨3ˆ œB㸬w
Ä RR8ùx`ݺ†Hûm»;kì˜^ÙäÕ¾@©{f/CX^U!»øC±¼L O¨Ú~wsü÷ߘÖ}××bQHÝù8öÚL( ú³ 6e/tˆ–íZ€w²@k‡èæ˜ÚÕíMqHYpJp¸¡Ü ɛΎý&° ¡ÑHá§"â1S^%Á±Æ±ùo…%€%f²vQ|¿k{%ªË¢èdߟÅH߀Ù:Þ3hà(¦¡[ë)ëp¯Œ‰¶>j: 9u$L‘¸±‹ƒÊû§|½õªEÙ@Í#_´2ÊÍñb2° îÿFÕ#¥ 8}u«KÍ© i«ÆÊišeƒx2‰u Iº6ÿ8ljš% cÌÒÔqC.s¸4Ú´ó$ŠE0Œ n˜¼%®•£¸Û†)k˜†£§áAËRž:)&ph /Û‰8CÎáàÀëêÑ3~p/ÞC›ÅÆv‹²)Ê9L¶ŸËB>ië]ÛèÖáT7ÈL‡†ªƒÁ€À©Š çIî_¾#Q‡è~"þ<„oå6þûÕ4Èp,¿› aîµÛ ý “¶5¥0òà Ät˜¸ûfÎÓf˜*Z
7ÃÝpóuˆ …«øD‚˜ÙÏM%À€‰"÷4îç1Ÿ‡Þꔧ &oh2½›ÙHl”øBúý/ÐFÐuSÅöZ &,h©AÄ'ÝÄÜÄQ¦Áj§êþî†é\“ˆòx *h5³“&
Ì3™‹FOªE‰T18\ UÕj¢øaæ \¯êw"—º…ÕÞç…Gj71M&½~16<œ‘¿û v=Qí±Ý—UÈ#6%õn[Â\f<Ù6§Ž»2U…!|SÙKžUU˜,âøO5½ú†Tn˜ÅúÂ@Õ%ûtRMx†#ªöäEžËÒ‡_SòÎ\vô䯆‚‚+ùx‹ÍT£†¡ç`}Q2MÅÇï À ¸S
=ËQ ®¤Ý¤ì9 ëAàÆöÓ3ˆýуòᣠñÙõjöOøû7g pendstream
endobj
75 0 obj
2215
endobj
79 0 obj
<>
stream
xœÝYÛrÛF}çWLy fEÜyK¼NRZK‘èʺ¤” "@k` P÷òÑ{zn (Ùµ[ÎÓ–«,‰ôôôœ>}ºù;ó\ŸyôOÿ\mgo®öÐÍ<ö0û}æˇLÿXmÙK,ôÁr=Sïø,á,IW¤l¹ùwîN^GÙw쇛·ççìqÎC7QèdÕ Vj¶)dÈx(ÜÈxñ”åŪÜfÕ÷òDAÄ]DËDìÕÝ ^ɨ¾¹N5T9Îr1[~w뼿œ‡ž³|w#íŽÀì©
ÁMŸµ=ùz(û
\z=‹qVabE ¹°h»²©YârœÿŒõ›b€Ù6€/ùá‡ësÊºé ˜Äa7Y³ËúÍ™<ŽÙLŸÇSa=lÊÕ† æ)ÂúC¯·ÅœGl³ïª£´²ÊºÂÕó=}2çí‡ë‹Ë«å'üÀa†#'ž+‹Ã²“&š¶}t²~“õÓ8ŠÔMO§ˆ³Ýwú¹1‰ä}O'‡#ÏJG^7m¡Z¯"à\Ø͇Üß-VoUòOl§žËckî®QEîž^\ ÚlAwž§¿ºÖø—°Ž}3‰„ìB^éå’]OÝpH¶·—7'‡nYTD^*M¬²š.yß!ïû©¿%NB$) úfÕT¡@…
¬d82¢MWÐfu·.Z™ƒ"tƒÐ„H¡ƒø!L‹7¸Jõ:/vþ«%¦ä†f›
¥\QÔlÕlwe¥ ëö»]Óö.[ÒÒmvÔ^¯÷’ÄŽÍže«U±ë ´7íx¡ðH‰„°îÍ)Ì
›æO ºdÞ5ûvUÈô– My,œ ¾ÙØhƒ®+ïKäq ëÜW&Æ_ø±+¾v‹Ü
,ˆ¾|‹iüì-.ÂØ
"Ø0üq•ÙWSWD†à¸§âÜQ5©ÐeÛ4UNŸÜ—ý6ë>SèÉÕ©›~´ñø¿w“¶S óé;–ÔEç²óµÕ™ŠÙP³³ [È}¹vcs&ì )pžànàWÖò:Æà Ü„ÞcÈT/5Üë.Ç ˆS[.É)$dNRá : "\8J¼Qsà:£ÌÑΡö ´Ö>JÇ…oVé#ØB{?§¥‘ïì˪ !F¨ºjKžÀJ2Ê—X¨Àâ¨]ו÷´µ@1ñì5Ä"T›B-t=e«o·Cúce#ÖÑþ’:‘D*
f/r*Û(Ê<¼'BTœ¿uÙJ,ô¦‚y±V çƾjØdûªŸ2ˆÎSì;:
y©ìÜäVלp%FÃæ&Å®ßýíüú$ÑÒˆ®î›Èš'šH )u&eιs~ÈI/•TUÉ¢ª/SÁ‹~&ßNÂÿ¿'ÈVO(`™2‹nu2 jÝh§IL dË•m‘—m±¢BWÔ§„£r¹µ×÷ÓåÅÅå\¶ ‹_/.:cÕjí)Öÿ0bR=©³<¿|"Ûáã6_¯HQg÷¤Pà&ÔC5ý 鬫•vÄFXÄ
ŠA°L¨ °:b f²= ys>ä ÉNîH‚bÙ3Ò ÉâÀVªÉÜ·=aTl}¢'É $@~:¿x'+öÍÛ+Õ¨@Y'"þrÖ"S|Kc
3ËKy ô¾H-{¾¾D·¨¡ HŠdŠ&”ìBå;ä¶QJ]IùîëUSç%Eú(-*< 8;Ê50Égô¡¾Ì± ôé nNèçe6º¹&us Z#±ªJ iL¸3„N³*!ë⫯HçòŸãNÎTùGùNˆ—øXõE±bŒT“¿/—Wt³OGLBë È0éƒjÍ ôýñØ98ŽlùnÍ]ÿöý›7¬+k)d5º4¶<71’èØ% .uÜJãf$¡°A’`È ˜kÿP£KÊG~¾¦õ Z°"a’F¦ávºÝ°)ìùÜäÿ(t>ÕÉÉ”¡nLòœ9'ŧ+'}¡Ê¢‚6UzŠ¢ŸÆñI#jLœMY‰H Añü0Vœ%¡HQ–Wë{“ C+Q¼žÕ°Ÿ(‘¯´l“ŒAd†¦ôãÕåõrª=JÛ9j I Ý%Âtª2êW0U
‹B„s¶Y{ hH8-”éU*؉ìÆt»VTƒ—‹øqÔd½!¬{\n¢D|PHdg/ÅÈ ¡Ì< !ºæLVx©Žph•pÈ /•G:_Lö |°¼u\íÃÝ(žíuëÔ%ŠhêFÎú8"Q𪠥±*{{…6$7ÄŸ°)5ŒE¿Òõ˜Ày2’òÑ &¾°#)m‰ÚãR¬Ö¡ÔÆÆ_xd€—’˜Ÿº‚BeÒÔJ5¸Ó–‹¬ßƒ¶´W")¢» $)ZÍ
ÔÞg(Hï¬;QÔ>ÊWñS±ó‹L*k hþ¤òdùîD̨ìØV#ªÄ äIƦøi‘Ò)5–7õkA^RÝ@‹˜êãôHD2ðÃgÓ
„‡g48ôGÜ*:’)°¯ë‚’ möŠ/N± †\m.\nìfLö‘M<
˜2)' PA\5†0è™ÆÐy o„ø^3ØIì!…]c"OOyQNü YH>Î% ë^âR–˜¶`ùáýûw'D“ ˜'“]ó™fH»D1©áO 7Ûwº¬Yx<–mSËaâ£Rc˜©‰eÖ–¤n»éx.@“e)-yßï>íÚ¹/ º°)بhŽGKƒn±^#p Ýö –øX±|Ý*‘4ªLþ’1:nÌO#KxLÏ×”•¬©.6ΕúzßN %yû)$J0ÌtZQˆH˜2e"X%Ã!P%ÒØéú‰Ì|A¤Ô ñ¬è_ªNHY)åÿ,.!ç%¾R‰è¶ç:&\?HÌ$À©WÕ>/ì0@÷(w²\ ãA¶ô(ÐCäzzÄe]>A%5¾È˜–ý½f×
cþ¦ÍèHW¦Ð!„ÉÙó¼ÕØ´=ɬ‡Ô†)'iÊkTe%¿jè'P
Dì&^üœáæ‰í»Ð5šÆþé8LF\ö,Ð5«Ï]ˆ}Ïô¯Ùð{Dî µÔ úëNöšUÖ‘Ì,ÈK5|Òkd)«Ãȇ‘‚ ê D-qÐ8Ðj(ÒÿyÌ£¡àÆ=_½ˆÊÏmÁðåŽï–³_ðï?°y„Òendstream
endobj
80 0 obj
3198
endobj
84 0 obj
<>
stream
xœZÛrÛF}×WÌú%à–8Æ îyÓjåX‰#i%&µ.yK‘CkдöòÑ{z.¸Pô%—«l ˜™îéËéÓ
`>̧?ößùæèåu š#Ÿ= }8ú%³ÿÌ7ì 3,HéÁlydö–H–dO36Û p?b³ÝÑ7ßÖë;•7Owj«Çö¼›°uqO/&SùÜ÷ï×¼Üækvpõä?³Ÿ `Äl¶8òy*õá^^.XÞ¼/ÊÖ®{¬«OO¬Ø¢Ò¿×ª©Ö ñö˜åë¦bïËj2ûï‘ôc C=ß ëÃv%Îb§¿]¿¹º¦eSŸ‡l6?Š#žøÒ¬ö.ÿM¯|z.BîYj^Üzoïn.O¹‰î^_ÞÌ.&Aȳ̗ÞɯgZý©Lc „ ›
iäúÆB^ûô¨`¨]«[Õ´Z÷æQÍ‹?æL Ê>’TIîgNmßõvU7EUÒö{ŶZpvQ‘)Új^í9jqÌVmûøãË—Lm½fÄÔ¾©=Ù©fÌQ`
Žlk•·ŠìÌ^ÏfWÚÈ…j¸Þ‡LEÌSm2ÝåÕìnÏ|’©3Ó—ìwuy=‰u0ÞÌØ !ÑÒiˆÃdÖϻʻc2žv®L"©uo–³u…°Øí
ö,†`²vBd
Â屪[z:¯ÊRÍõÛrpDÑ2ìsdEÙïÒÔ’FM[#ÐèùËkáÛä—©/ìÝ?c Áeœeì#yt›ßš£]ÚE<Š}Û—Æ" Añ} â½½½:³ûþŒpºüf/ ôYµ Û5DFJ:SJHN\æñ«ŒÔÊ`M—• ‡Š\.ìuZ—b߯•ß°eU}òZíùL²h೩
õ„‹>I¼±Q…à©ø/ÞQ]DÜÝUŽ÷Ô‰yÙ0„Æ‚ƒÞìÎÿŠà;qçïÅQÆÃ8´«dPyçå‹…‰yÜkÞMöKÈÒò¯ë¥.ÜÓÊçQõJE{J‡D1¢>É=ÏÕ $}/5£±šaÌEïô}ɉDŠì{Yèd,°º{Å$è€ßRƒÞ ñ8 ‡¸øKþ¬Êˆ §] 0 –Xè6\á€úœÍ ºòh´@Î.Ôr’éêxùvÝröÎ;ìó-c˜ŠÀ °© mÉ4¸t¾dOÕ– ÈØ%sîÄêÀ :ì x" [&ÝGÎAŽÇ<ÝÑmµïHöÅwˆÒa’#ð)*æüBÍw\L$Uþ4òÚ6™>T’ÕdÐ
[· ‚ª\?±|9‘Do"á-©d®*½¹Æ”…v¿·[µÅ
§e€:ðÉã5
`a]A Uþ¾¡j‘Ûj½[©’^^\œÎ( áéBDó$‰œweŒÎJú–(Ñÿ/ ý‚ ’EÞÃv×/Ì–…5–¶™ÃFÔr‹²iU¾ ÖÐÖÕz3©È=ók€Ú (í£ßÏ®oÎ//ÆQ"i]å15]F)OÒ5ýâr " Cd\ÕÇ=B±%òñÅŠV‘†}E¬Š²UµñÊÿT
®êMQj–hhñˆù™LÔ°'ú ¿m69rï1¯õ†5^Ñ›UÕ´ÏX‚/6ÀVæ…@Xå-‘û²jµ›ŠZu‘u =Îç+¢»jtSéKÀ—£ ÊæG,ÌMeOn½’²"ȼe5È
ð´ KR
¹!ŸL#ßl¡‹ë$^ÌóÄÙqYK\ÂG©ÃŠÏ1$›Åä”@Ü'1½ñb0¬•ñóßÙ|£Îá
s½˜VB 4ΗÞñn˜ŽAbØ[óÛä-Œ×èö€ Ò ënxKí YvĈ¿™X$<ê¡ÑØØf_¦Y
iߌy_§p
W% Lð³^a¢Ê !„Ÿ……% øà pBaÀ^³v˜IÇþ5WÔíŒ*¨‚Õ&Ǻ¶e4~3Ê‘HÆ1Ó„±€æ Që%g¯H<9)ŽÝ
«zœdîK2õé°iпÈÄ`U¾y\+ŠaA8Þ'ý„#{ØN¿$Š½j»^˜ a%™ #ÉdÚ g¡¯ßíÎL“tðôÇÔ7žÞíL €ðHº qmc°Œ‡GÞÓk0É8Mœû·^ÄŒ ¡'rÙK‚bß(ó8 䥹žŽ»Ö× êê< fd^ Ê=U5ÝPæ˜>GNÂß1v¦É7vD¿¡î¼Ñ;¡ç°<VãÆ5—HŲ8)è¯MþÞ´7‚–RúAlà7dÄ…y8/z8k]Ü×y
ˆÛ¢E]›æýQ?u/Ó®êjû°B ?ì%d
NŒA¯“>NÊòu/= Jw ¿éÌ€\I0ªOAð0”nâídà`mñé¾x@Êk IP»f—›ÑËk˹b÷ªÝ)E5š
‡Cv
LØÏÞÞ]· ï³LnQ•?è4ä> ¬NÐxg(Ú÷ýå|T—È©u»2îzo7@I‚5ר?6®dC8¦g6*/›¤´¿Î=uúé&ÇÇœn#8vîÈËÖ –¹3Ãt®¶Ñ‘k}dßv¡m™÷O77'Wçw7gד„°B&Þïç§g㙊 Ý|qšâÛÖUŸj J `sÙ¹«ò«j½ps8
¶oTý±˜+æ’€§ð,I{9ª‰Ë»õæŒeUì6
¨‘]-ôò›µ µÚú4ƒ¡°4†IëùfñrïùDÚ¹ÓtùaQ’®ý¨ÙVx»F;•&E«¼|P: LJ må0凰gì ØQÂ~Ý%" ÌõúÙŠž£XˆQ¥™rÔXOcPSg9;Ñ^kO š&,XIü×{¨Ú"77ÕSCªëøeS-(}ÍmF“®RÉ?Ï™ÑËœæ8ùõ«S‘d5ùQfèjyð2D´ð÷JW±{å„w»‡CPB´²0HE§Ž‘ݳD3ÂE‹Bµb£PÁµœE’ê¢ù"$K©ù3V‚˜ö¹›Œ‰ _“èmÙéd ¬ÌºZí›Zí}²áб¬
Ͻê§
[Ú* ŠÞþ£‰› œ³ž_Ìή_
Y8ìÑONûô J÷no¬GA¿ïq>{¡/¿&S3ßpj°W(fÃʉ~„ ú¶³$? ŽÕuw¡;ü4I2Ð< 4˜m‰¬¶íCE`S¢^è…~˜€v½w{…OÛt ÚI
b±ODèØy^Rôáï^p&ã´L̈_±|±¨UÓh*˜k"¨_шá
Q®Ôô+7-òp£Ï„£_ö¤z5æ
-kÌ¢Åòo/è}i'σɻi»§âGÄw“ î˜^j!ÔêÜqâ¤Ç4 =ôg“ØݶjóØ2=é ·KiÄE,÷û¥$|N n½Ùš„@€ÐSå _
Ððt¥:-Ü—º]÷YVsl½D;F½Ùêä¬È$ºöÉT+p¡u¾´Õ8ãA
{$ûiåóÆ&ÿÁÜÏ,íš‚}ÅòŽúk=‚ æ±Ë’@Cd^Û5Ý`yêºä2ߤôUBmGwDì›#¨‰~*ç`9eµmÖšxEæíœø“”q7ÿÏ,ðæî…¯?oé\u%±EÕt“ëû®Š‡ªVÔ«’0GV¶Ýú
jqaÂMëJ=™tìhêbÅTå [?½ñ–=|Pß“eVR˜1Â\™™ŽèëÚG¯ @}¬†äXX”&äŒBo甤Ұu5OX‚ëMR
?ãÜ›|õޔ˜k»ÏÝ]±]V^Ž‘SF!2,ýzgg«S£!¡)Óþ gõgÇ3‡è–§™±+ÅOôD¿õÎî^M’ È%ïäüÍÙ?5ÕQí¶.iËBµ^P”Ï© Ôµð‹¸¾§‰Ç¹ ,%B9œ·>«§Dˆ¾l®Þd÷†½)O²þƒ-G Â(áL9Û ‘n§ÆŠi÷Øq$&ô—׳듋Ÿö@+žt4ÀÆ m§€ó:Ï5ñ1Îáì÷‰ÂË×H¯w4‚UNY EÐjœ ¿rTQ¥¥}S\mÿdpi4þ hã¡0‘Õ‡“hû領ÙÆ–†¦2Á{.§n©óFô‚Œ¤^õǨ~Ea?E6Pp€Á¤0 ‘JégÁm¦(èð»©Pß/G~ÐÏ
²Ì`ây;ªOš¦ÛycÒcÿgçkå^HFf¡……ÏþšF®á tQ‰~h| ›ò“&„1µ®QH=žu9enÒ˜$ƒCß„†i”w@‹ nÐáIIíÄÏ£‘HŸˆ€é ³1@íÚvÓ³³ÙÑ¿ðçÿ6u+9endstream
endobj
85 0 obj
3349
endobj
89 0 obj
<>
stream
xœ•YkSÜFýίèÍk¶@Q·Þ[•Ø&k²³0N6k¶(ÍLÏŒ‚ =Àãß ½çöCÒ qÊEÔê¾} çœ{ý;ó\Î<ú2?—åÑ÷×1Û´G Û ý~ÄÕCf~,KözŽ ýa¾>Òïp §¾›¤l^ qá»^ÈæGŸœeßw2k÷wìê]wëø·3Vä z0;¡çz^ì¼Ïª>+Ø‹«gÿ›ÿt„NüˆÍWGžEjsçFv]^mX·Í[ÖÕ0£nØBõlþÛ‘ïrZ¶ 5&¸"I“@?ä@>µ“Ë^Oòn`
ݯFCÅ“,”k8›@Ìw²¾èŽ-¸é´Úéyµ®U"oð«B"\?D™ŸˆÀT†Ng'TOÀÒй1÷, Á‚)2ÅþX‰^ ì+U-Åõa†üI“8q²&¯ûVÌr
j wgz᪮^) ‡Cy¸vÍpf[/Òà“Ff+mz+›‡Bîñ4tU䆦T'˜Œáº`’ƒ"´(g€§z;LÏ»"_æ ’®«‹áÐCÕ+ÈûŸ3ºÂ1¡Ü2+
ä£-N?&;¿¿æž¥XbݧÇÓØ“F 7WqÚ»¼Ê
aÅÈzªn,4rng.›S”ËloðÈæ JàžÐ'õ„ïH¹c};Ø%ü”,®ž
_ß` w”ñ EK¤ä?y71wCï0Å}7þ³wªÜ>–BÆj[¿ óÇwÓ˜§6RZN&½{sŶYËúÝ*ëP–dâKÁ=fYµÒ)OÎ(êú ¾¸×$aOàU>$o6ž.„›5ëòF—®ý0æ Ö> m5Åt
1ZÒÆõ'ÙŽ¼
N
á¿TÄŽ)8…Ñ/‚ûÇ›³»^|x=óMF^hÀן€úߊö@ØC´wÙùZ«ê Ò„V#oƒü˜åÀRY-³ÙDÉ•±MQ/pÕ·ÖEênûæ!?@BÒX¡OüjNy ŽŸp«'FÜ°–ÈîQÊŠ‘"ÓQÀ–€ïÃ(ls"Ô½ÆÊ•GÐ'SÄ<5n³%t8i³µ SE~p3Q¨Â(¢<ä.åÔ”"¡æÅ‘óËé앹ID i‹âúòüòŸÿxR½(;1Ð'tˆ”!œ$ð ºÍQ‚Èõzüß¡Iu#0øø˜wË-«½íƒÉÒø (¡‘xV”Ÿœ¦› @¹àÜ©{uA]Ü
ü`4Pè Òš u·%õ–WÖ‹qD”a/|b¡NüG㬳 ÒEªbÂdÎ’6m;„ço |©6@f$Ü ñlmÚ²¹ywz}vèÞd H~² ¢“ú#r*½O÷™ùH@/J 9Á\rȸo pG=¬î)â„ý…z~PW`Ç?þxv}sþßo,^¨ïIñ²v'—ùzOØC3³]#ײ¡ ió/„!²Øw²E‹cå]ú¤ !Ò›€œdÏ‹õ¥f‰Ó+~O ˜]šddÏL‰ .ÂÜ•ËÞ©Shx–&Ãèîp Ê
Æ™Å0 ž õbŽh€Âf"£ÇGˆp<È¢)¡bïxô^b¦ u©ºB8âÖ)k¨PЀ5+Ý7éIÈz&ˆ7ÓÄùc™Ó9*5Éý”H44D#¼ï;$NªvÈ*P^¦f‹ºC‡Ü!@2ƒÀćJŸVA×äzLã—¾“† 7 (Âœg•Dª2Aüõ!øòH`þ*åV X#ë½ÐÂt$ÂOß¾½>»¹¹»yóáêì ½þZÄÁWDJåe½Cÿ±ÒÍ9€hA0¾ µ©Ö AÕ€ëj¼Íί "ˆñêþ¤¨¡Õ@ÊXÒHúhŸÈ¼lµjåç£éÔ5šï+Âà_ggW³”S¿#œÓ‹óŸ¿¹Õ‰<þÂœÂLrù±‚"ÔèMÇ&LÊ]VMãá"µÀ§dA{LâRÍ¿ ò•™Ü!Í›Lel»‡È-YÛïH˜*Â(‡¿‡\ Dª[ Ø…„¶âº)À–545âcH<Ýæ¨Ù̽´³è,øçɃmù0Wf¼:‘+&™sP5”D»ªÜàU˜‘rýg“Íbî5ø ´e¾ogü§)<ûሠ×/úÔÊðFL;› ý_ÿw#ò‰endstream
endobj
90 0 obj
3221
endobj
94 0 obj
<>
stream
xœYÛrÛ8}×W æ%Ô”Œ¼È›'ñìxV±=¶²y°S.š‚,n(R!({½ûþèíÆ”ìÌNª¶\)—IèËéÓ§‘o$¤Œ„øc—›ÉÛKNîÕ$$÷“o¦_û«Ü_ðAŽ«‰YÃ1ÍYl&,Ši˜’Åãä:(w]}+ õt«dßnû› ¾™’ººÃÓ£(
iòàcÑ슚¼úõôËâ÷Iœ‘#ø·XN‚÷Ÿ.çç‹ÛÅû‹Û¿Ÿœ\œ~˜ŸLÿœ pj©¿e‘þö¢À7!>4OÁVxÒ˜'h^ )HÝ6÷”\É^‘~-ÉRÖÅ®ŠhÎõ~"£<Â,¾fÕ4Ê9MD 4J§÷g‚
æ¾Â#ldÙ6K5ƒ½‹^ ÐneWôUsOÔ“ê冱çuíT”œµ=)ÀC·Q»í¶íÐéJÁkô’›àx¹”KR5Ú
‡4ã>_œF)
!çøNç1£ùëY?[ücþCiÃCaròZÞ«¦—ÝÃÏgIõ A ÿjú4JC¦àþ<¦… ½“ý£”KŒ3 -<ŠY ù ‚ðUŽ¬ÇÀ'.{/’ c¹Ë €î•Üx‡/þ/‰#{Y
iÄžôöR +P‘"1 1Æi xv<Ø”ÒTÄ®ž>ž\‘¢Y’‹)©È¸Ž¯®>ërHò<8¿üpE ó§çgWhÄ)#†;ÈFÓWeöYš˜)
i1uð9;Y\¾GC´€É‘Õ:¼-ºb# X{}×Ö ÛN®d'› °r æóºSÀ‚U
¬VÚ£m¡Ôãx!Oã4h»¥"«®ÝhKñìù$xjwÝô
ØÍÂÁðÜ×ãu🷴‘}7yP ¸3 ¤ö¹–3Òƒõû8‰sænÓNzCtK M=ÍínH~0 åóŠ—˜.¬í%`C1×Xª+ÀÍcÕ¯#_$ÖŸ"ø…G~fcú ¨áAX9Š›CÇ·.3 ¬rŸÀZëíi;Hi»Ùörp‡öô§6ÇÀ†ü…ÍW'—GÆ0óÚ3ÑçûÎD eY“Ñ«o!ª£´pH‹÷þ «~è<£Œ¹-¯ÍQXʸWîžL9{tOÓÔôjºŠƒ
T.p&s‘}KG:NëÑê¶Ñ•‰M¨ÝA–R•]u‡fȺuçe–Âu”ˆh‡¬ÕO yØÑîª-r ¼I þÀ%úH\£9ú@¤é…ƒàó œõÓlµÏ#˜B “Ä›µñ¹ƒ
û÷i3L¸6²X! c >¬F&À¶¡:6E9e몑ÎÌQ2cÊ=ɳÇ1× Î ®«rMä¾\Jh–EnåƒÜ‹ƒÐ„ìÚuWû8,|‡XO™0v ™zˆì¤>â:ÚBŠ4ЬÕV–Õ³iÁR?X¨óÉâçëàS³”ψS€¸»)@[—¥Oëb¿îYŠ‚÷õ¾è¶ £È•M+Pª–N"BIr àlñžþíìüòäÃ~ÖhòîŠîÉXXÝ7¨e{[è}V±½Ve:$ ÝÌ+'êW¾C»Ú9V˜{ôryò¶ƒO§hæ>³`ùĶj"ŒbŒÚO`€•0 f£v`×ÝÜŒâ°ÂèKˆÌ$
÷¢ä
‹â·Åâ"Õ=L™ Œd§Àà…φ~L»«êfÙâÆ 8a’ÊNþöDõOP¹û +RK#!)!›ÕX™æ <àV“_
U•öÂL_¿¸X{7$#©~Ø `„3í?²ÞÞm„à˜{? ¹²þõ|>?ŸšËÛ8ø1Ï©»ü.–‚Æ
P(2 +ð‚&/›8§Ð ÂqW†ºcöûwÚ2P{2³0N€2ýŠ Ÿ,&ÀÏÁÔ>
stream
xœYínÛFý¯§(LÖ,g† r,°n›4.b[kÓÈNÐc³¥H•¤êxŸa º÷ÎIQrcgŽ%Î ïÇ9÷ž;ùƒø” ì¿‹Õä ¹m&>¹ü1aú!±ÿ,VäÇÄøEòybö0q)AcE’Õ„qAý$÷“ko±©‹OYÚ<|j²¶Z· <ñaJŠü Lg<ô©ïGÞiZnÒ‚ì]=ý˜ü:Ì„$ÉÌ‚ƒ½t±È—YÙ¦¼ü\Õ«´Í«’Yú{z›ÑiòÛ„$y;ñ®šlz&3ßÙ SÄ`6 æýtuñö|ž|z“$sÜ4ó)X¾˜DÂ.8¾Â¯}üŽq ŸÙÉ|0EHÃ(¶O}ÊU¤
m+Ò¬³Eþù´wI7ð»ló…±w•µwÕ’€- 7i“-É¢*Ël RÕæ5ù3ÆBIfŒo¹ðöü—“³Oð×ÉùÙåÈ6 S_ZÓœY𖶮
rrz¬]çÆsZæ½çésûà|.HZ.Éå)X YB;uÄgÜTB¦0ôßW ¸¾i²Zï[§Ms?UTÅ~yU½$M[çåmCÒ:#eÕðˆ,³EµÌ–G¤©0ruv¨ Vâ¡ HoLCkëµ×”SÄ’b±WÝë…Úp.©Ï£ÈžB Ø—$5•é*ÃXÌŒQ€itÁµÁJóìƒ ‹ª€¬müÔÞåuŸDÙvžXȨŒœ}.IW—¯.Φ<¢>“Ò;>}¥m d
"(k/¢½KÛ#@X¼(6ËŒä-X‚#m؃óÀfIã-HÌ/,¦YNE¬ òÏÿÓ§7 ¾è ¼Gçï~¶[™FÅ,€CÓuó´Û®h :ØG!×!kŒÖ]Z“$m å5„¹Í4˜å!Óc* Øî‡4Scý‰Ì`è._Ü‘æ®ÚKr“‘ë.{ _^wR\Æ©˜iXAL ³§à‰:xÂÀ'Öåš2ù†õšŽëºúò`¸¡eØA£.RôÇ¡ÑÀKWªöN¿Tc ! Œ°ÁâÀïBèR©ypŸú6À?|4{ *‡ ¦|*8ßÂëµN6e¡÷%]‹¬®Nû‡jãBš•ø>„äëqLuö–Ogûc8c”K¥¶pæê*&·¯¡ï‡Õ5¢qÎ=Õ•Çݾ§UC
&1Ç=5ÆL!0'T ;À ù5¨KÁž u& Ô#Àf ö¢=ïÕgŽ°¾®rpkŽ®…ä¿Y
dõ*/Ó0Ò'´G½qŸÃ‘JŽàG´uZ6ŸÁÊ0€B 0ÚJ¤lÄ“ãX1ͯh_Õ‚
"xGYŸytñf„80ðFÖ5ÖV€ÍQ
)y?eÌ÷:tZÂÚ×lgìèò ÃKn3ì@(ËÄ^U,³´ÇÐ'¨r®‚[ƺkÐ Z ž Ð þ à Û% v — 1üPõK£ŽâX
Šê|·óˆ¤@ÍÛÞÔ.VGÖ¯qgáºÛi-óiŒ=5 ¼ãËË™C37åÂF•ß…Î{wÞ#0¤Nì\ü¼ÃºâÓÇ=N›ÕXK=Kˆ8ý :^.
*"
Pc ütsÃÒ*ö1x>U }}×þspà™,ŽCñ \Á,?d{X Š×IÆNõ5ööÍ
ɀŶSqÐ1ñÓi D
††E}À' oX$\Êtô°¿ETöåÂè˜Ô{á( ô·Mi:©Ãì ˆ .G°@ÂÍ,ÍxdP ͤ[ÞÙñ°,†¬SœPp¶a4ÄÝGÃ74Ú]‰´Ö 2Œ
aÀ±u¨ µuD«ãXhë»å&æé߃)Õ!Uá^,…¡pâyX²* ƒ'Fh±D³Z{,¶q5Äàˆª1> ·P¬3ÐÎ-©ÊâÁL
‡àdÚ Bq—°áì€2¸ÜÖìÐlÖëªn·ë!%¯µH’Ð1ƒÀ…–1aK(Y¡ }éMµi AÁ[1<è[/ ˆ`Ì‚9 #¯â"Žð˜+¸¶íäUòš,ëôsk~ϲ´†\¶3˜Ngͪ]Ï|Ÿ¶_ZƒI×/ AÔᶠ¢cÖÁÅŒÜ\¤eG0=Ÿ´}_Ô2ç‹qËh6€Š´éœv'÷Èåv ‡¤AZk8zG%@˼Y‘?ó” OÃGqá]%oþy–¼==À©¾×SÌAØáÜÖ\ùâàHm§P˜d˜}[ÉxB‰1§ ¿qxöuÎl;ßg@º6jÇ]ÙøÔ9I>¥ë0á¤coÕX:ŽÕè÷UŽÓqÈý]^ôs•yÅ\L20BÑÔl8l·] 5\à!ß’ùê+wqÇØ(*»Ù ’ðx»jзþ¶!}p´1Ј*ЖRõ=Ë´*qœâ]6÷€&Ø3íø{FÁTÝ#6%‡ÜK9Ö‚”Eèt&sïûî
à‘7ý ;b¨X=,û6C5úAádø•
täóò ƒ£²ã&:-ŠjÊ`>÷îûéÂaoµR}»£GÞ#Rä¿ëhA§VzãP½™’=Y>>ê:é•íàæzNÌ{Ü%2dËD¾ASˆR.D0y;…Ã"ÁUæ"{Iš|ýíÿ×`^§ëJFt±u&0>€2Âo
è/€3h>iÑb Û|ëʇùõÅ\Sü‰lêÞ¦(º©6}0Ç’öדЗ¤ìnB³v4>^Dà¨ÐìÅ÷=’Ùk—dènÉ.M±4Fâu!úVVÐæÒr wòvw8 _°rp\…ÁÎë÷¤ÅþBuتpBB j®PYý% F0{tù±sõ5±÷µÛA܈9*(ºîÉxo9”ñÿ_¡‰ÂøæÅ¡§Ž71ìf¸A°bÙÖ}K½«÷õÔ vÂFi쌒¢ÄVÛìÿBÀèuþà
GN¤©YÆ~ jÙ@ æpŸ™Ð=xÇG¦ð»WÉäßðó<¢¾endstream
endobj
100 0 obj
2275
endobj
104 0 obj
<>
stream
xœ•YÛRÛÈ}ç+ºò2òVÔû#I˜„98Ø©ÌT8E «ÁdÉ‘d ææüóY»/’l É) ¬V÷î½×ZûÂW湜yôe~.V¯/cv× xìîàëW™ù±X±7s,Hèƒùí~‡³X°8õÝ$eóÕ¾ë…l¾=øâ,6My-³öñº•]½î® ÿjÂÊ↠L¦"ô\Ï‹YµÉJöìêÉæ¿ ø›âÿ]Õi[–±Å2kد,kÙ:k²•ìdC/ù®O«ðbêr/äÆÊÃí`%\ûÖÈe±X²vYoÊœÝH¶®‹ª+ª;ÖÕ¬[Jö·lð‹lVE•u2ÇYm»U7 ¹pê&§…›V²ÛºÑ—âB¸žHì]< Ú«k²ª½•
Û.‹R²E]Ura»hêo“( ÅŽ«öp÷)näyº÷ ›ŒBòK ‘Äwƒ àÿwDT¸S7 « S7°`QÓ7qÙ•s”çú±Ë @ÎæAêF!ÌŠÜdð æó c]¨ nÔ;Ò9ú4FS2aþÁ¼e€
7ü `‡Àiì²"žÂš°L¯ao <káÆ1çÖjGï¢e 9¡,c7E·ÊÚûCpY–V ”XšmS0`‘©(ãüe_9uâ‡=¸Ý !S ¬7L$
¬êXÑn¸Œ€›YÎ åî!ài`îñ0ö ‡?탢ÌnÀX
×4Ö¶DÃYÖÆÓQhØ r;îÆÚ*gë²ZÑ'85tEÛÕ˜(ÜKóÌÀo°v™U¬®”
Æ“‡ƒÓ
xðŸ¦í”1‚¸ä
ÔGÌô>_7²yTzÒ$·´R~Ïã-y¯Ý¬×uC¯rz¹bëbq¯¶¹‘m§Œ"·g¥v†Ÿ$€€Q6g«‰g>ëMòãD™4ŠÎo´2ð]Ñ㊖™¸Ö
kë•´v7K8AÝ»¨ò͘œÀ± OCçDŽU² P7÷¬©7U>íšbí²!‘ð°è(UÀ8]P£ÃZaù¢å–"¸~Ï?N\4Ê_R¢0tã J%RÄ&õ¸øüN¯µºðDIj9eäaç ¢^‘Æ[“0ÁQôŒ:qâ [ƒLL÷¶Fâ
]áõv¿˜$äÑ€kåäï êséø(¼>â3’Á¶×A:4‚VöÕj©ÕŒ²d¹ëƒ:jcŽ&! ¦Î§ù‡ë7>Ê
f¼íëm=‡
EjkÒSö&k‹Å ÞI€'ü#Läò–Næ Q§gsÆj“lSvHûu±‡– AùhÀITU-*m¿Ùf+
ým‘Ëi»nd–«ÔM[®AZ Š†€‰]厖sx̳‰íAŽôJŒôªyÜ.e#͵ZYåúf8§é±®ªˆ©Ý]%
'î «Î¶ ë:ç61ê@ôõ®mHº‰Í‘Æ8ü'æuý¾‰*Q_Éž¶ªH#Úë2Ã÷7•É7¨ ÊÆþYdënÓ?²—lZ]¶L(ð÷aóîäýñl¾(
´ê(¼¼+îHæö 3™†Aäœ;Ï>§øçòŸJgûËßÞŠˆÇÊé%×$] KGžÂIB¨Ô;ÿõ‹ÓJh:dy(re¤‘y½D½[¾ò€|îx?pcÁŸñÿz§ E
iý¿¹)AîiF!N?„ k7ðz%¸
w›Õp]æSE „àÚš.k—°ZÓ~êCIƒp§:u415‰\½*ú™ø]Ÿ ï…wJýñÏGHÉ*nurÌþ› å’$vã>;?XŒ‡ÈæAäF©®‡—½ëý)°0µ ŒìÐk~ˆ¹y‚²C ÂåÅ\#ñY± ¨P¬~*"î.M}—Ôí{8é圬ÒFÀ2J³Xô¡"B6M{MiÔy1"Û„'†©ýsžÓªõ– ò ü‰+ûa:,3„fJb“Î`›*¶, ”â&a@k@~²_±åT
xb¯Ë\”°×vWŽÊB
ê
« Ëv:!Ûôÿñïg³³ã÷ç?ÕVÍOŽ& "<ß— ø)òG*Ž§gº@ôDàÜÕ]Nú™2@Ž—¢öè—^9YÙÖ*^ª+F/–ÄCTtÎ RÓ¤òÕ«3…õ(r…oUv3Í(zMÎGö¦ÖÅa¯®&¶š0äNòZ.Ûâ®Ò¹îc±h궾í¬(Øþ7*P5Ê–×¥¹Ê®U•¬œ¯ ¡ê“Î*k
UÁPËDá±¥MØ¿z„ÊæFâÔp_`n´O|d…h€aªÓ¦c+(“rŸíã3Õ_’›žE¿Ù{#
måO)ý…ö„šn,ƒ™J‹
¯ô2joNŽç¿±¼Éà'õ}zÓÈ¿³{T^•±< żŽþÔÊÖ²ëÖS”ÎÝ·Nç&®K&= qþ¬'¿ØZ‡óQ©älªq
5ž €wR
nn&ÜÀyS”ùH](A!E§ºOÂåÑÅ =o24rÕa E+ˆ¯)}ÂTéë÷¹t6?ýø„5©Ÿ ‰“V<¡È TE²##ð{W/êÒ¦°>Å 5âäG…jEµ.áWbŒj«ª˜h",ðŠ™À•¥¬îä´‘íH×ÅíY‚FE ¹†œ«‚2 <¥‹5xX7»µµHЗó ˜Lçën¢Ò dß †‚òµ;zÂv%Ò¹mê¨@C7™íØ€
æË~ksÄ`-ó ,N#\jÎC¨Ì*u ÎÅÉEßu{\ó¶‡' }K0¬ÐåÕS¼ÊBñõ|-«Ùìô½¯6óÓµ±g³ÙŽ¨(èš.·ë =¯
ahôsm’÷ý!íÿ‹°ûç>]Un²-zˆm«MžÍ@*c™áOèc~ÈŸëÏožt›¾¯ñ©Ø“ËÒ‚ÌSÆÖQlkŠ»ñÀÉ Å×Îc·EuSše¹¶#¸„ÆâxAÁÍÂÕ=—ôaöÕšïGF…÷jOlHR©y‘4êëhÂTÙX¨Ý¨ÌíïfkÞQféûÝ]2%.·YïÛ‹dŠR= XlH ¶4^ª€;iê9Õ«Ö·zT3:“ºZª¸þ!ùÐ:¢ß^-R¯Ö4æî
lt3 e#ÒÌÇ5ö¢þúõ¦m^ãί«®\]“ÚíjinÊÔ”þYÝÉgjÁ[êWÍ%²mI!Åf£›'ÍñMH«îÕ «So"覄ëÓ3Ý¢”;ž ü_ÿãÜendstream
endobj
105 0 obj
3053
endobj
109 0 obj
<>
stream
xœÝYÛrÓÈ}÷WôòTÜ£nÝÏ›aà Sø$¦
NQ²Ü!šØ’‘dBæøè³v_$Ù˜!œËË©PEZÝû²öÚk7 ™ÏóéÇþ]l'?_&ìC;ñÙ‡ÉljÐ/™ý«Ø²ÇK,HéÁòzb¾,‘,Éžfl¹p?bË»É[¯Ø7›÷*oïß·ª«wÝ;/x7e›rE/¦3ùÜ÷ïE^íó
;¹zúÏåo0#e³ fËõÄç±Hhwï&¯ÖÕ°®fùtùÇdæsÉ–Å$L¹ C²
˽O5½óéEÆSóðW®ÙJ•ÕÖîW¨¢Ó›°&/+êj]ve]ñé,ŠSé-oÊ ÜäÆšLð ‰Í^dOªíùTÖ
úіlü XYiûd˜ñP²™úC¢ë}·oû4!Ï2™xªiqxËêk(®O%ÿg"†Úƒ'¯.ÏçÓ(⾈2ïÕò×÷ó—oôB½Î ÁE hÛ´ø““{6X"¢ rÑR£hÉ4KC±ªT¢³Í‹¦fÝMÞ1$ n6lUÒ/Õ÷-VÜNò*²ÈSóíÊâ‹´…’ÇdW1Až°0pgÜ—SÇ<ðC¯û¢WjK¤àa oKíSµ¦X—ÝLûÈ»¦ÑõòÕFñÞ„»Ææû®Þæ]YÀò{ø°Ñ©ºQ¬®¨Ž}¡m·uKþá+ÅÍîßýÕüÙÓ£ø .„ü^üžÄñ ~50Ç3ïs¡v {œ·eñ ¤pÅT´Qæ,÷rm¥äÑ [(M€r–Çi"ËlšRô_ËÐúYú×ɸxyg}ï¸ \LMÕ
ùت.gíývUo8» ›Ð›OSIÑL/ßì*ùƒ‚i
,ïnðM æØ(ÖîTQ~)È•ý‰[Í®ë¦P†+pò96:".X´kê•¢¥l_ÍÕvMYtjm¶£Ì•×¬ª»3D297››u{¶Ú‚²>›>: þ;o¾^cDzb GzˆN Mf‰<ŽßÅbù~y~…0‚„ÒPè0.ß, {¬¡ôù˜V#W›‘u³¥ÐnjlÞ²]Þä³jè™ПaWÑÓôÙ]¿ŸÛ›zïê²Ò HùOEÚC5۲ʩQ›
ÇŒ’ÖÁK˱)7ÍÚr‹¦rNr³m§ØWçíD1%>Oþ¢˜,ªû¶5Æ/ˆ'ˆ †¤003Hæ`×û
ØôدžÉ 2UFC=·U¤Ó÷½*Bï“c @
´ÄnßBÄ
}ýP-¦™´TBiëâ´·èÐ%ƒðèJh>¤¾ä ÑzHÚ[K«SåúŠu-ÎØ@2ü“Ë®D¢'ï€Yå´ ”î'3CÚ”p kÚ èÏu’/ý‘ú©¥Í»¼¸%ÎH“$ó@Ø RÆ\dcÎ%¢¡½«ýv…‡õ58 mGm^ o¶œ]ÐP¾ÛmpìjcøØ-UÖèæILj"ü5MÓítÙn-;GŸ¿˜/¦\Ê¥^êâÅ8ã#(\,½ÅÕ‹å‚šTWõ¦=RêÜvA ]†nX$ð˜KÒ—u§þÆ^ß”D• ú‡¦b«^ˆt
«ükFE]Ä2BùD}ÊÓÀÜ}¦ •¾e¤¾zFêÀu?"¨µS "4·ùÆ-;JCK£´½'‚D5IºV¹¾¾?©Í5Ú¡ªñBY 9¢ecöü’=™”úãççÏ—o¦BfÞ‰ûþ¾V~¿põnî?BU_3QpXíòýã§ó˧‡%6 ‘别,úþˆ@á›3ë+à"IÅ°©ÇÓ 2ØsºþDÜØc•7î¼(TÛº†šÚ ¤-|[ LûÀo0ÈÀ[ Lí¡¹˜Ô’Ój¯º ó{Ø_L
‡Âu’iºëòo–D<‰q¢„$—¾8YBCÇI1ÕØyÁ]iP´Ltèþ¿ýR7基ÜMt¤B ‡¨<£ŽƒéÕ5¶ ¼ ‚¾¾!¹ôÿs…º®Ôà
ôí¨¡Hì¸áÈ¿
ç‰ñL
E¤Ì‡Aˆ¸/¤ gO—“àç_†C¾endstream
endobj
110 0 obj
2720
endobj
114 0 obj
<>
stream
xœYÛrÛÈ}çWÌÛ‚‰ˆÅ îΓVæfµ%KE×&e¥\9"ƒ ÍÕ~ƒóÏ9=7”œÊ¦\e‰à`¦§ûôéÓ_YàsÐ?ósµ›|¿HÙ¦›l3ùuÂÕ—ÌüXíØK,ÈèÁòi¢ßá,,ÍC?ËÙr7á"ôƒ˜-“ÞêÐVŸdÑ=êdßìû/|˜²ª|¤/¦3~¤Þ»¢>{uõôŸËŸ'8`&l¹ž?BÚÜ»mzù†-·’ :Ù²ºØ©ßÖ¬oØFÖ²-zÉz|ýƒ,Z,XN—ÿš‘úQ˜Âjìå5ŸéYîçú3í-ÔÞ²fݶ9Tkö(YwØï«) ÚÞù~Áë„0öÃP˜-¯>,f´`¦ÂO’œÍ¸ />z7wï—Ÿ>ÜÏ·Sð8ò.ßÍÕõf!öÊ3kß¾/›Ú×æXâç1šñgFØ;ñ3Z(«Z.ß3œr}w{¯ß±ÛÂwÎX¨L¹œÆ‘Ÿç"õ>,§<óîó ç‹ùBY4 pÔêäMï}A›ô4÷³XÛøqžªÓ»Žl_´ˆCw#„ Nÿɺx¬(eç³_¶ð®~²¾°X`DzªXqè›]Ñ—«¢ªžõˆßB>Iðr«:ÙXh}•ˆSY³Vþz]ß±ãëYÙ³§¦ªš©À53xûHÞ4«‚œúË×e+W½¯/¬.jÜyê¤0×Nººšãóüöêîíõí_Õ;ƒoà(Q^¸—0€¬^5u/k|hžÔçËÕJîûÙ¼^5ë²Þ¼a[Y¬•Ÿêž¬/˜
Ÿ¹Ä+êµñRÇÖR¿„½ˆý$J) tøÍÄ+Úéw:.@HÄSaCÃ# Ù훺“ä:èJ›öÒ–²Ãù+Y*O[ˆ@ø"¶øþ"O@ ²<‹lî$Q¦[ûHÊVªuaæ'<ÌÉLvésV§WÓörýæ<±pp.Ìþ^¹†Éeÿ|ìÀ|}¡“,åùIXrÐÇm¹Ú²ugÖ
pXo.ÎNCæåAl˜À[˃>Æg‰ÜãÁ·9×ðÓ[;ðQ¬ÁG_¦<·å™¿"VÍnßJäHÙ““M@ E•^ù ‰ÀŠjÓÌ4 9áõl¸IªñÕ–ýv§Ðqfû< ¸±ó{¹ [ÏãáûWŒ¦W”êE: µŸEÜ^9MÔ•½ë'€èwÙ6³JÖ›~˺¾¥{ >ÈÙ Ú
0«-äUdçð/ ¥®÷€”4EYÓf €l€Œ:¤î•} ðÃb å%†C!ÚdJÓbû¿ ÁùnÂîó›il +vÅ3^P?èõuƒ ùÓYœÂÅ\ ¢™™í]¯J¨êÁC˜‹Z…O +Yg?l‚¾O±™$‘>²nêÙ퇛öe* hŠê Q)a…¬€³mèszypÅqb÷?¸œäj‰‰v\•§ ÄujÉ ŸÇ@E¤=M å¦n@>»—º|v{¹*‹ÊÀRd>ãÓ(~µ½ß/æ—oßÍ}wЬ_KijêT´–úè=ŒÜwœ‚°P s¯è‘>ì´Ìk™îÅF’¥¾à~bôÀˆ Y/—·÷¨aKt€z¬<~¹^Ÿ DYj&,§¡©ŒmQw(>Ì•ˆš|Ò úMCŸO9Ûg×OƒWuÈü(r Ã-!Ûȳd°1R6züN•LU
º¾ìP°º ªl«¢6,²FéD
Ò¹ÆÃ-ª°h‚)Æ·S^!,G'æžS" *•3ëe½êդőE¯ë62`\ºõÉÀšòM
Ì kPeBUe¼¥+b¹ uÅ3–©l÷…c°Ø‘ÉXWÇغ|Ò”† ^STåfÛà §¶Ù) ×>öÜ XÑ}V OA–Û¦~’¿wÜ ÈÌh;ªø5™pÂÁJ*:8¨ô÷¤àÉBG&1˜ãÚ“»§~œ¶Ö‚|WtÇ,j¥¹º
]·?Ùc&ªŽÔâX[@øê·‡Ž½ûp¿¤·•Þ ÈéÔ£ÖE_ \·cmÀóUg¬
HýG/ôÁG¯+§a“>ñê^9&Ðòv¤Vñ’p‚Ö¿o$~ 2î ². :„1{TH› øEƒ{.– r?ä"ÿ&Î#
ÞEâ§?Ó—[Ó£”Äö¨™qÕg¨´t
(„²ÐI¨ï 3W=ÐDK¬ä§E'èL$•zuüöÝ·´èw77wŽš~¹¹»ºœr*HÐûºêø ÃX´_î_D~–f®šƒvuô_*vYUZ oÛ¢}¦ÇZKkõIob¿D€ ¬ÓÅ Ÿ»Ã"sXýÌnƒH æç}ôœD7ª@¥ÇXWE¹§µ3ñxGmGOâX{A ´#ÈÂÁÝ+~:õwp1Q¦(éó\_d:»zFrc=á~ ¦ƒÜ ¬ëÇ/¶rF&jÛ©?µ§Ñe¤V ùA¨ä¼€MK|ÇêÔ^,±Y`Ü£Àå¢B+Z›RG9W›¨ •¿8‘+î„Y˜ExŸèMjÇÜœ…£SÒŒÌ×å›bQå÷e½ÄvõH·¾¥›÷‡¶†®0”èt«È EéÀ°
ëï.ÿ¾˜¿½^œõ±3»zT‘¨>ÍUîJ Œú°{LÐÙf¯7œÎ}ðP¢»Yh9úƒƒÌDZ±nøÊzEê”
í,™¤í82ömÓ7«¦"ùÿZ«ûŠ P‹¡ =¯f꣡E›>"Œ\n–àÚ…ÒÝp†;V /ÄgÕ\u`²×¥ï¬£È\%²aQ1ùô~aLÕ4 SÊ«u3Xª%ÎÝ’Ý
†Â5³R+|ÒË'ÖRKÔ'°Ö4õ*± )©:Ùàå}º¢Òw¹™.Æ¡
‡§9 %vÊ虊×Ê' ¼Ñ ýæÔȬ"MÇX¥™CÏ´M3®z`¡¬¿Öe¯Š¹%Áké™øè½(ôfÈUj
6EBŠÄ$¼¿Cy $ý¡¤çÔܹœ,û 5–jøW÷-jնљœ…Ú™ýËÃHìÑ÷nPg¼[ÐT÷l¯W>
stream
xœ•YÛrÓJ}ÏWtñr䩸QwëÊ[„§2„ NQ ™J)¶‚5Ø–Ñãù†ùèY»o’„9P!²ÔÚ—µ×^{û ¹`!ý±?çë“çW)ûÒž„ìËÉ·¡?döÇ|Í~Ÿá†Œ.ÌîOÌ3‚¥’¥¹âYÎfë!c6Û|æ}³º-‹vÛ–]½ínu3a«êŽ>˜Le ò0Lƒ¿›¾X±Gïžüköç ^0U ›-NB G) 4e»-ç »zýR&"y.B®¸dÅfÁ6uÇæõf2û÷ÉžÁ˜ù‰ˆ2 EìÅ)Á÷’> 郜Ë,Ï"óÁç éØûË3Ö”ßú²íZVmºšýq>º²[–v_¯VõDÆp Ï‚]µùÂ
¦B¡íŠ8å©ÊØTH:Vq_ŒÕ‹ªÙU½áìCÙuxLÉ$ÏUœ+BžØÛïªñ½ ¾Ó=2ç¹H¬Åª×><¿Ê]6ržæÎÁ—×W·Wç¯Þ^Ý’;·*”t·5d>N¢Hx’ÚÇn&k qéV|¥ë9WÊÇ*([—J¶.&ücݲtÒá—) } £\iÏÖe·¬¬¸ïÊFGN2¸Zµ kMxAº ˆ<çažþ,
q¬ò'à t$Õ诇! ýÄ|Š´OC@´ï*Îx’DÎwÁãÄ@÷±h±Q> œÍp£Á€Bᣧܗ!Oe"ŸpÿìâÂÜî½– —¹Å˜h«–Æ…,䙌 ÁêâˆÍÿ«ªP º©Êͼd‹ò¿›ž:ÁxÑj…ßš²¤<·Ü Fq%‘ä©ŒŒai.
£P 6õfŠªgw岘 ßyGÁ÷ªîÃû»ê[_uuO¥Ëvå »kL¡Š( vmÙ´§¬u쑦hölQ#utüÓì T±ä‘/º§ $
¬›•Íîö&z > ½Ey¯!,‹¿¡«–8áq樟ªåòýìöõåÅÅåD÷&PûÇ‹Ë—g•â·$ fo/ßi„ŒjH%ȇƒÁ/HŽÇƒñY–ôÞg‹E¹ `¦ ùè†7ÁØþÝD„AѲ¯›Z¿F$hjît:ɤb‡˜µÌLÁCëaý–bŠcA‘ô9xSG í·SV{š³LŸµ›6üéüÜ íüâ΄gžKôË®g¦“Ħ@xŸmÒŒy:†¸AÑ`9€Ù Kñ²rµjJ—û¶dof³÷ ¯¢ß»¦Ø´÷xlQt…áBú k—u¿Z€è<ãŸ}³hWuË㔣<<¶½SWçg¯^ÙP)y÷Þƒàl6¸†,¸«‡d
¶áÐ 7‹£W#”¹:èÐôê·ï^¿½8ÿðöŸçGÔ Bë$°’
‰M +*]Þ–*`QnQ e•äPÛn¤´A¢%ÊQ•š¬€0Û×½‹hµë J„ź÷A¥D^# °ÜeøÏvíú=ÕQ‚ŽDpöê¨n’ Ü Ž#\| u€¸éÜqšÿwi Ì•KH÷R€þ"òµæD(øÒ¯ŠÆÀp[·e™]…nU¬Zbé¯ÚŸÁ ²YxmÔ:™äZöè…^íR¢è¾©Šz¯Î x6ø%ˆ«mÐë
zB7Õñˆ€Wz~¦ í·å Vl·«
(@ŽŸÿ˜îv»é}ݬ§P'è(5hè["ˆq2¤ `Srx žm 8ü½Û³{0–aJÄ‹â¹F¸Ð»Ökâ ÓMe3hÞ/ íås3Ñ l_Ài¥È5È †`¨ï'¿A®‰ãZ¢ã^¿=¿xõḖr )§îêæ¸0ÁPè‹G‡½¼|ÿéÉPíT(k„)Á– DÃIuOݧ0Ü…ËE”j0•&YšËðÁŒ=d
TVIù¤§‰Z'ó
顳@lüÓãn/ήþ8>4‘H²ôrGšvLŽZî%
Ȳì0Éçêê?¥Îop©cÕ·GB1bèq$Bl”gåÓýøéHŠ¤™0
²š¶…´#:RB.ìË`•VßëÁ†c©à*¬*ÓyV÷p:\Íêº@g M½~ ï“~;Byœ>6” V_šò0Šœi4Žž’Ô0ÃeßÕk mÔ9öˆ-©G‚{É»Ëß/_M"Û*? ÚD~)NžÄN½‡ì&
Î-ïÄ=ÅS-ICÚQé „ZsŽ˜ jÛÞïòÜ›ö
Zrî’RøbJ#Û ìšó«]ŧ‘ 2¿X(‹7Þ‘6îà@BßÇxuÏZ ÷°`ªGÊe±1CBï
[oÌ·ºš«r¤öJ³A9ÿ ¹êLÜõÉ3:$Ð’™Ùkå<óƒÃn(P‘réW;6 ú£±ò(‡YÄ¿:ýË9ŒG«GÆ:øfù£Ý3É vODð”±–£=˜¸!‘UŠÆ¬q œvUÉü‰EÍ ü‡=ú°®y_Œh-ócLZ®…š+Øw£ï1ÖÕÕ‚ý¶™[·ÄqjBÍyáñqºRÏýP¦7Û ß²š/G‹CÊñ}²;ÂõFÚl Ûõ¶l
£fu/—Ôk À–Öq6ŒÇz›]¤—ÌÜã©‹4Pîm±Ý_éù‹¾2ñCÚ
sŠÎínwš+Ó’m¯Á=º°±“5éaûgðó²:üÊC&JÏK.nÆGV ìÙd– ÙtÜ#¨É ó¢ŽN†@ ˆ%Šy2¯»D²ízÏ”¼Dïuc¢øs<•*R’º2æA…úv3q õ·|糓àÏÿ 2ë "endstream
endobj
120 0 obj
3136
endobj
124 0 obj
<>
stream
xœÝYÛ’Û6}×W`ý*5‚IðÂûd;ÎÆ©‰íµåÚòÚ[.Í0C‘2IEQ¾Á ½§ð¢‹//û²5U ó »OŸ>Ýó‰ù<`>ý¸ßùföðµd·íÌg·³O³À "î‡*Å9èé š úô@q‘ª4²|{ž¦cuÃt•×+ÍŠŽqu¨wœýV· ÛëÖêæ9ÖTi yºiÙ¾(K–µín£YwW´l•uëjv£Î»°‹¸9綇BI¶‘Ù–GaH[{Ë;ͶuQuzeWÈÍ^¼¤Ó
®è%˜âÃ(%œ)Ë|0%y”
g#)Ìšõ¶Àj7œK“S›¬9<ÂYYÆà¥VÚápúŠ ÷û³œ<
g¼ÃfÜ'æ2}ðÞÛÁ'°rÛhë•ÁR©7ìiM}Á>Zbð´—geYT·,ÛnË"Ϻ¢®Ø®êŠÒœµk²ª]ë†}®ŠöN·Ü »ž<°àÇàìW/ß,YAUu³F& >üs±ßïˆáfH¸@°û¢Z±^† Ðl )lžuìi]-æ?Ìè¸×3¯ÓU·Xâ¡K ù}Þ8¦ú
¥'°¬<çYÕ;Üz™Ò796ÇСÝÌœöøC?8Yô˳Ç?={}N!}ô2"Wˆî bHm¤O’>ßá^ßFzY³±Ê ÁQƆ…î
¯Si³˜"p÷˜Ò“Ú˜ Ê¥ªtìVóÛ¬é 3› oAï- ûŒ½þù©ÓtaîQ!Èït~Ïê]w¹I
Å‘¸às¶[v Š®gKŽuFHAHÈ#_c“p ¢ ´tGZŒ"e%”ãE²hB6Ýz‰ H8™p“¥%‘!¡ ¡"ËP¯?xƒø|Í·k´YÆ,Ùé+§.Ü1FªŠÄ-Wi7N©P-åì__(ÄÆ6B9ûzW‚1nŠ
¢ÉìÚWéÇhöEkÂcE‚óòÇ÷ V*‹û¹µ‹JÈP*[7²¢äìùÚîNVÐÞFxÔ°àj*Ô,³P¢ ;ãÖÈm¾v¢òÛýxýøõ?Ž‹Ä_ïU6¡Ì4î!,|iCÚÅHâ»^Ï´¯
•·þØQ) ¶³î@t”Ò•½X½$P¾od¶Uo0Ë‘î©p O"ùÝzÂça_3É‹`‡H—’¬í½ {\VÄ÷”4(N÷=†×M½ Ö“àÕÕˆ`Xüù–0íR݆“Mëd`™5&Ïü„Çr²[hƒr«ÙçR3›SA”P3B`Fˆ,(D
òŒó.84‚š ü"LÕDÄ9i˜zZ›=^‘¶.*eŠjƒ¾Œ|Ȉº¾st>}ùêÝq辘ÐMQbv·¸¼Ëöã1 ‹ •âq2XyµŸ"ÒhÔu‘Õu&Ç[PS¹"Ê H a3ä ;3[YM¡·ºÉ¬'žwÖp‘8 Eé¾ËŽÑ•òd,m]!•8Cò/›‡1î¡×v&º}
†Jt ]tÙái±øZ¶ˆdP)¾“ð^±[xO^±šÐÁ·nŠ[Pe9ö®ù¥îÓPfJvöÔpeSQÙ¾i*PJʲž‹ØÛ;UtÔ-"µEúàR’"Ñ·d`³oŠN_:ôÐé5í´>pQjzé€\¬Þz¢óŒXúÄp”rºè+OgeD >4д†¥Ô#Ó öúoRš*jÕßU¹¹¼ ‘~ˆ'ž6EáyWô¥ÜöcöÐŽ4§» ‡÷¿Jc‰ y*ÕI KÞ“ñ{ïÑóy˜‚{Uâ'x¿í 9Ç*¨¾(Ü!Å«š¼ O¹& 2Ç’Q»Ç±ýjÛè",ÓO[ÈA”§†œ³ŸÚÂaÛn/(B?òpD‚mVn”Qo³ Æ6À\7´wD™påËQÆø©µC—kÛÕ
}dDCeúü#¹Ýô¥ÄìoºÑ¼ÞY5L:öILªˆö}!\í6;€¿ì$(N•«2Q=KU'<(^X¤:°Éd
Ä/Çwz«²ÖŽ¬9”$´hWeM:1i˶;q}u '˜T=‰lš¢L†ß lˆ¬øj`wãÙÍþƒ¢ +4(<•Ñ'‡ ÌÃè{[ßœg(¥×ègI‡¶%“¨ÃjÂòW#\WqÏ,™Ñ&v K4„‹²¨îÝ,]ò0#tÓLMÓHÔ
H_£´ïºnk¤†5ª=8±ù’¦ æK|9•7Iâ‹‘–ÐD®6$1&Ó )¦Ô4ä¦f%•Ry™i^òFƒX»ƒ,Ê̯˜•ì¨z2SÄRô©dì Øe«• Õ a5Q4o ü ¥pÔ åœƒ7iNŠØZáz6ã¥1„@<’ðD84z“T<» x°seÓÜ•ußr ‚NVÐÐÙí<4WdO Ôö fþ‘—:«vÛ Ö¡¾
qC&aœ> þÿó‹ÿ‹Íñ †Ða©Áôî—玀^àǧ¥}ÊZ!òd¸H—¨A™\óˆJ…×í'B; +›¿÷ìºz J“¸Ã…‰-$®á°l˜/Ÿ¼üi ù¶a{ç@6œEpl>™…úè«€ŽÜ…#F1 ‡² ̈¶Ãè/`ÒQ¶
U϶ "6teÝšCÚž2‚_§/ œfÂì‡(+Bö_ˆˆî=[Îþ‰Ÿÿ”UŠendstream
endobj
125 0 obj
2785
endobj
129 0 obj
<>
stream
xœÅYÛnÛH}×W4übj!wؼ3Á<8Yeâ'ÎÚÊ{aÐRÛâE*¼Äãý†|ôžê IÉvv=û° ±É꺞:UùÊ\.˜Kÿ™¿ËÍäÕyÌËî&_'B 2óg¹aox!¡‹Û‰þF°Øcqêó$e‹ÍDx>wC¶¸Ÿ\:Ë®.®eÖ<\7²¶í•ã_MY‘ßÐÁôÈ ]ó1+»¬`O¾=ýÇâ—‰ ±#ü¿XMœw_ÎOÏ>/®Ïçïççóóé⟓#h —ê5á©×>gtâÒÓ”'!ÔÄS—{QJš9MÃ2¶ò²•5k+üø—¬+†_›¼ÌZ¹bM[çå ˶Íêl#qD= “ˆåÄsî ¡;üÄ Æt–ð0Mßœµ÷½*B}žöÚÄJ™¼(Ød]ƒk¡ ŒgíZ²sy+kY¿fk™ f^*c=?åo
u¹ k“è“uÛnY-¿v²i!§lI ÔrSµêo$D„1÷\« µ,‰•e8iêY˃ö‚I*¬ö~œè(¯ó†-³rlÃmUú6"Äi‚KVÕ¬YÖù¶m8ûm*¢/œªS gES©X ‰8ä)¬³ê€Á)Y©õT±öK£ üOYê…¡
ês“îpS«MiJßÇÉŠW#O…EË:mq!½÷rÕ¦3{”´(»$éÓóÿ˜·iÀC}ê>#ãÀšzƒÇ[äåïSá:ð~‘#âÕ-£kŒ}
½´ÍšÆ&Š %¦ùˆq4ÜšØP =T]ŘDâl±–Ú¸
(4V÷+ÐãAäš ú<°[½šuÕ+Ê”ŒÝvEñÀ¾M=ƒ^Y‘÷Ú+å^§Ö½qÀcß¨é »e«[YC ìÆÐ{‰Øy•[W[YãÂïEmò’S±í `*7[»†;®³íV–+Ý/wîCz¦ÖdÁÝØ×¢bËZ>”ÕYY¹Ú»/IxàÚ:º ßv[O}ÈM=Ï‘ò:+Š¡QnN¨ÃXKéÆB¢.º-®b¨ù¼Ö7svrKÑ4xês\i,D!ÇB)œVŠ)ˆvµ e]Aùú>o$ÉZ¡!ÌÐu~ó`iS©XBͺÃG
òRtÛÍœÙÀÄ}g§<ÃõY•Å¨°Q×¾€O µÏC
êþ¼lZ¨kc;PI³.© àà”><^.å¶}}È® ®²6Ãó»54_IªžV':]{J %vª¢*¯¦3õÅ`´öG3ô¿,ò&»A²QÙtÍ /Qi .Á¼òJU˜nÌм”ÓC‚^º‰ÐÀï{ïýzð[ p‹íî;ÒnŠÀO2¸)cg(Þm‘-u{P @R;Ø!<ìùG*´ oø|P½-q{@Ì;{âaµÎ!T.Ä ÷¯Çöâ è%öàG1¤˜µkm²Gz&ÁnWPþž'ëc‡`©·U½a‡ >¨ÛÞèœ0‹R'aÜäæ;…ê„g§T4†;,¨Õwæå²èV*/MÍ'èù<îI‡šÈ¨Û ÁÄ– ñÝùéû£vÌðl™‘²ªÄ#zE™o¤öO„Úì–z‚Ì–ëžÒ¶rÃÙ{McßÉò¢.ZT›-rWyYe¥ÊÜZ6]Ñ’€Î¬¼“ìf*Rž&aàtwM¯ÔN ñ Šv¹î‘y6Ð¥£®ØT0ºÈ©ci$ÔÈïÊ
zaµ6bÖ³T&ÍV.óï(&u p6 "ð½VòJÊqd¥=W%N–—ºì$s[W+J€NUmÆ~ž/ˆ„|>»X`h‚ (}þ` ‘}ñ—Kb &f¦¸V‹›³³w˜L
Ò(ª©G¬ Žà£”ÑöHéŸÕr¨Ÿãå %jü€tmDo®zf{¾u˜òrE×ëX©NnÝ¢èfI8NãÎ!•¾§ˆ@;ŠM¿9ˆ ¡
l—¢6/š¢U^ð]î}ä{1'v@åò ŸÑ,æÓ—ÓS]²¹b'È> çM¶ü~Qí‰Z£©•b„¡ 2Aeòz£Œïƒcý²Îv±.
@u-ŽF°î` 'pOቼš™a]Õí²k›[í:èÍ^ƒ.œëÆ{,òÝÙÙ¯'óG,"êÇVg¶'ˆK2HŽÅ}4ŒØ–Ø¥3šŒüpŠF·Ä< ä<&$0wÄ‘ŸØ ¢ÐÚi:Øå¼>M¸Ïp^ÏuOOŽ/æ/ä½A>3¨YÚ™€ÅºC×
Òh—v¢4À.³Fª CÙ¶ŠšˆìPÅw¡*eâ•È¹£0HyäÎEµ“çxž$=ê5ö4ºÑò@õµÀ•ÆÛl7±ûÛT]óÝ,%ëb;8¾¯Ìˆ–êÖå¸.÷‘3}⦆‰ÿ‘ôåŒ,å»L͆´@0uL5²£æÁÉ»ßȺ¾A6^=Í · ”£³_8{«è] hN¼¡¦"Ó˜©7öij;cìÅhfpÑxÄðÁqÌ2¦KŸFºx¸K¯zú0êp„´*Û› Ó†6 z%d Ð'¯ ½Š¾²èÊ9^™† sr¨¦þš °µqԶ߫}KýpàQ
ìÞM{?yfˆ Ï@ìÑœcžÀADÝ óñP£õC†fŸ˜r0Ø*o½hÊ yâÛyØ}Áˆ÷÷ˆò'F 8¾¿öG#Ž!…ÑÐ"Oô}Ae¨P#‹[ÛæÁ4ˆµƒš¨ª'4˶yµ ¾©j:Œ-¨"ñ:™Ñ¯ßÊÛJ©£g"h qÆNÍo½2Jž§ÖA<²¢3Oœr€Dq:ì—s¸t›Ùï £` µ)Ÿ¯ÿ>?¿89û¤ÍK#(ãµEÊ›(³›ñlØQâ–QÉ*TЖ)[m†LNÍš¦Û¨ý¦¨I
xÜ-¼MÖ¢ÚÆR¥Ý¯eÉÔ&‡Â£‰áé=×mdhœ/h ±™Ýþôžð«‡2¶<=Øê}´¯÷Ýt%zˆk9^H«WÄ NúÜFM¡ª~Ïåx‰§óŠtÈŠ(IMO3jžÉzòlŒ è“Þ÷ùhý¶"JÌ~ùøãü§wgŸ 3ŠKM ø¡F3œR€õEš-²¶âŽSødÅÑ—÷´O>·Z~®"ŽaS÷
3Í—rpÌIŽ¶e> î¿Ù¤QaxxÆèOai™Ò§Å®¶ –Ò“ùz`%AŸ%2¡4˜¦%"´–0µ[9»xBþUízšpiKœ¨VíÇÄ -v´;+@ä°L5‹ÞDð0ØpÈ»â'3‹7Œ~{ö·÷æ€Év¹;©ŠÈ à°v€ÃÆÁ´ „"Dk£~\º§þ±-òeÞÒ˜fèn×ÞUd¤ÉÀ+§ÁˆL›˜Þ)椡¡F‚‘½;®Èc«NM¤YÙ uzÎF#±“{IûŠ ©¸¶Z 盼ÈjÍÇÌ¿Z «„ÖϳÁÏ ¾‰ëZPÓû ó U?á8£ÚÅ”=\*ÙÌ,w1þ£ÕªZ^è
@@ ñ'1ÛQÛ<Ѓñ?° P|ßb†øeœþ°ÄBz®Ð bî÷ì:ÁñBz6_Lþ†ÿþ
ûójendstream
endobj
130 0 obj
2866
endobj
134 0 obj
<>
stream
xœYkSãFýî_ÑÅ—È)¬¨[ïý6’!Kv0›Ú‚)Yn@ƒ,9’Œãü†üè=· z2•Ù¢f «uûö}œsnóó\Î<ú2ßóÍì‡O1{hg {˜ý6ãê!3ßò
{»Ä‚„>XÞÏô;œÅ‚Å©ï&)[nf\ø®²å~vë仦ü,³öð¹•]½íî ÿnÎÊbEæ z®çÅÎ/YµËJöêêù—?Ï°ÁÂØr
·`عi‹êuEË°®¨+¶Ù•]±-%ëŠlÙ¾(KVWåm²§ùòËL¸p)Ÿñ$r“NÔ#;zâÑç©ó4æÁ£deÖɶcm×ÐN5-\ HÊHºQâq³øYŽ¬ˆ$MýàÖišb
‡`mÛȹqÖ4qž‹z·+Ùºêl ß‹Ý0b ×”Åw7Ÿ..¯–Ÿß]^þóüìÇó‹³Éö>jåU6Ú; õÆÜõ¹¯ÂÔ¶,cÛº¨:Ù°®Æ/ȦfømST8àÚž/kÙ6k²Ä#²ˆ\’‰|&xìF^lOäžÏýö½ÀéZå½Ú[À5&6zõ®\³¼®º¬¨Ôñ+Xfõ=;Ô»†ýYª€-D€c'¾=‹‡_"åõc]®É©¼®Ÿ
ÉÖY—‘óÌÖ.[ÂÜøÁ&;°•dØè£ìÚ<ÛJöû¥þùÏ& ïëf“u¬Vç£-/t--¿¿u¾ìj¤ˆSŠbßyØ•YÃ>,—W‹¶; ¨ ±·lZ¶Þm¶ˆš
%Ρ(2æüTÌ¿’„‚
'â»±ç¿R$U6÷c!õJŽBaY˜ÚŒ
Ogt³í8«êj¡Ì†‰›òhX&Բߋ¶£ÂGZ½: ½éɤ²bR眜ÜÍO'ͤºGVÙʤŠ{+1¤ÊG²i à–‚«
P ³Ç¬Z—ò”Zv(:¶«(| >gôµÖJ<—Ť²E¸|ÚWe¼›³ÎûÂç©=ãm‚“Vl‡}öüq¡k.Aëb±=ˆ:ÄPk-ÕÑý®Û5äÝo; š”ê…êB->WU¬ìþ5üœª5ªª²õšmjØC*Ú¾ŒQ)"¨ˆØfÎótñ_ïV-í\uú
•
Ñî›w&î+ëÆåì Éíšü<<]äo>iøù»°‚u^2À
•–êk`Gþˆvùþô]¨[ s„ †#O¥SÀˆ°i“åxC‘p1ì™j*ÑœÁöMÑaOXT¨Vá§{ªê¹Ü4õ„³¯T0úp"Сí+7ˆt
j‡v+óâO´5 iª!_~øÄ=Ërm·®wË^òsV¶µ”Vc
!—ŸÇIü:¦´ÐU#°Pèö£g
xœL#ë0ò{¶¡f¼¯Ë²ÖeÓ“|Á‘Df¹³Ï†²…y\Ø”Õy¦¼tM«×˜‰#×óãÔVïfˆ¥Ñ¶CÀ3F—8>*Jð) Ý:-5}–çuCôW æ‘¡#M3 Œ",u
~ɧ¢Æªï€+È(-ƒ+–nn5Pc Dæ#š Ç•ª«‡c”Ó;‡z‚v<î Ÿ»a¯™þV_p7Åq[€}tTÂÐõ£>*ÂMM6KÛû”Šªî¼ã¸ôc#·uCŸ0Ù4pÜV©Á#—EÄ] Øü[dü÷Ù§·—×gG¾Æ€Ú>“Z6L‰42¤ùÅpÃn eÿýÙÛ9§ú
Sçæ§ o>¾[ž_~TIii”Žo¥)*YóÍ£Âäˆ¬©TƒÕl]´Û2;h!¢ÈR¦
«?NWCyª÷Í绑‚$B"¨œ”Z~.ÚbE#åz•åOÔmšz| ó¨]Ub”[«Z‚•mÝÒÛVJ.Y[t;ÕG/i鈕®Ï®¯)$ß"s¡B1ðQY# ˜((œþÛdÍ“ö+£ç••¨vk°Ôï> ã]è
üãÓò½ìÄ`Ñ Ü@
.—v¤QXûP#Ei"Rh“‚êÅ.5Ž¡5 *&5N’ufˆ ì–DNØ}So†©‚hOÄfª0k]ööÀÖò^× Z>ƒ<9íç.…&J;@@-ZªA|
CÐ~:‡¿ÑÀž¯9à€
;œUë-r»í]
* û¶ÿØŠ{ !Å|¥ F.ï‰õ0Ù/“•ØQ ´Ï\O?ו*@×#±ªãœ5#Â*ºGŠ5?¢—„óû¶h4'H+ MCišÉ$éënú½ôÄ ŸJáŠò?Õ¶QŠ³z=ú–iGæ@e~¿B»
gôXÔêU}ÏŒ}9ªæÕ|l›¹R@†`6ù«ž»8¿^~cÃɨá´èÓ³¡"=R¸ìþM‘7æÏ×G´~,cv£Y‰&lÏVMc^CH2šC"íЋQ
¬u-»…vä ÌuÝ»¹ÙK©° ¡°^Ëꡨ °Tm&˜&¢¤ÏR¤» Bd£õ˺—£É¾Ø»†Œi¡ÙµÓÜIÐq"Ð ¯ÆÝѓͺEn經7'Æ&kå¸ó¬ªÄRA¯Ž< UI!…ÀEœÞ¬×t¤ÊL)j(á”Е
lÀl† ^© #ÑO§¡¦Ë†!S©j"ã.AüÉè^fpú¸¹{5 ò±«æ²ÄìÜÇ95#ïp_Q'Ö׉÷1Hõ ýUW¼¸¹þ`| æîéaø‡>Кí&®â—o/ßÏO ó?G²#ÁPÚÏ#>2 éè»^0Èjkûæêâr óþØ6 èe‹îDl ˜ ”ükìHa¡‘àÿ¤!7“œ-ÿS«HëJ]€RZŸzÃY‰š€Nkó¦X*Ȳ¶w2‘V ˜B†;¢D“ÑÞeË¡îIBõ©}4W yev¸ ¿.ÖmçXÈê;.‹Z¹êÓI@P¡÷iùË›p ú†@¾5wB…&TŒ¼zÞ I;V%¸@MøÇ7 ͆/Å{&xߧò ¢}M÷m@0scÆ:Êù$á¨Öö¶=™&»R~•l=¾6‡?Ô˜ÀGkðÉySØù(4£?5ŒÔ©Öÿ{ÒýÏýM´TQÓZ¬š¬!€ˆâd&¦LÑ‹rz£GéñmkÙëÔðµ?T¨IE2N×
H†0Etimj«¨žZögg†9ºIùj$ùgOk¹¾>Î*=,)Àç®7½c}9 Ûã_·ÇìÑuå"Æ
ÐP4Š… uø¾MÿyÒ%CkAË
ë} sýõ¾ˆè³³åì_øú ‚tendstream
endobj
135 0 obj
2849
endobj
139 0 obj
<>
stream
xœ¥XkoÛ8ýî_AôKå…Í©7°X ›IÚ Ò$ëªû@³h‰¶5•%W’“ñü†üè½—IvìtmÑ6"y_çž{ÈïÄ¥Œ¸øËüm'?-"²n'.YO¾O˜úHÌ_Ù–ü5…1þ ]Mô F"N¢Ä£qBÒí„qºIŸ&_lß”R´‡‡Vvõ®»w¼û))‹%~˜ÎyàRלO¢Ú‹’¼ºzúïô—‰’9üIó‰sþeq}{—>\}¸¹]\<œßÞ¤7éÃõÅ͇ôã4ýUe ׺4â q®ÖUÝHÒm$9¯«NVÝüZVënC6Rä²Qû(ÇÕÙ„yõY‘¡=šâGW}`4ö¸ùù¦h üÞ·rµ/ɪnÈÙNd`€ÑßȽ#ªœ´Å¶(ECZÙ<â!,¨gFç<åœlZHÊÓ¦È6ä©(K\:÷<Ÿ¡?„âF±ZÝÈ]Ýt¤¨²ºidÖ‘LDJ zò\Ê–Ôê (l |9
ÜØ8ÿ(ñ#üÍ& åqûæcÃ×CÈ1õã 1_
õ!¢‘çöG‰å¡“-%W+H/$êVÔ•IM>SEUa‘ªîÈR±,•õ9Kbê²QˆÜUˆ]MDûD'Ë1ïšzÝȶL:ò»ƒ-`E•6W!sžÐˆù6ËÜ4Ÿª²°s#+µZU…ù4I\5 ²Ê[õZÉl®€7·§Y'µƒ!Å"ç¹Ì¡$¢p°ªÒ! C ÁõcšÞõ`ýùâüöç«›Gpë܉¾ J …@ómK)ëjM S£ÒvÙÔÉ.®„ê¹>"“
È@7õÜ€&.sj¡ÂS&x 'Gñ`E
u´èÊeVçEµV…†öDӿ˦ž½X¡k³45ö!¼˜55æó¢E äãã):Ĭ̧k•h<``¥êË8u{oCéòŠ}Ù½ôe9åH1~âì;@Ò÷}"‡z * ?-˜kmnN7þ~íëw6 @0çüüþqcJ¨èÑG@çT¤ØÝFt§x )7xa±‹{ÞÀLº8»ù|y±ø_AãûÞ
§ ®Ô q- hxâSÏõOAãñ ¬ðhºFTí
zêmÔ¼Xr ()QãºÊ73R¼…È3"…©Ñâ)\ÜOi m^ ²Í¾úÖ/=/ÝY ˆ=†ù¡†×¾bmUСkKǼ7Šóõ¢¿À$ š
s ÿó§ôŽ@õ¯no>c.l
µ `ùéìêúár1õÑÍ qn?iÚúãøà^0àcWÐ@
º/T €”f[TÀÄ0κ͸ØÊNÏMã@Ùânܼ:7=ßO‹¾²ˆYk7õ¾Ìq,à´@»íNfÅê`(º‚áü^ÍÎX :&Ú„S64«.†ÜŠ¢$t šíñô\¥V}~*`RDP„¯ÊI=-œ³ŠÔM±ÆÈ¡Ï |V¾>Ë\Ÿ'ª5ÂoÙˆìÔ˜‡ L\¯§U_ÓªìZ ÅŸÿ#_4õ fYÑÍÌôLÃT±Ù݃”aÚ3ksf†h€^-ÄWM½%ZqÀ)ñùˆ…º@r X#Êõ¡cŸ¦Hn® 9¢Éa˜_NY i/4gÀ V?Ånx,rˆ~.ëhs ?úV A˜ºF±º Õ諳’ (ùñ$ŽßÑèk䯨mð«J>ÕÌCýPgѪ ‰Øx(0ú’tXyQÁö]wð`rÖâ”@"ª¸Ê‡÷)ä…‰‘h¦Bà¸Ë¬;‚ C7†à4vÀXÕQÁhÃ3œ{çl SŠ^—ªÏçwé²ìFot7”õnúD¡ ,DrXÒ¯Àí¬Ø±Vá@´M® B%‰1I
ÌÖfÔi8se Ó/Ýèa;‡a2¿Oc cüÐ5øñ¨ÏýcG†¶$7¿Ç)7¦EYôœØ‰ A€žUóÀa{ÔÌxÓhqÃ1ÅF¨ò˜ -nù;Ù€Áç²Tõ¢äK+õΑrAZñ~f9ƒ±ÛéëÌ‘=¸ÄžËÆz2›5W%XÅ‚÷ÄX dè%ýŒ ™Z5S/9ÁAÓÊQ–Ã%jdFQoVY,%´Ê~§¦ê@$)ËTSQ 0Ãjh9ð Ø^7[5t¹í 5ƒÁõ…Š«»•67“#¤†qÛÛÜž¨½Å²€0 ²(æ˜qçFo2:b`¼SÖ½ãã5¦¿Ù<ÉãÛÐ"³X4·%ø迸,1 ÍŒ´Ãă«•x7ÑXÖ1¡üD’@ŠÕñÜH°v!4S‡ƒ!ðÜ ²
]†ÍkI^1´â~kú
Udä
”Dcn¬¢=ËÞ.㊽sHc[ å“醷+YeeøKt#êTÙ $!
‡áó!Õ(zÁ*Ê Ëqš6ÍÛ#=ïa⨖ò/¡Uõ> E3j´·ê1fºx΄’`÷Îß—ÿ‚»Àv Á`Åå…–ÐÓÊœ}|ÙÛ(qÒ
&
¨‚Ñ0Wy
éC£¨‹àÃg`xô£Btqy xœ¡=â{¸Þ›¸Cú§¯o´þK1Ô5ÍúÛß;ÿ¼»ù¡P_¨×}«¼„½) p¦ggò] /ÆÄÐ'¶Ÿ´Ù“,Ì=üñHŸhܳi€7+ 9_Ò?¬q]þk\—[ö2ôDã2΋^¯qæxMáŠ=ꔮȄæ/Îc¸±Ÿ¨%…'Û÷t/ìè ‘¡FËmÑ¡÷[X Ö¦oÁòRb0,ÅA›@;ÙœÎíi`þ©e–ñY\¦ÃG”#Õ¦žr”n´5h©¾“K·ÜÔ+Z=C4·ŸTæ^Uïh”©³!#gŸuc.qcwt¨.îFž^Aõ‹ª¦Ï ¤>2‡ kµ‚ ³æÉWÅ ÅóìUýrDcqÒ¿íV„»Loªæ‘ÝÁ#üÙE:ùüú½Ùá#endstream
endobj
140 0 obj
2574
endobj
144 0 obj
<>
stream
xœYÛnÛH}×Wô›©Õa7ïÆb™Äƒõ¬wâq” ìÚƒ–Z6Ç©” Ï7ä£÷TßHÅö‚E`È›ÕÕU§Nê|b!,¤ösµ½¹ÌØ]? ÙÝìÓLè‡Ì~¬¶ì‡%äôÅr33ï–I–Ï ¶Ü΄Œx˜°åÓì*Xí»úF•ýóM¯†v7\ÑõœÕÕ-=˜/dò0Ì‚¿•Í¾¬Ù««ç¿-šaƒE”²åzòDXãýNª/jÍžªá¾jXÉveÕ±vÃÊæ®Æ÷·]¹z˜ ì!â4PCÏ®ƒ?ýùzÎÙ_ZmV† Ïc †ƒ'5_þ>[ °¿š ÁcJûðÑ=ŒéYÁe^¸DJ Ý1«hÎOßhR¦ÖÆU°)çQ(x¦A£´!B¼d,r³ŠÎg¬mwÃ3뇮jîXÕ³}
÷jrNí’Lb˜³…ú}sô‚ÃKé£?UuÍnëU3°Ûg—Vö¬SŸöUG{f—?¾•Is œö|\߯×xŒg\&ÐçªÝn(-
).ô9¼2캪յØÀ›ÆEí„'-a˜’†]Õ¤Ÿªqf[·Â'ŒÜ˜d§aa¨ªÐÁä¹Â$
}¿æD‰Ýè·&¾ßã|×Á×÷ 0ëg4'*잇²äñÚ¦q—òö×wnS“STN:6Tä M¼rF|èd©…Z£‰ K dÇ„¥©I˜KKR©×FbnöÔõ µTжKÞÑv£7历gs©t0å)—™ð©Œí JÕ¯¸íC—Yˆ`‹E2}¬ËyU«RÏ%:牊 üìi0–Vy•T“¯²²[šüúH"„-ßa&GÚtst¼-¥n 0Æ+3 @b&ÇŒ'óvÀß (n¯=¯ éY°ʘ•wó$ ébÂ)¥¦DÂNú!š€®p
ÍSg¿ÒÚ@ù Y‰X€Jý:pE&Ä’qtñaÖµ®õYÆã$úêNCöN#çƒàx7UÏä…mµêËg3›EÓ’L¹/dž ˥햚a³„pìªþ.~gÒ¾- Ìî4¿ÐîO&K=Ý=Í ÃQ¤†#¬Fà ˆ(î;$4¼Ü†üN¼€©#FþQÓ»ò ¬îVMln¯!‘Į˜ù‘Í÷!"² Ú +7¢êÛ£¯.¿tÀ²µÓûNMo!§¥¿NÓs«Òtñ¨¥D²a‘Ê_+*=à¦)_[Ô¼y.féŸ ‚þòÇ·w"ºÒó™,‡#)ì/L¾ ×¼lY›ñ Ú2úkè.L…qô°9äOØêþ®Û ãcÛ®é£õùÔ@–ãgû°®:Wšy¦•@C%ñ«°E¨=pDnG)˜î”™å»-ýIÓ8ŒÅ‹=ûI?³´pÂäy눡¬ÒÄg4ÐA /²4ûä<°é!w
s8• ׸ž£R®SÏö¦rz]–rK‹LðœÞE~\¼ÿ°ü?IP|ë6Ì"G͈Qe…î?þgePcÍð^–˜ëé…U' º:žk»Õ±‰LQãn÷Áݾ¡kæ¦eªëàX»Bz:w¹l¥NR$ßnä.vê4ºÃÙÑ«Ó¦È M[þ‹Fÿí>O|³Výª«nñ· .'mNàc e¨»°r@UY øYñU›“èæEöz›+rǬ¦Ëi ƤèüŒç#Ž
áØt2 HÝ0]1‰ŸÆ „–ùîÞ©a2æÅ(†Sî
™Ów§ËÙ/ø÷/•nqendstream
endobj
145 0 obj
2980
endobj
149 0 obj
<>
stream
xœåY[sÛ6~ׯÀ[¨ % Þ0ûäÄîÖ 7vm¦Ž½“¡$ÈfC‘
AÅ«þ†þè=7RŠ›4³;~°MÀ¹|ç;ß>’˜2ãû½Ü̾»ÍÉ£žÅäqöqÆ̇ÄýZnÈë^(ðA¹žÙ5ŒäœäRÐB’r3c\Ð8%åóì>Zîú潪ôþ½VC· "ñ0'M½Àæ§g`Š´‘ªuµhyp2O³¿8òZCêA§Œ±Ÿ?© Žx!‹ÄÅÛĺ×xrN²ñ ©×dßíHÕèÏ>ŽÄ¤Ç¡z{ýúú<Äè7cÍÉ ..`>;™z@Võª}…§pjŒ/2Ê™”þýç1Žœ:³£®ÿ@MrEoË—ªíüòöêò®œ³ ꌺ~{ùŒqœæYvTlgÛñ(SôÒƒ’ã»Ê¾Ú(¬
ˆ &‚‘A56¥ÜÓWý ÿ¾„˜â-¬Ñˆâ?ø—{µ º~oÝÎ3[÷1 %Ïœ‹'u°¦ q’H>Zcª?jõ ªî¼ê @lDxF³8¥iÁ†7 kŒÃ%ÃS5ç€sS¡u»lv+…æ]ÿ¡ô YU˜®†%%%fW`4ìjZ!wøD_[†@F¸É*2+—ÕNÃVUkV½½º+=+aàÈE-”|ëß0ÔôjÆÓœ:ÿ ÐO(ÙÜ$07hñ Ò×&¤Ôå1K2f?<åЋÐõLF^…âÏ'ÄjÝ+ÝmÔh,)$M¹g+0EÛ˜ ÉAÈ#Ë]¡&›w CÝ“^ém×j…þ¢ÿä3ð2uÆFÿ ¦ùÏbæñ¤&Kª9Úo¦nñ"ö›ÕOi»!$Wï
µÉÇŠèýfÑ5õÒз¶åÅ$P
8†¹Äøä)7ÎÝ9NšÖ±©ÃõfÛ˜]_@œrù±DÅyA¥§KRRÇ?sí>jë¹à)eТփ˜ñ“ÇTÈ„ùæ©M1Ô
CiK.¸-ð ÆÓËHŒ ÓÏ|Ä Ïõð>è¦ÒO'6ϘŒ ×ÖóS½|" ¤·®µi“Z*æ™a’$²5Áh ›FCö¯Ù åø«Ÿ&™w$*wÓL
>Ðê èS²†Ê:&k¯ð¾ŽÔøëåÕù›³ÛóŸÎæÐã”Bùæ‡#Òƶ™óÔ·Ü*¯Úk
”Q¨5 —@E©¯¿5¤»>H1CL:ÿ«F5{WIÔóa„£E¯ª¶ תv¦:Uk Zþã>z°ÜâBbé …Øú¡íæ *Ï£g#| ªm(û
Ó lg°È„çcä~Ûͽ¤Ü°!
, Ë|Ä!DËãûhúýáÐû²I
98»¹¹x{n‘™0ù…V”ÒLÈ pÉä·´¢j»U–[ñƒ^mºÁ2{=vî _"N @Ò¯å«îkت \K¨ rIEzD…†Ð„È3$Žì¶MW téa»ÿ9£sÉ-žmxá NÔ+ƒ>9™ ŠÄ’Äg4ñm¼FÎCA3îÝó„'@]f±?x¯|Å+€••ZÈéAºâN’íšaJ†‹ÍËÜF Ì‚8Kq¼ ¹ŽY¼™}„c „²wgÐ9Dˆ\pàd1q .y—ßÊ;ä˜`ÂÉ܈',ã¾L¸+<+Zp ‘Üö8hùi1AðÙ4)EHÊ}Ç‚õPÛ™“ô§þ?$ÙÞøÿÄ7·å7q(¥ô‹\(tåø¶»3ûhºAc8üZ]ÈXŽ€…ÂÄAX5oTooô€óeì{Щ-z‰šhrÍ™3;ÿØX¦÷)è…l2†2wÓÐë²—v«~=lW' Â?îêÞqmמêì©úU°/U>›œ5fæY¹ìÏs–1Êm»¿G‰ ª·qÒŒ"p¶Ã9Œ$²à‰‰Å¦[)J~¨Ð èÌ‚œ™9Îium}õ‚fäR‚³iÊù‹lšæ,Ð:wï@ìü岶V8áS§HµÅôÿÂÀ »þû×JþÍíÅÙœ1•ïº¼»»|û/¼¼ûö‹öä ‚>âÑÀÐTð„d—0¹Â”TµNÍK+A8²
fßOÉFÄ"ˆy;®Pð„¾žuŸäQU7æÿͯçÖ7ž´àÙÑEÝ Å—ÐX´>\ºáŽË§ª}Tãµ &|¼¢œÅ†Q߸èD/TŒü~¤–r?
'P`“»$ì¦á^0\rãE æþüÂ;ÅÓe׶x¯Ðµš~1Γw t˜Ú¨zŒÈÕ,ZVí+¼R¤2ãî‚"z0:GžðpíŠ÷ˆ&˜ Sý0u»j”Ÿ‡ªŸ³"zTÃiÓ-+{9߆۽¯Ã—3:´2ãxçÚ õæ‹ ¸œBMä\ åt‹h
ü^퉲_çÀ û ``ôž4Õò ³Uý¦Öxãßž }q€ –âk³ ;z¯P6OóQá« Ñ;ÅÁÆ^ñØoç\
Oú·Bxêe? ”ÃØØ qò˜Ù…"¡ÜK¯ˆK|vQÎ~†ŸÿÛI˜bendstream
endobj
150 0 obj
2847
endobj
154 0 obj
<>
stream
xœÅYÛnÜF}Ÿ¯èÕ‹9†!»y}TdQ¢X³šQ‚…½P3=Æ Rf“´ßÞSÝÍÛø†,, ØŽIvWª:uªôy®Ï<úeÿÜ gßßÅìQÍ<ö8û0óõCfÿØ Ùk¼Ð?¬÷3óÏbÎâT¸IÊÖǙυë…lý<{ëlÛºØÈL½l”lª§æ#ÞÍY‘?Ѓù‚‡žëy±ókV¶YÁ>ûöüßëŸg¸`!"¶ÞÍ<— ß ¾j²ºÉËGöœ7»~êçì¥jÙ6+YV¨Šá Ö rÅ>Îyà¦iè;YÑJÖTŒŸ³çC¾=àë¢`Çì½¾ˆ»1 ¿ñ8r_À=\êÈb¾þàAêâ?¶Œ'¬–Mý‚›$»üý5ÛVǽ¿àIäÆQÀ>·¶Ãmû1+w,{œ“Q‘œ,/Y¾×'¨öAÉ,öë/ú0ýò^Ûç§ ˆæv:Ïb‘å…rÙš\ÅR=ÉmžÅ k•Ü·
`^Í5àAêÔ’í*ÂgÛƒ˜’X·^´ù"õñ6ïÌ÷]_Äæ:• Û¢ÉJYµ
–¥Ü6yUªÎ% %ä’jŒGÙ¿ÉúãÜ]Ï"GÖŒ|ÂC}¹p#:¨‹ØM‚´³"ëQ÷‘Sq:âuÐHÛP?NÜ@ľyîÓßÉNç#"= º±w¯XW B ©ã™,³‡BîÎY¦È²Ò†&ÇCE”(ÐÇì…ýYÃËý i‘„"¤@°‡9'˜yà´ $cYáÏzà—JøAî+„C§éè¹Á§ÕïhÈYí,¹™9ûlþÊ8»QÈg@?´ABJÀT¥˜6¥~¡“åÏdp‡‘SÕïÕ?lõ˜¢É˦®víVúþÎ÷lÍóv[€áþîæÇõrsywu1Gô<¡__m^_ßÙ/{²@ ã°‹!Ü#|G/Dâ»aÔAýÕ£7wWë»9¢îù(éÞP¶Ø1XȲ=²y¨Ð&¿”dYðâÄyl(8å¤í K~0!BþÞ$ð‘¿ŠbÔqŽ%4C%¨'^þXÒ7tG ¨ïî0¤Ò!ζ
åêÓGP|ÏÔGFoȹ³& ”¤Á#dn—ë
¡swµZÞ¾Y]mÖ׿^ÝÞ¯'u!z8e6¢°$ìDXFR(^VTå£;_„ pî¥ÎeúPš—Éb2`äÁHo†?#ßé¤úL·³å âª;« QêÙè@d,ïõeèYRªêÝ+¥p”cU“gºÚ&Òg¤AA`5¬E'¬Jüö ÜqÔsIîÀ³:7)Úèš«ñÜ%r$„žIAuÊÈ ¥C¶']´Û#Ôî@o»WúÈÀM _|@aöÙ«VCH„ĆŠn´ÍPÂz‰[‰Y;uV‚oë†^¤l’”m™µ-rÒì[‰¡äOŠ‘–Öµ‰Â>0Ú¯Q<¤‹NÚÕ ‹Ð
¿Y «_®—›%ÕÈÅê·ÍõršÜßjþ>8i{?»ÞwúÄ?g98"¾n·-ÈÁ#¨YÊ%×K–ívèGjhðD¨$•ºA…n2±Zª}|”
ÒÈÓ˜Æ)Ð’ãp{?0Çy¼èÛ1n¶F¼¢¯7
LÁQ ëÈQËñÔàÇI÷ õ=\çTç‘Í-ãÀ.k²‘"@@f;[`hVÑh ðb] ÎDÖrÑ¡£GŸD@4+j §'³^ŒÒ…ÝÅäâ ²ð¾>Òžg=Ã…:!j €è¾®Žú”1Z§ù„DG>½š‘¦½™¿{ë¬G³ÏlVVLîû"Ýà b™åmÏ™ä+‘lŠÓzº7l¿>gWìè C¯XÞv mï
&¢ÓüáÔW£þäï¸×䱃µ¶Ý뀸¤Ü‡¹QDÁ@Î8V2s0ò…ÒYn.æ!¹¦Îýú§¿Z9IœÈfËU)µê=È®#c ¤Ž¬L˜ dÑ«³Èήñ M°ædçùÜ̮Ъi`Q·w¨V“ÙíüÄ2§@[b‡jrÝ îÅÜs1¦A¼Òms9WŠÌ>»Ð’ ¢á-n1’ Ð!Vg¬²
^ öñ„çÐ|jý*`?3µ‡œÊTß‹\NTªÍš:¢o - ßZ¬n(G0Qåv2£c8ÿÇq@ýѱ˜µP2JÊ 'ÐfzQÑçúéÞLÆ!zsÞÍOkëÔk…4Ôúm:Óu}Ü£ô§¶ÅIûw–_ÜOB>ø½þióúêÇÉ—bR‚æKñ~Ùê2{¼’´åDª?/óÈÎSŸYj~bÿÅ\h œËõçÌ¿þªÝš–Ì–Ûü0¢é7gÚ°³!æ_Ü>ß¹¼¼½³þ«1àþH#>Ñ o ÊØd]1üß1/3Ò vî‡9›½¹¿¹Ñ0抎ˆèwó3]4Ÿü E½
šúþ~ý(bû£€³l»Õ YšnÎ,#Ñ6@ïÄ5VfàÛŸaÞ×3ÁƒÄÍOue6ߢ¥wœ«G¥œVÕzÕk7±I¬i"ô]¯›Î};YÒxa¿/±ÙƒèJ·#Î"!„æA‘¸ÁPˆ wÇ.¥ä¸–p¨èµ£ÿó" äžo>ÄhÏãî ¡ÿíj=û'~ýt°®endstream
endobj
155 0 obj
3084
endobj
159 0 obj
<>
stream
xœ•YkSÛHýî_Ñ5_·bºõžªýÀ€3Ã-jj7Ù¢„Ü€&²äXrö7ìÞsû!Y’Ý"ÀjußǹçžÛ|ažË™G_æ{±™ü¸ŒÙC;ñØÃäË„«‡Ì|+6ìç ú »Ÿèw8‹‹SßMR–m&\ø®²ìiòÑ)ö»êVæíóm+»fÛ}rüOSV•wô`:¡çz^ì|Èë}^±WWOÿ•ý6™ynÀ²b‚ƒf~IJõÄ9=›fÂJ|Ê}7HÒ¦àG';g+šÍ&¯×.û䜮×rÍÊšÅ.Özد΂T¿6ã‘›¨=Ïn–—׋ìö}¶¸}q9ÿ0Ï~½>W‹ ÎÂé3.ÔêEÞ[ºIhŽw÷• mËrV5õë óŽµÍ¾Z³Ç|´]¸AÜ¿šW¿JÖ Þň‘϶ÿèÔXt½%»oªª™ŠÀM“0pžJ ùu*B¼–&N^íeë²ì±lbZ65"Sw»¦jÙ¶‘Ýc³î“¢ÂÍw}‘XW‘¥ ÔNi/öd]Ãv2/ áå*ØRãBŠ[¹ûJ ð(uÓÐ8èÈ }&Ü0PÎÇp&M…yèfƒË á Ë ¸˜ï¦÷xdlù*R+ ’À•¨)g÷}x…pý@»ŠBÚãT×®Ñ@A x½LE('ð@ ~Ph‡KpLñ"íªÔ§*œ~èäm×Ç9ø?ûº¸úårþ"Ä ã£ÙPŒŸJrŒì 7;¢&
'w dÇÖåN]³{VAŪڔ²Ú@½FlùCÝè²2%ôvUQ9è®°A\ž@;«ÊÏ´ƒž“ D[‰aYNƒ ¡‚wêN ¢Så»id fl ݲxZ³"oå§éâ¶Ù(òà~¬èófÊ Ý4š r×ÁÇ|·n)OÛªÌkª]è¨ ôä¸~NêGž¨’ÑE‚º¡€6¦~TL·²w?µŸX3OL>I
7vÁ4v E—\¦P*h@$VÆHX t›Àcn¹cµ` ×W+Z0h tD!
søÇ^,,§Ä»ßlµ¸]Οª_Áý7s”š)ªøH_-/~ž¿PqqŒ DüOžWÎŒˆôÐâ»~haäÌÏ®¯Î/ˆxǹå>ú‘U;fE)çÅñ4(6ûÞ4æêÝ-³@ê›o‰N]„¢JŽtɘeÐËÇ,ó‚d¸úýi¯“ Ô0-ú.Áœ^]]ß\½$îÚ¼?HG¶4ûÞAX²¢*ñó»C Yáõ µ@^«¿b¡¦»HÚþ+‡‚Ck.ïµppc/Õ݃ګ“Ó“ gaßNÀb^j¥2™{öí ZÛ›aÚ^uÙ¢ÙáÂFÊëÞ©…Ú ÑZÝ,œÖu³¯ uÅPÖ ¤žžâÍñVG
%^ßVhÊS4¸Sô§
U>Ó;jöËï¬î´ñQÜš
ƒ`ØKwL›&‚kËz.|¨””Vl!+ó_‡) é`+3ËšL!Ž`¸¸ÉÒ²¸^eìÏ=„ bå¤4ìk3tØW‰—ÁÔjžÝ.¦‰™;O—§˜yæËc‡1ñ;( ~ý PŒo/o:4>œ•ìö[
M=ƒºSñïvy
½°ƒËù³™G¸=n\
O«;®¾ ¾’$Q •k–M}ö~{Í: 4{Š@Yõ¸=3d¿ë‹#’£8ßfËÓ«ÕâZÏ
ļa‚ºúVÄðÝvW6ª¨WБ-…Æe÷4Ä9 íg‡Ê@K!OiN:¢_ß? a›iÔþa£vƒWóÕ
¤|{qnn‡Âð¨½ÐÕ/
? ºWš ÞéɄf†¿Í¢SÒPÝ qq=Ò‡tG`J;uý 7Eq¦ Ñ}蹉ïõWWßá Vw
B »ö·HoDŠÉöû±¸´ “1ue/›GÃR»‰×_Ú¼9¨êÚÄô¯™|M¤LóƒÔ¥‡ƒëÕGºŠWS¼J;eýDPÎßšëA>
stream
xœYÛrÛF}×WÌ›Á” cƒ[Þ”ˆI´¥X
mªÖÞRAäPDB ZÑ?ä£÷ôÌ` Pt⤶ü 1—¾ž>Ýó |Îúgÿ.wïæ {j.ötñÛ× ™ý³Ü±or,Hé‡|}aöp––d¡Ÿf,ß]púAÄòç‹ÞòXo TѼ<4ªíG/ü8aÛò‘>L¦"
ü H¼ ‹ý±Ø²³«'ÿÍÿu ¦aÌòÎüö~~ó0ŸÄØÊ£ÌËwóÙOùìr~u; ¥Ÿe"ñ~~¯÷aÏ” ÚøRj¡¼|S6lYívÅ~ÅZUïÊ}Ѫ†{6Ÿä¿@þØç ô²»¤Ùµ¸cjš²ÚûlQîÛ¶ÜVM¹bŽÛïÕ²ÅG¶ªpÖ¾jÍÑS:qjt¢DBûÐͬÝ(Ü e<âËN_*V¶ šˆˆŒzŶ„à]ÚÖÕÖ®·'ñh{¥m0…o¡ùòB$‘ Âhæ}R$\E²,/2_¤Y*íÇzE úÀ¹ Faf?”kúùi ðØþ¶VµÚ·ÖFá0Õ_øÆôd Æg ½ËÕJé+ ¶ ³ÔZ[/*÷,ñ¼ ßÓYYd–Lyì§ßÏò‡»IÆ}è‘y—óË gùl~Þ\µu©uï
#}žvBŸÇFÚO
ž=8CˆÄ—qg> ˜UE]ì|ÍÖuµÓ¾lTý‰ve±/¤ì,§júMúa¬ï„Š ‘j>~ðüo&2Œ}™Jïe¥Eîîtûµå?ŽÝ6¯8nÛ·]:±çr‹`8¶Õ®hËe±E„"~¶Çô ½ïæ<°‰;åYàÇiä¬ò-b Nœæ:(2?…p]
dY¬5}9¨¯Õ´r%"vÒÿÞ¾;õ„#@¹Œ=c L¼6ZŸ 5¢ÔO²Èf˜·QÅ
ÖC¸Bb$Î~ªv‡ö…Õê·£jÚ† ÷[Ä3%Ù±nX‰”h\^…RtZdH,“WÀŸV,qè/8 †ûU‹Æ¬BÇz
—…Á‹ œï%BÅ…©—çwìî>gUÍîn9â¹QêÔ‚ds9ßŬ
Õ…-EΦ‘ ‡ê ]£Abî¸ÆZ7ïãÄg—‡Ã ÖéD÷Æ ‚V¦]h†q¨—>—͆ð XÑ(€]Á`ìº}TEËvª1©*„€œQŸªqÌõî¦xRPMùO>âHGö¡V8TqXç$'0wç‰
âtÚ Ô²üC¶ÊªŽ-Š@³©ŽÛ•ìØ(B1íxãØ8ôeÖ#¦ñjïÐLˆÞ¡6RüÉ4
Ï‚ ˆ†A!Æ/™ø zp †Iû…j \öWûQîs.qy4²IèÇÑgr àGãÌ'0øç“ŸD1yùQ€Ç@_ÑÁx]¦¡®:ÜEþâ’%£¯ÒOŒ4#è,ðw!"FňÒþè(Óg[¬8L'}'”P¤.L9~.Û)#)R(M"ÆÕFLéÐVåæ.Š Š. ¼;.7,Œi´Ïü ‹³3`þ†Iv ,Fg$@¬8éá€Ê’E £PpØù ôÀvÅ SP“,Ó¼Æ!dg*Æ8t{—?ÜßÝÜN"ièêÄ™ð³ KéΆƒc 4¤Ó¾;s>»¼º²ñìƒì)ÊθÞeÞÓŠÀïàôÒœí`•)鮶V—d'»/Âc«,CÙÕð€–?;ëÎ ˜Kç¹ÞÛj"£ÕЫKý¿$^»ëí &~šð.aì3VCΰ¯§Ö"äòï®g7W‹S%3è#-CŸgâ/´ÄºÊ ga¯¥ .N¿BM Dê‚ëý$ä™ ráUËApxd_Œ{- :ûjמÍCÎÕŠêt2ê=«Õ[ÖT„{aŒ…Q–¡4¹T £•*/RUo;Á#°ÆØÑÊ΄×ï¿»¾™-®ÿ3;5¡ôeàˆ©ÁßuUï ö'g' #GÆ>Œü3I¤7µ¤Ò\ÙñŒç^Ý q_D®A k¥û·EÛ´‡)´/%Ò¯§þeŸP¶ÿ°mª·tB¡l_隈2»¸—S@g«=Üh@+»V –tœ %lx/J w°æù =w1öt…Éñp0¡V6ª¸¯¨ø—”ÐùìÛÛùÕëîËäã}£tïÒ*T©aÁP$ÎIØBëáK¬®Õ²ªWšrØ çœ D³LÂSTº|ÿý‰áfؾKi´š™¸hWʵ¡ <#
ÅØ $±†˜ŒkeØ?´Ôìúß³W¦ŠãA£ZRÓô
²e:ìQ- Št†®Ý4 oo!À4‚ã¿9^=]8à‹^ÑÚ%oDD5Ü‚Ž¾ð3‹ç0 >t¡…ÓiïºÂ,àCM©‚U Ðw}Ü›Ú
£ÂÒ.T9êÚxlzúŽôf®k+{‰¢¡ D ¶ª÷~Àþª)Ž²èuS¼š÷çÊÁ¹¤‡ ܱ¬é³ëÖð°ZµÇÍš(â¡®:ÊK{Ê Àž©Þ¿¤ða'BSƒë°GMû$AW¬GMS?Hƒ ë›É!ú€51ѵbd½§±éЙFYwbàGv7L×ULÒŒŸÞ0v+q°MA ¹è¸ &„!òŒ9@ÔQ’ÐTgœ$:]Í,C$”'`ä‹Åõíû‡ë«ñ0cÐÑßJš:`æ‰qŠaŠ›¢f_±¢‘vÝéJÄ k—”îMßQl‹i 8¶žv)Ó Ò—…¸\_QÒ a–ÕVi¤Z ·Fx$¿ß“„>nhZ«ãNO“(𧖧šX®ƒ¼[mæ ÎdŠAÚqÉjÈ0©×‚
h´©›tx/û!" "\yDþþþ憆N–!Ò¹ã&ÃVLpØXöÄÇDü)[LˆwŒŠïL÷Âν³ù|ÚvøöU#,Eë(†a=åšìý°: ¢ì$¥ežIéõ¼âNFït–ƒ’ߟI"ˆ®<9 F¿µÜ õ×èO`}“éiDTÁ%z7ZúèÁãÖEdè“?mຠ…ºôç5€êÏHÄ0 ¢æ‚7Ž; ±»ÑCDJWÄÔ¡‚|¾Ed9ÈÀÊö¥%íL¶æh~|¸Ÿ_¿& Qb²ia•iZ@ÜŽa-Y¡: ekõÑ/HѦ›¬šÄõÙw.͈¦Sº‘ dæý^ì[DfAÃÒ§rÃOª)Š¦’S;äaù
*x]m·X9y3 P ¸!gÝ6‡¯ß½[WÕ»ö¹l€ïŠãª¬Æ *ûÁèkÆÉSÊoþù3?•+uzf&ûßÀƒ TŸ ï0Ñ€ ¢35µÛÄb?K‡ã
a'ñØ[W‡º$[Ë µ‰5¢ÔïI4®ÔZ·êºs!í fª{R{U—K‹Úói:˜¤Õ&€Ìo=ú¦¤˜Ë›¡ßß|õÆÍœ¶ÅÒ¡¯a½)¢©ëÇp wú… )8½W°y ^¡Ç´§žB·+m‡a' èI?ù0]óüÆô’€½ëdJüÙñüŸ{`‰u2Zi‡lÔž=»HUÿJz¹gþ@Qy?q4ÜÞ];&÷oÛAŒ78ñ^ä¼å´Á$í¸Áâ4…éV—ûÅ ÀîyS´°ñ
¢À‚(D$Ž5äÆ°ûÕˆZêñ„JÖ½ ¥µ£çM¹U®£ – Á“œHn½Ñ‹œp?ãýŒ>HlÓ‹N
ýÂvÜ‘ .ª
ˆ¥#{"ÁŸÐÊÔ>wõÏ@mEóÈHTìÙ)êµÐÀ’§_ OÝH©£Åc5.|4%ŽÝpÀHE¬NýÞ8:ÖÔѺÐöeE¶+Ÿ6Ô^ØÚt=â/ŒÄgm,ó4©žÜýߪKŽNnqwk©˜Bþw9a*-¥’® uGñ Œ ËÍÓb <š… ªºýº‹Y³c§ÅAŸ¦ý•g mkg4Gš¥YÚ‡S Û•{ýº8ò3ȈìCp‚×äf_êY=¨î¦ÒiØu>z>€
f±;¤Ú«#jåŠí•Z¹7„¶Ÿ¹Â 6—ÏÚC=£.>+qý³üþÎØ%’èLv‰¹eÝÀ_{ÏΖŠÎ_ ¯ä{THrs4 Cß鞆- )Ñ÷,o¾,L˜]^y9ìÎIajÌ[rAï_e¡î´%÷ã@ž`Äyî®2HFï6Ë~'®›ñüû!×iàÞA÷Þc» Ýl›ªkhèGa „Áö… OX¥"0 t0™Çfʹ}“ŠÜ!-´5ò€
ÉÏd Òí2Í9¶Me;zïž¹d'.à²
Íã‹ÆöT!=ûÁν~3]2ç™Á˜‰ênJÁÿ5l  êáp³‘$Ü\#ôÛ,¿ø ÿþ§»ÀÏendstream
endobj
165 0 obj
3315
endobj
169 0 obj
<>
stream
xœYksÛÆý®_±“/;$‚]¼§ÓÎ(
•(#Y
E5ÎH
H.%Ô @ õ7¤ÿ¹çîY®' ÛqLwïëœ{îê#ó\Î<úeþ^ïN¾[Äì©9ñØÓÉÇ®¾dæ¯õŽ}¿Ä }°Üžèw8‹‹SßMR¶Üpá»^È–Ç“{g}¨‹G™5/l«}ûàøVä+úb2¡çz^ì\eå!+Ø›OOþ¹üGrÏœ‰³f~Ä–˜?»[\^ß, ïnç‹Ó‰ :?Îß-Õ Â…ë¡«^è
ò/:îƒ3Yþ !â‘Äõ}ÏKô7 ¹íœn6rÃò’Å®€ƒðÏxºaÀf_©)úk’¨^õÌoW¸<o÷UaU¤<ŒÝ(:z—›ZaÕpšÄI_ä4ŽT‘oeýI—@ ž449‘5™Ý0Jù{gö÷³"§„ÛΘÌbæžpN•¦Rà&ŒGé»wvÕjªë´•Y{¨%²YäM+KjòVy£|E"NsP¸ãC™ïö…ª¹Ü¼]
ópu ;#¤ÛÂ87 U,Ï
üÄôˆbàL€qR•üë%»îšL{‘?ÄöÙõ%C}/®ßÝÒc=A̸›Æ~ØàûVX.NßÝžÏ 1¯YÆwyÓA}8§û¾WC7àÖGåVØr²:ÛÉ9RýQ?[Y*8¨±ÎêúøÐHvz{vqÁvÕFÁùò†µuV6[Y7S¤È6¬ÒðÞÈ- íG¡Æ©i‡ìP´ºÍÑ¿i:à¢TÓ‡³ÊKu¢±«L ËŠ?ÃI±åž÷‘q©²gÀ³c^ú‚5/ph×°¼e›JÔUÛ i7ÕAÅk¤¨ˆÐ àzâ¤uV²•BÇ,ö\Ÿ§©õ–#yš9M¶*$;ôË55a«aÅ}7ä† ¸M¹¢ÈMÖf0ß %^µž óö™mòíDº¶0G8ù”Kýr„ƒpNÖm††]?£~ë–
Ac ƒ¦9¬ŸY¦xM„αÈKä‰jò]^dõ$ 5›¸z\ly‰š ŠÒLÈ>‹›
D¼®Dm ìä[‚Wµâ沤kòIvÅJ]‘¤–Ké ݆uC9W‰ÜT”Amµë/VÄóÒÁÑy z v„S%õbóùòfô Fž°Ýµ ¾ ûõ~g†«c—'a¶¥rd`»”»^ ã;–@Ó.oÕ¼ûî?™>; ÔÙQfdøØögÓ#ö 2¦ òœµ¨ÃªÚ¼°gTµ¦ÁöQ™TC§(_YaÍ®“š•¶×Øiìz±-“[àÝè5íðhÐ ÀÁÛY½éJ½ÃƒÈôÎh€u¤Õó¥
W¸>
d½~? §žß}ñ[ÇuW×?ÌGõŸ°ç»ÜßdƒKBÛ^~ ¨Œ5ä{Q•O.»ÐüôI
&½ÔׄX@è Æ >8U) &S"Í6Íøº“L& :Õ–Ç€1•s3ÝÁz~Ø“^« Æl
”p1ÏàõOK|³¯«ß_tÏø\%‘ÃwasuïLWߦó’©JØ™FVN⥮'¸…ÞH2ó‰SW¥Û€¨Zº<]eŒÈ×liä{Óµ"´T!ÔÉ®Õé‘õÍ‹)mÉóÚYR€o„œ:07‡ý Zr$„ ¤BÏsFŠ’Ú*š#LÚ7 z¶¸< l !Þ„”mb¦Ù[؆¾ &‹!šÊ7{²Ðãü+“éAmweþ»Ñêzd•?9—hç̬ÃÙ¢ €˜uiÒMAs¼ˆcůcÚëé² r=ìÛFÈž&jRG‰CÓxõbÛÞ¦ÁHP•†Aã?Lþ[¢¡œÿ©j¼":Rì/4ð÷VÞéMbÅ iäƼ›uÓcß}hâ´ßŸ %ÞcìA?4@~±¡‚)é¡döš< iz’ì¥:°ã„{NVbÝ»hí++Éô V£¤ˆ«—KâÍðàþÍûÙoßLI ÷ßüÆvÙ ™)ä¶e WÓbO˜YÑT $9Î Â
¢¯k‘Àl°uF[aK;„U]0?…Ù}63u 8zî¾Îa§ÐBi‡àw^¾"2Úÿ“Ž»)ÞIÊ©‘„3}7»úÆèùØÆ÷Ñ/Rî†B!ýÔZlt ¢Q?䥒ä;j½ÖfP€Àô¼ÎHâSQ)³¦P˜ÔQ¿„8
½IT
°un(m¬‰¬Ö'’ ,íûª„ÑMµ>¨M°Ïå¨{€tVÁʉ«‹«¹JpoZ¹~.sÚÚ€¦¸ÉëÐ*±ª65Ž” ðl°½jqËaSóij”|{£¡GVöy(ôÒ ¬DI7:E¤gÛ³Ú}Ð¥
åHlfzß´ú¶*Šj|B`µ' ½_¦“
çüLø"Ââªî(|©‰›{XzPŠH1Àb¡ç³Ë»æ^öáEæ ÎíÄ!‘Ð ®
éÏ_ âUèÖZê^Mí&êcD¦~·ü8˜C¯Æl4szRB]BëªíúB¯…S{@O OùXÒ‡!pR3RG0½wÊ °¤å×wÊr ut_æ};e‡väG³Û·¶l;Ö‘ÂÐlF;Ï—ØU“ê»»ËKŽzþÇ?7ÝXjIFKèHõAÊŠ±~ï,tŽº ¸"~ u®ƒœ„ÒÇ2= –m°¥,o†ÂcôÕ—Þ¹w..ç€ Ð·–:˜ª`1‰ÌÝèôÏè;‘á.V/“(´’ŸÓb®„àçWóÛ»«ùãùbxÎõÕxÒ]cxa2–ïŸÍ4ˆ-ºkQ)#þ´Qº ›I=Ü®M‚³£¤7ŸjÆ×#MïJÕV«—4t¶$[@Zæ¶ ¥]*ÖcvØ!cAJo¼´•IúÒãý¬ …V}`¾Z_9º@}ûº<úÏ.û`vTz‰ ‚™ÐíG² ¡¹gˆP˜©=p§?N¹¹’ :Oy©®Ì ˆauyG÷€Ö>‰áWÁû ›|QšaóÔ¨€ms
iŸ'ƒ‹]©)žSÖ¹£w!‹®î×¢Ô¨X¦·›Kc¡Ox—‘×iœñA ;sÜÃ
ÞÈcŠ‘'©M¤ÇÓ¯fR–Ý•¾˜ž¸ˆ'øòG!Õ “F4pôhôê6ø ¶HÒTy ˜•z@ׇ=éˆÃ¾¨²
©EòÐ
<}§ûk¿ˆè'ÌÕåí[„™Òskõ³'oÍ6ž¯»º>
stream
xœWÛnÛÆ}×WÌ[¨kÊ™áµoi£´.”È•éErÐm±‘H…;þ‡~tמá”ìÓà …ƒ8!‡û²öÚkïùÂ\.˜K?ýïì0ûn²ûfæ²ûÙ—™Ð/Yÿ+;° ˆèAr73ßJÆŠG1K3!w}–<Î>8YWï?åióô©ÉÛêØ~tÔÇ9Û·ôb¾¾Ë]7tÞ¥e—îÙ‹§çÿM~™ÁÁB,ÙÎ|IÆßwyÉžªŽe»´¼ÏY»ËYéò¦e‡¼ÝU[vûÄ`©-Êûyò'âŽû¸¥ó0
;,~p~¼Ù¬ÖWɧ o®“¹y +é¬ßm–¿Î^àÜ,ñŠ"™$ïÅ<ð¤1â´kªC¾ G åÇÜ“[ib:âv‡H.tÌÛª|EGGVÙ,PÜî`+¥W.½€ÿHÄqÿ"kÓþÉf¼«&&Bɽ(Žú“ûÑ 0O
îì6ßi Tݧ#žÏƒÑýC>1s «ž…ª©æ* L|§N5 ÚJ ùƒó¬mXQ¢½W;QŠ‡£“û1ǘ«Ñ…So0©šÇ´n‹¬Û§µ-¬6(#ÉÅ ®«¡5¿`EË ‹ýžUå™J5t¬ik” ¤([ŠpBN¦¥Ç’Õ,ùÏgƒGUÛHŠ²Íë¶ùæ„*'íöí„b8XèÐß߬V\cã$ôL.ª’ei äY×ä[:Õ ó¬¸{šÆðýüÕ„¤ÎÏIr¥ŸXƹ<
÷/˦ÍÓ-«îØOË„U5ûyùú
{¤–8æõ]U ("²ÀnSòØ»h8Ó1áψ. BTwÝþ‚áK¸ ˆA¯fNþÝgt0Ч‡ã>×_N]§Æù›åj™,O@ Œ/¬±áŽÒ¿Õ|–Üï™?i Ã%Ûbl‰¯Úý÷†.÷•+¬=óÊèÐ mrôúCUØV)aׇxÁnç"†¸ÒéZªN9”*Õ`ƒhÝýÿÉ:pä0PS7÷ÜX£b}h66-ý
²ÐßK5k”ðJ Ó§È/TÜ· [5cÞ‚‡q44xÑf;Ê eǺð& ÔÑHpL!7VçZ÷~ýÃúÍÜëåí3m‹bjZãéÂHôÝG9lס†½¨Êσ¹Z_'/##î{aoÙÆB‡ÍAë?ôQa1¨Ï¸<Žä FÞ^.Wo®OM h½’ýi
ÛtPZš. C7iJGž<—NŸU 91ë’Žgs цŽiz#"QÚÓÕ #-7Šÿ
²êI-¬^È… É?Në,]?¶Ç²Ÿ¥¦·ŒÊ¤Fæ. s/5ùÉÒ!ý¬µ®ƒŒú5(W?Ì…g¸tšîx¬ê¶ÑQ/üˆ+uš¸CÚ”U‡Eݓˆ»%»Õ}?ÓôÖüŒÎ‹êìÚâ=MÓG„ML™%ÁÉ+40;›H4,&gƒþìCÎ G{(¬ð¢s{uUÞEÛ°zýEëü¸O33ÐE=n àÁŽž53*ä<ˆüѸ)æc‰SfûnÛ/ …
â±/¤ˆM½…N
J×(PÔ}‘U'%iñï»bOá ž‡â~‡0Ìtñb°þ3(`oX…á©åA‚m‘í §lŠ®Y#1 5Í›¼§b–}GùëÇiÀ]9É@ô¹R¥B_©ë‚þUŠÓÃt†‹éš°/F2ê¼AVuû-;VMSÜÒp®Ê;ŠÆÌ¿CÕæ#A#ß#‚Þ¦ÛýSŸ}à†Ú hÍ4þùÍ4{%-*Ïem¤BñMÙAûÃS`¡ ‘8·„ü-å¾-=ðë‡ýiÑ
Š™·†
Û´M9»yq rÜ概C2¿Üœ;"²ÚÓ¢é '®òÄÅÄ` +8ì“Ëa4N¤Þ4á‹ÍWÃkG¥ Q «V*ÓÆ ‹(Ô;ü µ‘´RÛRu0›F·,5ŒŸHšeë+6Q(*©sKÒÙvu™ë»®iÓZwˆð= Š˜×&KEv(KL©XÚöá¯çý\8M3¹ÒyÀÄîMN—ížu77þÿöÊ2 ºƒNïôH¸ÍûKs µg«— ã“-œ¨Û
B\´SÓ5Ãôêz}¥¯"ù WTC=Þ1tÌõ»ä·%íä«+ªéo›·œ¶ }øõþí–d¦eóÎöj'&I3ÐRÆ¿LJ5ÎÜB¥+̇ˆV†ö åѳe2û?) ÝWendstream
endobj
175 0 obj
1915
endobj
179 0 obj
<>
stream
xœíXÛrÛF}çWLù%`•8™Üó¦Ør¢”$r%¸6YkK‘C1.4.R¸ßàÞî¹ ÌxËÉÖî>l©Ê–€AO÷™Ó§»ç#a”†?æÿu1ûö6$OÍŒ‘§ÙÇW/‰ùo]ïXáƒd;Óßp
Æ.b’3.\Ê|’¼ÌÞ;ë®Î dÚ ÙVûöÞqïç$Ï ñÅ|!|F ë´ìÒœœ\=ÿ{òÓ 6X¸I63—zqŒÆ›ª.ÒSü&m%©¶&´¢‚¿6Õº+d ÖJå–ÚØ8Ä©`®6«ö²Vv(IvŠ »
æÒvl³‘õ³b”»†&hÌSÆd
+ )õI›àR
Ÿîó mU¥zÈׇ¬|RnYS½gÜÕt2°£KSò
ѳtÈƧ903AäÈ6+·Õ—#ŠÃáùkÒeÛ•Cbàiè!Mù\W—7o—G>R
Ìñ:ioCêGqäY¨¸«ÇyÒg£é§‰åúÔãGt}ï(^¦Ûðê´l¶ð+@)çÜw~ƒ'k{@k™©H{þqߧ6Ãœg©3Þ× ƒOΦíÉÉ¼Ò ëÞɶ sî!²¡s¸ŸS½€Õ±7dÃ4‹}ø"ò¸ÉbB'iq¾ v_ý¸O WgFZ§…lõ9iežk~AzÔi}ÀÇe…,_çÝFªWÕæ°Ø§5>Uª®Ýwa7¾5®e.&c…Âea¼°þ=Ó–1†Z{à·Àñ}]µÕºÊMÆìÒ#!ˆ=¬ ‘¥ 3ß>C>
ñԤ͚—föN¦¤ HÆF0¶†’eI~L’Õ½sµjÈMø>ŠSÉÍ挨lWzR¤ ;‘Üxæ ‚Êú8ÖM«ELâ /Îßôòn"02p$ãzˤ"ëù7&¾Fœõ5Ã×+viù4h1œäª2A]V…)Š %b‹svÕ¬9§êH³«º|ƒ:>I` OŽŠ°Mö• ZTèëa×quüÜùÕò.9U S<=¬¸þX@BŸFn¿³l×^Î9¼u´„èîòoJˆ†ÌBÇšAÅ‚×íó*Ý€âÂá}Ê¥–b+éY+
1L!5PŽª"&ÝPŽlMzOº©ÀxüàÖÖ_óƸ$hq-jMö¾Xe%:”5&7Ÿçu† 'Í¡®ìÓFIáP*ï¤$iÞTFÞ‡vN‰³`rà)Ó™ö<¿‡«óÛ &rî =ÉèQN/ìË’ ^¿F ôô†/ënÌÛ¨gNþlºÿ½{½
#$KÿA§C (c–'£³«ê)ý‘Þ½'ŸóæTÜ Ô”÷Ç:œ¶U}˜¾į̂-5*ï"Ži`¡à´OÿWc}‹úœ²Å
Úßö•æ ¼1>}šûNš•gJù3•^ nvµ¶Ì~L fOvì@HY¤²Aõ:1°:Û¹©¶å´QäÇÞZÓˆL[ÅÆô»ª¾(ôa0@HQÓBS
¢,žuUÑ°là§Ø‘“··Ðó:ËkÒ7=÷ÎùfA )Î)¦A\Ã;:öM
VÁ<+ ¬]²ëR+!Th׳,z)†3‰p‰•³&8åtÒw®ÛNÍ.ë柪p
–²«<'¡“v1?èÝzbÒw? ݨ¡˜˜yþ˜®?˜ÙçKÍõ)²þOK û‚ÌÍ>cÎXë §ú‚Ö©Þ¶ÚöK·í„ P,9zuB5úæëÄ迬CÓFZUå¯Q çmþ
úiøÄÿ…
ÚöoÕ"—ÿi-F›w««å &5hè]çüm¼ üâhDa c „_3Ûìk ¤:«ÔêÛ©¡3 Ó »…^ýé\\åd½dÐ÷ÔçÉ‘ اÇéS?Œ¸5
ܘ6¸.õýð³÷÷󺧡}ŸŠw) ]ÓâAsn}®z|t9JZënÈ ˜CÃŽ¹Õ;ƒx@CJJÌ Ú½Ãêç<ä Žz~ð˜æ¸ëR7êUòHgÁ`?û@w{Üøæz#¸Ëê]Ò]™Ë¦!qÆ¥É$¶ãúÀ¹
>®_²F*㨯eÞ)ËhU]r ãæ>’æff§kUJ^]¨Êö ÀʘWYÙÉWf…”öµY »€–¾Ÿ é/C¸ âÚÓÇQ´6Y“>æö¦äDˆéÍ `jæÜ3T ¶'Ç8œF/n'd€œÖµ±á0³P5õª‘¾i€FŒJµ
=Pv´ÆaoŽ¤âŽGa^ÖšíBVYJGUÜ£¿*Ã_• \4ôØaØU×’e•Èy±|PÄ£¶Js󊮊}>¢¶Œ²Q톬 n_½ùOcÏÜaÎgãúCˆÚ/\ Ÿ]$³¿ÀÏ?Ðÿakendstream
endobj
180 0 obj
2187
endobj
184 0 obj
<>
stream
xœíYÛrÛF}çWLùÅ`•8ÁÌà6û¦µèD.] ™ÞMÖÞRA$(b2XQ¾Á ½Ý=3¸- ǵ¯)UI%ÓÓ×Ó§›Ÿ˜ÏóñÇþ]ïg?ÜÄ쾞ùì~öi&è!³Ö{ö÷¼à«íÌœ,–,ÖŠ'šö3!÷C¶zš}ðÖí¡¸ÍÒúù¶Îšê±ùè©sVäwø`¾¡Ï}?ö.Ó²M vôíù¿WofpÁBElµ™I F
÷ê&=4yyÏš]ÆšCZÖÛìÀò-{®ZÖÖ[ïÚòa¾úÏLD‚k8î;V»lòr]m@g¿Î…ð=8š•é]wyÍîžYºÁç,e»,ÝÀEþ@*I©y$C#ÔËðž…Ò¤ ¶?ýà½XÍUÈ}jÏ*HgUÌsÐçReK«Ê߬â M¶yÁžòfG‡~¸¾ó»Ÿpi%x¯Þß\\¿]Ýþ´Z½ýiyz¶¼A]$ŸÖÃ` ø,±‡ø?ñ% ß—‘/í¸¡$&¸Ïª]_µ
é´ #1UàØBÆ’G‰³Õ{È̵!>Ô\)8
7MœøÂ>p>éʘ«^™“çÁAë0Š=„ißÖ
« ³u¾}¦¨óß3NjÉ5^²OF>º<ýåõùÅòÝù¿–κ’ÃÙñ6íîÔ< ]˜|%LÖÕ
E…Q³Çô³@‘g’˜'í|Õ› ¸œé˜]iQTt2á:²¿Šnzª)“›jdå>ý-ß·{²–}ôòr´Éj¨ªj š}ÁÌØÆÈ
BΗO6|*ñytöú\k*¯¨Ò
gç[ºå ²OmV7P% k‘’‘ §©Ö‘IÞ{(Œf—–¦j>Ïe ˆ/-Úìd\ OyQ°²‚Øaý²´Ü0ŒÎò³ L_Ø[œŠ¤ ÆìvùË«åòlyf¤Ü¡ŽM{(³
7ö²Õªe beí WZxiZÌ_v) Š]?¥Ã8…]~ðžköPVs‚ Ùã!‡¢0 FU“ˆG‘ÖCBmbW¢7OȺ- ¨Ûõu©ƒ Ûòªd»•bÙ–<«CJ2£Î6[76C%e(Ä
*RtNYHJ]¸+ų̂ô5½*ºûà•ù\Åš‡Þ¶!•ÉF)ï.µ…Dë².ZY¹©Yû®FÄ$É$Ú÷¹ š«%¡¡n|ç×ÏcÝ4” e1rº êcB˜ïó†³^³®Êuv(“+€¨×€Pà\r‘ C ©q¶„9+j T䀷§7?~/.¨06ž#` Vm)ÿµÒÞö¶ãu8 ›’£HDq— VHH?Ðÿ4ØSn;ã ^è® ×Âö%“Ê "s§yaQ@ê?‡Ó · mœ‚=DŒp µ t8q ûÄÿÀøåt³AÍKsð³ #nÏ.C6ßÄA ü Dþ‘ÕùåòÕõÕÙùêüúê{‰E|›Xà;”jZ…ú8³• P‹Mö¥„DÙU#aÀ£ËÖ-£W:n’™ºêù¦ÀBN\2 ÍþÇ<Dy§ï—¶ˆ»‚ôC¸Põ¦*“ M¾Ï,> ñ!|ÀâjYÚ`‘þJr€L'‘tJU¥/G¤¡JkH#L*u¾C´›ÚAÍ»¬B3ºÐÝž¿¾¼>{w~õj9• 2PN‹ÃTd ¥þŠÈ÷W†tɘXÏh¼áU–ùö7ÂP†Çƒ, ¢˜Es·à³ö±ôñ±È*âïÉÂ×¼3àäõ‹÷åMŽ Ü •ð;¨òVïF‡Ð¹Ý³“aºƒi Ð qÜ”“î› `× ì)ü=ŒD_Ö)! eM×ÊŽ‚±€™$Ðß@cœ9µIÄ–áâX 6#ØBo ¬ÍKèN p§©©ìÒ1`I " ‰`ùs# ³=›åJÛÛ
lS— Bk á‘Ô ÍIFB=àù
BÃÿзG-`HMºŠ¯Ðñ ž'‘⯠MqQœhw5Æu“S˜žæšÊZBÉ
ÒÔYH|m8ˆAÁå쮿šsâ,‡Å4©¬dPÙ|R‚
ßí[U¿E¸'M|©¼¬ÉËmÕïúbKFI‹Ó.•É
€úŠ‹9¿z}}Ûaþíû«Ëåj ¦AËÍù±é´¶m#d1ikà"éÑ*í&Ôp‘¥‡·)û=;T ¤r˜•Oœìa»Ë³ºÞ¶{á½€` ÏÐU6-
‡í„6^ }Ú¬w¸1q6¹)Ü \høq÷ßÓë’øÛ½.!nœ$\øñqn,t4ìuõŽí.3³+8CáiÌ{:ö
ŸêÞ´ Ñx€R„á˜P„@^:phMÄû <¢ýÌ´'Ä=
}•# 2EŒ©æ™†g éf_ I:â ×WWËW(ˆhøón,p‰áõ×ïWßIN„¥¢Ç† iÒ¼tK87€LC 4¯¡¥[xð($„Qàñ$p¦ I`Ë® M‰ØEÌ0* ,2|7Ša UÙÁ¶
Èøô #/ãìª:ìA•g;…v“ŠGÂeÜI9D;m>ËÁÕCûXS
£h“·F
4zßw» /K×½˜Ú Óª¬ó
hH›Ft&eLÙ)_›&©dô†Ê˜f3`¢®
N¡?ÙÅŸÙüdùÝpù´ Bk çÛ¼laFd‡¼~`é]e6ªp=v£âÀ]5PÈi‹bT=딶
ï"ñy‚ :-$Ê’wç?ž^Ü\b\ܪ °¨Zºº~†Ár2‹Â0nï¼dm™ÿ¶ÀÅëKÇ5°1: ×ÃH%ªÛ.’¤úÄàÝ>¿ß5VÕ:¿/Ó‚¨’ƒà¶DONêXúH¹¦¬÷ê,¸šËp5BÚ;é(0¹a×´ŸlËZ¨PA[®óÁ;ƒæOè ˆÜ
ùwpƇAq †÷§]\dŸAâ³¼aå„"@ë㱚4ð#cÒ¡/®ò twî!þp-ïræ c3 Èí%aM À¬BÓÙN! €…2e„3A“›D õö}høƒ‚ˆë¶éSÞ®¡ Ã$:‚¨=¤M¶Ýôïg¥; Yˆ³šf€{‘è9¯)ëÑ -5%8¬l÷w3[Ȭ¢È Ô!eÌìºÄaV^U\àhçF7¤xÎD/Ǽ¨˜+ $¤›ô°quR" ²º*>›o: mvÙàZjdè ®ÖµîH}o9Œ•ÀæºéÀú ê»Ú YÛÔ
þF€l cºi Zq%å„–z-ÉÃ5†Íòš:'ÀÖ ˆë˜ýݦ YËÔ&(Q•™í&†¡˜½úüŒ³< Ã
(‰ðX¶ù2Ê“@&Îv»
öòYËWDÙb~Çð8tÉ• PëƬ¾(> ±êÒ X Ù@ó/ί4ò ‰By0»»\A¬â6npp¼ÌŠ¸zûr¶ÀoË¢˜›#. áÀšáW-Ðc•r%'Þ –ê¸7¸„šƒ€
²[v©?[®f?ÃÏ%w‚kendstream
endobj
185 0 obj
2693
endobj
189 0 obj
<>
stream
xœíYÛrܸ}×WàmgRL€÷¼yem¢-Ùr¤ÙlRVJÅ!1c9æŲòõ9 ÉIk{“ª¼¤T¶U$ÐhtŸsº›þÄ<.˜G?öß|{ôê*fwÝ‘ÇîŽ> ý’Ùò-ûq… =XmŽÌ ÁbÉâÔçIÊVÛ#!}î…lõpôa‘mu«²îñ¶S}³ëoþÍ’Uåš^,OdèqÏ‹o³zÈ*öìêå?V? ù;ÁŸU›§¿\]\¾_Ý^\.ý{"L¿Þ^¿?;{s{qþö|¥7œàBð!×;…¤‹÷ÙrõOÜ OSž„ð O=.£”œ]t ËXÕÔw,ëØ.k³êUK[$£„¶% Oü05;?,øùRÆÓ`ÑçúXm\$ÅP¹U„ Ñ— Ãö0a–A£.¦ýt®Yažß«< îá¢ó›˜¸8ÇDÊ¥=Õ$íÛa yh LOçø” pyîFPàm0Áatûíë¿Ý^Ÿ½{ã\~}õ§3½ãÛÕ#–±‘:
`Íf)1/M›Û~ Ðl¢$K Éä Ò½ä!8c¹·É–¾„ ¹¨‡Ij@P)}gaW5YÁtÒÀùØÅä¥Ñ /9ä† RvVzny3Ôýó"nj#8IŒôNÑȇíPe}¹ pvG†–ðŸÓ‘Cðeâ<ÂÓY4e’"=N.í¾6»S¬Ðª´‡j+È¡#W
—õã Ç ÷ Ô3£‘ÉÒœ eU!5C§v —Â3ISj§OÌöUA ²%¿rãw›õÀ´ê4+kÖ´‡È·”Ѿl©OTúà 9…}¦ iÄ}˜6–5HçªAqöFm4\Rªµ3BeCÕwdn¨«r[Rbu¢
Ä/ d }]Ph˦fE£ºú‡Óâ€'"M6e6Õ£pá Æf3#âð„#¨ÊûƒZ×á Z!öý=ûéüâì¯^1°±ã@âë¢Ð8Ô'AáƒpÄ[Œ$ðÝ€Q ¾À櫳ӿþl–©˜tÝ‘ \Ë—Ó*iÄëÝXš·D ÿýtÜÀyIò.…{¹ÉŠ½à¢ð§Íü*¤Q:ö µå» µ ÒßÇnqI.ùzÿ·éýáe~SA4ã³ð~ƒ¾ä,ÑöâYÚþð¿g-Ûã¨r÷ `š¨4ï0 èD³HR‚= o8qõ‡‹¢²è@•„~¨!°1{yq~úwÍñ©úÝ,.×]S¡K@ƒvXê)~D·§ß8FË?]]ÿùÖºù%Öóåa‰½V4†3Am³v@ðMëûck¤ú™Í8i8*1x‡6Õ‚êˬ» dfôÒÔ.k7¥œŽz¸YÌ%ÞKƦUÝ=‚4«ïëGú²”£d§Zaô;]\O¤O7œ>ñ 6ú1k
îÍ ÍŸÞ*´µ¬Å«1¦Í [ÉQ‚Ø/Püœo®9±„ÃàåyÓÖ7cg,‘°ß´¶šî±SŒaoÓ²bêQµ«2w¥7²¥˜ûÀƒžÀX[<¢ë™ ”ÇîS$Œë3ÀMßòXËÄD¿#Ú45j~©õÀô|˜""1«á©µ9Ôt®§=TlÊ^ƒÙ‚‹NÄ
=úë>ÛC¬@å
ÀÐ]‹q訦kÐ7ywUÎt\Yß«í®G¡:qE•Y,B|ž&ÊÄQzŒî+ëÍb öõAÐÞ,^¾ÀËË« Ïß`BýåúûÆRýÃOÔÏÒ’*^bh™ð(ðŸÒ½P’Äéd6Ǧz“?g¬Ýd%uyÀ3ri<>
stream
xœµXÙrÛÊ}çWÌ›Á”8Æ`GÞ›Îå
µD„JÉ)D%Ä @ eåòÑ9= ÒòÜJ¥\–l`–^NŸ>¯Ì傹ôÇüÞì'oïböØN\ö8ù:ê%3¿6{ö§ zí&z`±ÇâÔçIʲýDx>wC–=Oîͱ)×2o_ÖìêC÷Ùñ?OYY<ЋéÌ ]s•WǼd¯®žþ#ûuâGl†¿Ùvâ¼ûx·¼¹ÍÖïn®¯çï²lq5¿ù˜M³Nfp÷nÔjá©Õ·9½qéiÊ“Öâ©Ë#?%¶e9+ëꑳEÇÚ§úXnÙ¦®º¼¨X÷$Ù>ÿ^ì{Ö{Éð¬•x»mñ.ïØK}dyYÖt…Ϲ™x©Ë½8Ö79Ï]¿PKÄ`B¢LÀ%8²’›®¨qgM×*o|lð¢Á•V6ßè…ˆx(\Ïž“¾:G6jsþEYp? S½Æç¾]ÃYöT´j…ÏS×® Sµ¢®Êäg_tòdÚá)oå««
"Ñ1üϾ•Û ,.Z†œÑJú׎U*.³$àq,Rë …Ç¾n$;¶0j%;2þ_²©éwû\t›' ¶•»iÊÓ$ôC'?– {P©Ç‡(D
pα(»Ò4Ž(2W ;6c¾ëÚüÑ•¹kµæ,i“·wµ@‡"5Ñê!8ÂÞPiȽÄ5ivtD¸¾ f^ VÖ.*v¬Šï³²PIó¸BoàñÀì–í€ äÈï}i;¹oMÔ÷ÅãSÇ69BÉÚⱂ[»Ü-®(eÛž9乂 sÚ}ïÐõÍjñçë©sWD‘s¹T‘ ù–ò Lc®Fjßüå… Føùó*]_özPß;Køß\¦Ž4×
V
îG"> û«•ïQFÌ $ ÎÃÑ–¨g˜À¼è†òLx”z¦X—QÊ}?M‚¡dMéÚ¨ŽûT ¾/ʲ°ÔPTHN¾£ì,Ó1]sÖLà
‡ÅCikûÜÛ@f‘®I`šòIé¥kÛ.¯¶y³eB«rPS#Ûº4ôóÔ³ÊF#+¢³6“ñLS–‹Á{ì aqGäv¨U?poDì®ÂúIíŽe9Óž›Jù})¹ºÒ•uGuÜ®nlI¶8¬{'Y*UÅ©^P‘ó ƺ’¦xùtº®óÙ¹ÜnñÕ #TÜ3b¦Ðep8@{q{7_Ý,5×ù4IÀ¥aqó°¯2R xF—¨X~8”Å&·4ÝÊRŃbõ¥¨”‘‹[–o·ð¶•MÙó“¬LzŠê‘=Õm§RÖ\<³×ö ™º?“#U'qFG'¨íéaº!
( Î×íH$Ü·<éÈ¡
{^2j ‰ÎUo¿¾B‘4¯T¾MELµ:ÞžïÂúÞxgq;"³˜Ç‰ëZ4òl¸žø§ço}õ“ ¥ |@©ÿ6õ"ÿÀÉË#¬ÊùG}/ KRÅÚ'É>Ëôúo¿\N…N6ÿ4¿;Ëû½ó ÍÅÒ5— CaàGWŽS
)Ízû&ƒ"hl]ž¢¸å?Cç¹ÁŸ‚stÞõi5QAG=Lï ÙM’ªj³
±‡¼ÅãÜ~ ?¸mÌ"Q ûms¢ÿ‹9ѹ9ïEòZé¾_ß\k£þ®#ùß«=7J~P{šÕyƒêAm1ùõH}S\¶édYjŽ7yóB™?Èä¥òª^5ØR4€è¡©¿¿°üˆ‡UWÌ”7êzc–‘;†:@Þcy‚z<\@Óx®Æø¯ªÙ6ïrÖ5yÕî@áäo¤c¨…úy1<ê‹É9UbÅþPÊ=,ƒ¥D¾¿dÙfˆPoMyßa/Vãú £þÈ+½gæÇ!‡R ³»CÝÞÜú*$o–Äœ"R/3Êز‡XMBüI†!°`5dåTçL‰Ý78ÎçñÀ^¦™¥"z¥™=Œµ’‡%–ÄážÒ† …ÊN4.ˤ°‡‘rЋä[ò[R0„PÄH“,®?ܬ——«luóî/ó39(Ï^/!ÒØèìƒñõìô ¦'qjKi˜ˆ I§^” ¼ŠjW³ÑpWÁ4¸J«•üÉ”€Ž ¶¯kÄz!Ä]:ÒénœjàÚÄP¢ ãj߸ґõÃ03QWjä˜C‚U|Ûzcd^ŠþÑ) ¶¹)0õ@ÝÐ$Ù°4ø:mô¡jôoN‰´§Š«ùzµZþÎi0Àüª<í Â4?jyFÿè>”z±éC»¦ÞÎ xCF‘.'ˆ¦ß L>žVê»±g*6Ôf½ °ò8ôNT(mÚæ‘ ud9¼&Ë Z [„:ßäÙ•ÐöÊ{‡:ZŠé ÝjDí˜Â³5±ZR~5_D) ™œ…³§¶ÑÜC3V_ëü³3’æ¾?ˆˆ1wº)$ÝIj@Xi+ªwBš¬ò‡’ò h¼Í–+]ø4½Sl>dcÁ"Ò 3Î+|è¾Â‡ýžÑ–ÛŸlC^°ÅÕå-“ÝF·<Ïù`2 d
Þpij* j
¨ä/• J=ðÓ~TˆRÓdžQ¦-³å ר T×Z&¶Ž©ôi– q©Ž&¹â¦‰>F#ÛÞdkˆÎƹ8vý {]…Ký
H¯®o®ç¨ÒQí½¯«7cÍà*ö¶sظ0iÒ CLirèg ¯ÃE búƒd0dwÓÈH´^0ø焘ªãl!¼ 3™ úik`tA]#D„»‚, ‘ÕjóŒ9P›BÔÿÜ<ˆX觚Sn–?(Ó;-/è2=4éŒuM]Ž»%Þ •™¥neçs´KMh<íÏ-U®?@ “Hu.Ëùû³Ž"„ßó¤c&ý]&>ã^ãÔåry>ߟ»AêiSï÷ÇÊvåmn?ó€¾Ðœ~¯ø <ˆ1í¾:$þ0"þ ‘Œ>) j5±i-êQ<žPO ×¢”¹@ÃDŸi»ð2cq?Û¦:àvQ—@3r#Û ŠqõDqjõ\E‚µŸXÕ¼Žh“p…êjGª' O{¿ˆ„¡jð†¿m©> ÊÁ0¾ë÷-GD¦ƒZo̧Tè½\}#x±
4JË¢÷Ùd+í?Û„Ü-Ó# GŒØJµ´áTZ¡·x®Ÿž,n©.¡Ôqá¿ËRõ õh[bÐäÎÇöa—Ðgk}ØpåBGV[-·N®OÂÑ9CT5Û42ï¤Q\$mõ‡‘Ñ= :UOÝ÷ã«vÍÔ¨>
stream
xœÝW[sÛ6~ׯÀô%Tk¡ xÏ›7q§î¸±×V;Ó±3 Š„l6©ðbGÿ¡?zÏ9 HÊiÓÝ—¶³£I$œËw9üÈ—LàÇ~ç»Å·×1{è‚=,>.$Ýdö+ß±aA‚ÖÛ…yF²X±8õy’²õn!•ÏEÈÖÏ‹[/ Úê^gÝá¾Ó}³ïï<ÿnɪrƒ7–+
.Dìý˜ÕCV±ß]½|¿þa¬üˆ‹…â*Mpsï,Ë YWÖ•fu¶Ó¬Õ]S=-׿. §1[ç~À•
HxÔÓ ÞtÃçRÅæ:nÓ–} ۱‚m4{n˾×5ðÖ?j¶mÚ]Ö³ï/oÖ¸—k”Úý__]^ãÕ•à! ¢$|!íÝõëñô„ûIš¸°Nß¾½>»¹¡'}¨H°•TxKp姦’ϺÕt.+;
…r¶¥dÏeU±¾=°¾quOÓ8òô ø°ŒŠÇ¦RHß ëË¥Š}X¬¼®§uÂF/aWA$•Þ7mÏêa·Ñ-k¶K§Û§2‡‚a””¶VFS""¦D¼1`\å‡<©;AĦ±YÝw˜GÞÔµÎ{ü‰gPîY]0[¯±ÃN·eø9¿bYQ@ú gçÛ±6°nC§O‚ÄV}(«Þ”
W…ÜOåŸD{뵇þÑ hÕìu›aA:–=,¿¡T^VÖ]?BàæˆÇx88†ŽfÏãQ
Š1†€ÁtV Ÿ5;@¡@
®–"áaèJÿTº0Ð Zĉté!"S[‹ÎNM5T‹ÊŠÏ~{-…SÉÀçQì~óÓõÅ=<|y± !Ã$ ¼ŸÏ(¡IWãÌU’Àà¡ÄñºR”;½j†žmÛf÷¢Uù2Šäî;á3Ù¤’‡‘<zÓe]d „Õ•äTZï—€ð@‘nH¸›¤¡—T-ðö@y®\s 6
`-*ÞR…ÐìfèªÃ2
=NywÞ)-€
Ç Š‚“Å«+ ¶0qóòj}Ⱥ¿9»^&¸y}C;ø³ª(¢*ÞèÞö ’W@D¢b©RPóÑ;##ùº% ×€>£ 9=Àß +À Áaª9žÄv‹l¨zj ¡[¼<ÅBÃîZ€˜º˜Ü2±ÛvÖ {òBŒ1• M- 6òö56ðýíÉìÏ{Î9ÖѱÛûC™ùuYŽœh'€3 ù”íö•~m£Âu…,„{2ºE áâdþOžø<à!hW¸@-Y}{d¬þ8€u†=Óð‘¢òú„ÍRÑêÓHàpì†(P¡¨ÛdùŒ”pØÒN x j
Ì´qƒE½0EÅàòU†áØÍh ;Ç45 ÿM
jÍÈð»@Íϱ{Ýówë³ëï¬êá)O\#NßÌu;HœÓxgGB½Jbî‹tÄ…w•ÍL< Gˆ}BL4eùcÖ²¯”uŸµÀûÞ(§ÏC\…@G¯æ7S$¨Sjò¼ØJ¾eiˆEtû©MûêÇlñ’± D©7Î$f1j
ôÒŒøFN$¨A8Á þĆݛ›Ü`+¡EV AÈÜyHR ª•D.ê0
Isñ‡~
ØYðnÉ™ ¢ ï~º¸ÀoœKzCí•ÛúXåP ¤…+JÎ =:ÇW4õ+;åSÿÁ“‰dýfÎ>5Š8Úf‰ ´×yù[>+§¡H®!lS«çËÍ‘sÿïŒóý?eÜÅå›Ó‹ûó«€À>s
3ëßNNјxY°˜ :/ Ôf„)›ð×.a<2”Þ¼ùÔýì} rØkËÂy1à=Ë ux±êaN–›×ç£xÐní<‚Ò.¡ç¾_qŸ`žÑ—`LN†¤ê¬–wvc'/Á8eŒ¯ÏÁˆÓ?°±«Ï@<½ "xÉæ$˜(¸Ñ? ¾ p£ÿ¸Ñ_Üà‹À¾Ü8œ€ëÿOÀ%•M“?.lüWW
x …Ö„Ê6С†òè`Mwî*˜»«?ù<ø‘Ò<ˆ¯c®HžŸâµ³õâßðùzŠ€endstream
endobj
200 0 obj
1985
endobj
204 0 obj
<>
stream
xœÝYÛrÛÈ}çWL)·Ä1ƒë£ckíÚ–bÂÙuY)DŽ$Ä$@ måüÑ9=\hº +/±]%Š˜iôtŸ>§{üù\0ŸþÚŸ«íìÉë„ݵ3ŸÝÍ>Ì„~ÈìÕ–ý%Ç‚”¾Èogf`IÀ’Lò4cùv&ÉýˆåŸfï¼Õ¾Ù\«¢}¸nUWïº+O^ÍÙ¦¼¡óEùÜ÷ïeQí‹
;ºzþÏü—^°1Ë×38êÇÆx~_¶ Ëʺbú°/Õ²î¾èÜ Ø§yƳ4’‘W´ìf è·Io_n:ö©ìîYm½ù8 ¡§vS¬ÞÏ–Š0öTµ6&ÛýnW7 ½@¿U5½˜³ü^iEÀòˆ\ËÂɹci;%mV¬®60·ºÇ'ÅõÞ ¤½Þ•÷t½VXX±„KD§ÿóŒ¾1Oéøï¼go^¿¸¸Ì¯ŸÎ%—‰÷ìÙÙežŸ¿<»x“_¿\j‹ Ä 9XÍô怶z—Å<ÿy¸še<9|+¸ÂijmM]ݱNm6%~º8’ÛÛâs¹ÝoYµßÞ Jõ-Û–XÕªU]q²ÑvQ+ÊŽÝÖ
̵ªApCÊ‚.–a}¥VqS;b ôy˜&äŠGQ£¥} ïUÅ
ü[u%¡?b`âóÄîÿ¨ØÏýYEÂS™·Æ½#¿tž~›}«Öœß²ªf]¹Uõ¾£¯ÅS €²êTS¦kuKÆ™ò4L»©¶[ì®Z¯@æ2 'Y@½ öñðÛlزod>uæaàÉë •Æq@Û‚ŠÀáÀ[._ "k¶< Îó· ˜8¿xµ4Û\Ù €ƒÏÎ^ÏcÊU”yùãð‚ƒ>‡†Ë®Öa¡dìߪAèT³-«¢ÃiÚ®!¡övESl éÀñŒL¬fŸñaÓ†=ž)<’ý ¡·†Úûz¿YSÔ( _6ŠU°JP|¨÷Úô"W2 JÆŽ‰TÓ•_VðK—¬N¢®Ÿ85)^·…ÎøÉ¥NPœl©€>ÅL„?å~æ‚ cMB^ST-ñ‚ÎÅÉåÙK½±†
SÕ]Y©öT?[•qИ™ ZÝÕ BF¬dR(|›Ãdæ¢4Íbž¿½<›¦œJ¢©-–‚º©À²±
þVŽãŠ¬?œµ[àÇWË%C ÷À†$A1û}9 ™MqjrEÕºik—¬ª\½wɢ߇tPîpìö^ch‡ÕB»t#jp¬ß•z—¡ï–•:edZWÙnÉÛ²{`ë¢+nŠVéªÖ¯Ñ 凙WT ½ÕÜ’n›zk<Û7ÂÓ5ädµQ»×ÕÍø8à†z" ƾéén¦oc£ã²ž)¶ƒ-µVävü„?9¡/¿|>%¯ëfmkÈ&,0Ä•ôˆó>Öãb´_–kâ°Û}KfÍEÚä>S.£cúqHI¤HæRAä[*ˆxê § Z|‡ lñZ& t‘ÃhÛ½U2 x Ç°’@8`YzX©‡×Æ,ð›âÖeþüìõÉ)SºiAà}^©Ml_)2$a}]pv±S±ö•÷QÇY¦z wGÓŸd©gP·p †ˆR#ß-z¶ŒKíÑ~7h¬´ Œ=Hƒl ¨+„îbÉ"ªi½Ç0ÏÈ0’ °„¡p Öó ‹©ßòš û1õ–¿ ½Kg'L oÒ¥
Áì-“7Tÿ¶o2`$"š’Ÿa[ê.}¶ü“ªZÕ$†(Ëö@q`£Œ“¦hŒé_ÏÞN:„ÿ+=óvëCB`ô„>Ž(Ò d?b"æûióò¸g}O=Ø‚¤G)e¿ý«r @;©é²…Ô• ÉÁ¡ÊˆF24¼Á×*‡„ 9?æq6Q9™„#§n4&HS,W až¼xY¬>þ®[p t<@àSyWÕ
!í–ÙéAØ¡Ÿ D™é¡¸›GúW<,«¶›ö
’²&Ò^#-M\`VÛlH ò…Ûär7£lú£lêÒGs•m¨ˆ<ý¼CCkæ Šås– üH|,Gq’È(èëż €aL<à)zlÔY à LQÅ@èn…Ÿ¥gñ6*Ö¤‰-©¯•ò©#èPbX{€` ÓœnZ\ ³èƒ`vøõg
ÉNšv(ü{„ãðùåŒ~\9#K:1òû
åŒ «œ ÍbÂ0‹ ÀD20ÐÿŒc–£ŠG©}[ŒOM>{õד¨PjuL Ì´7 U/Es^Ü@_t[H“f]¬ûª™0l&xïÿ#j&[pé*æv8%ia¿ÂðZЂš‡ <2ÓZ×ÊuÔ:˜ Ð{ó$(Óv8 *rHØ0 SwéÔJ`êÌ ©ØQ˜Ö.×(Çò й+Zú®Qœœ{oç°¤‡@ÞÓ2Àì õ
‘yMçš8$OÂÔ ã‡CjÝ1ÂId’
.š[u¦S Ê B×CîìG¦)°¸ â#:Tœ¿Òe *
czýXoPLn?×XÜ[óÍ>8¨aiá6ÅØ&‘ýzi×_Æ÷’²››~4Ù`²©ÝªFÓIÛ ÑD†Ã†Ä$²nÞ£ÊW
9¨ïÂÝ€¡ÃÜßam—é£Án3Û¦~MzÃè (]γÀ{º\þöü±3ƒŒ“ e¾”L˜vËϤÓ~>Ò˜'Bxݧ‘Þ xq(†×Û9rtÿB¯Ðµ„ë+ÃÌ$·v׊„zsÎ 9ù}u ý¢ ÃÆÚ$h þFW3Æ÷ ÎuóU©sÙkëÈÐß®/_ŸÿÃ5:,p’A%ŸNÁË;£ þ|þâ ŠˆµB§%¬Ù<Â… =M HLܾ·zì7Z*5±‰."Þ—ÕñVÀk†™/™Hü;¯RŠÆŠBgíîšÓã
*oßi© ]toÛ¯tª9mµ‚ ' ©#jé “9U@mwæt.æ¡cð«ÉÕ¸mcQõ€ùû
C]d~ýTð§ D]CïRt’º¸Ù~G'Ea^ –[\æ¦{|›Ù+é|à‡Þ2coó¿ÙK
üˆûëPüŸHt݆(P‚éˆM$Bá£{°‰ä±CåÔ’ZË‹ ¢˜ ào¢^övª¿ n§ÈÎqŒ‰8嬛ÿï1ø˜Ib±wÞùíXy×Ê` hùX®My¤Iˆ •†ZŸ Îx"BoºSâÏ(í×&ïׯ.úÿÓȾxóê¹Ýß«pré( oT·o*µv`F ¸À h.8Ýÿ EŒ:Ï }…”.â— C¦ýU+ºŸÀf£ßôtêïÎòÙßñ÷?8¼endstream
endobj
205 0 obj
2559
endobj
209 0 obj
<>
stream
xœXksÛÆýÎ_±ß vÄ5‹gúIqèFÕv-:ŒÕÑ@àŠB Jaƒ~tÏÝ RÖ4v:[` ÷qî¹çâ7æsÁ|ú±¿‹íìõÇ„mº™Ï6³ßfB¿döW±e߯° ¥«»™Ù#X°$“<ÍØj;ä~ÄV³Ï^±o«•w‡›NõÍ®¿öäõœUå-½˜/‚È羟xÏë}^±/®žÿkõÓLÆl«õÌ{óéãåû«›««Ë廿]¼[Þü°|;_ý{¶ðy„k rÁ0Z~þɾËýV¦Yj_^®è¥O/¹ ²…è•oì¿R}Çú{Åò¢×¶‡]ß0UoÊÍ»µº› ßË÷UÏîš–]{pa»U}[ðÖîivªÍû²©;®]
B¶ºœþòÙ»¸ÓÇØuk5"ŠŠô Êóºnzv«‚r¦·¾þ(|—™ð03î|Ö±YRdnlh®–«·s!ôyÞùÅåò{ÀAdÀE£ìX«ú}[«5×A Ò”[©x¿| §¡ŒýÀì<Ë$…ÊS5œhö›{üÂAÈ \eëFuõ+ÚÂLi²#xœÚý^_iŸ+µfy}´1Hx ÖWï°7š%æyÞ戼j¶ÊG©/ì’³Ò½ÔÈx’Hßá¥îÆs%—éÄÑ@;Úl‘“¦~Úìm:iý$#©äa ]LO!m»è/$ ÈtH“0ÀÛ–›{ôµzª) ËÙ6/Ú†õù¯e½aj®ÓfÞï gu@Ü[L¶s‘r_‰·ÙoUÝwœîU«€LuÆÊþ•A |í}E<Œ\hºvð a Djý ËŒûªh íz
› Ö]ÞuLh° „\$ò¨€PXb3Bë'Ø0£Â1 8à×Ö6*Ê÷~^~¼ºxÿN[Œº¼õ}‡÷!Ÿ˜›F® :
VÕ H§÷#q}ÛTìñ>ïÙà ÈÉÒ(ôTÛZ›;†›_¯.¯hmÞ÷j»ëéÏ}§ø|Á¢kï|M¾—5KxÆËO }½+”†¥@Û Û#íî{ÍzÚ6½¢¸³]ÛôMì<hg©M `Ë•aÍ…»÷˜§U‰³Z:åA2P0Rø @Ä·ó Ðaìá:¢QZœ!ÿeqò*
¶.;
ûšÝ ,—›Ëµ+8©FM‰ë¹³áhŸeBð"nß6#Éø<ŽN½„¯·òßu®Âؼý_×i·¾í:³õk/“ß~™üªËt4nü?JŸ U-š²ýz#þT>ÅÿɈo̲1"xш481bÊÅ70áâí/ –Ë–Aþ¿@Ä´ý‡Ö¦ O1ñÙãßÏ$<¬µ£úÄ ä‚øÈ®r%
…D%z¦u#nèÐïè‡A@åÕ^« [¸¤=’Ôñ4‚$m»]M5 Ù¸…¾uÝ+Í+ú‚i»(Ÿ”Õ…{ü_÷eQöº‰ží”j]—Õ¼H]Vò(vQ)ÆD!'q0°hèXTµ}ùTä½âìÜú#²hôÇò ò4N¸p«rôgrdý+£2øjHR³¤ì> é¸ÀëMœÜH xR§ÿ„¬&µámš¾„æ¡tjÂF7•¦ú3íx§Ú}€H¡*ÃA:D¡‘-VÔkJQ18$®ËÂœZBl—k
g Ef+§<
]—äo¦Ò/Å–q™4*–‹Ð‰`aÚ(P.&ñâä$Yö4ɵ–âóº1ǦaÄáٓ4g}»ïzóhµG §Ç‰ A$]¨!Þ7'·Xe¶ Ö «8»ü “UvZ3…¨ €Æ -2a{3Ž6ÖàÛ¼C•Íˆõ}^jm³.7e!¦+7u¯º3Ö6辚k¨Èå¦%L_{oÎ QÙ‹BkÜ<úÑé°tûÝ®Ò ŒüÉOå 5øÿRë WÙ”@h-BˆkÄÔ»u#¦Vîíëu¥+àÍ9›^{íéÂËÑ«iÓé@t)›JÓÄ@
9c¸!y¤)•>7ÝHÑ;§‰å Zd2¹/+àr«PMy½ àÐíTQÞ X^áæš 45S‹ Xz22±ä™ãLÇ»oÎ/Þ½}:/³ïG"Ûò–öûôèHòxìãÙ ,‘Ë„Òcˆ ós¾šò“¬~<6㠑ȼœJzœøÉ †‰?NýM0Våùr£™Œ©}"%¡á:ä¸njbµ3BáéÌ4óY@ßÍ3ân -«N.msÜJE‚IH¤nÞ Ì Þƒbý,I'f˜pÅ_رSBìÓælbB=¦õx_æ}ÚÀ®L+n&Øea"¹o 8sQSTZpB;tš ®1ÑrjÊu†;£ŒûéH6‚Æ‹þ‡É1üº}Q`\§T¾Žga^ ·™
9™yZTtg˜mã;ä™LšÏ]dLŸxNÑú ɈªîŽæ‡Êݾr
BL+
!E¿hå$!
2 z!œÜÀà0†(ÎÄ€kÝaÃ*Là2 £֣Žª;šu\w0&1f²a¸Â´J-CK‹Px–® R# hHs†~öÎò¹ŒR`S¢+LÔ› ]~jUÄ52Î4Ö'3æP§ #xF! º×;Íj¤È—[ø‘WúÓCߘhJH!m“ó>u§äƒ†ëë N%>/õ ß_ž—z<~wHÃÔ`x Þ)œú£Z›*~ ›ï}ƒæWÓHWÖÏAr4/Ü5δ—frrÀˆ„ª\Ûæ2½ !ze>‹EÈj4n2f·c ëÀé®ÔÔZö¨ }G©éÛQŽ'á)Má 4¹DC6ŽêÞ—ÈS¦Ó pDÕh'1ÒD¦cAÛϳhxž¨õ@\:òÄOGmbü” ¼¾0 q;Bý¥h¹šý?ÿ*´Öendstream
endobj
210 0 obj
2298
endobj
214 0 obj
<>
stream
xœ¥XÛrÛÈ}çWLU n‰cÌàþ¨UäµÖÚ•"qw“’S*‰ˆA€@)Ê78ÿœÓ3ƒ iÙ±Ö¥r‘çÒ—Ó§Oã#s¹`.ýÙÏl3{}±ûvæ²ûÙÇ™Ð?2û‘mØK,ˆéÁònföI% ¶ÜÌ„ô¸°åãìÆÉvMy«Òöé¶U]½íÞ;Þû9+‹ý0_ÈÀå®9¿¤Õ.-Ù³«çÿ\þ<óB¶À¿e>sN~»:¿¸\Þž Ÿýúæb¾ü×lãq_¦W ©W]¦ô‹KO °OqY‘aNÛ²”eë´a?°®Æ÷ÿ¨¦fj6E•v*gm×Õ=«Ò
}¤ìS©Øº.sú_])V7lS7ŠeªéŠOö´tÐÝê’ûq8Þë;USÜ=±n´Í^(¹7,x$tÌœR
{,º5§u~Ì}‘$æ,Zä›À.×EË6é‡y“D†±ƒû[Uµ°¬*ŸØãZUlב¢bY½Y‘[E]郵
Õ×Wµ™”°vº{!¾¾>¿ýýôêla,vÅÞ7ÿ¸<=½¢Ç#¼„GA Ì }ãòˆ‹9;»3ˇ+}ŸÂ•_¸ó¹„'¸/ƒ>Âõ
ˆ¥ïèà|6D"98„ÍxnœpéýÊJ!lUÝ1µ.ßÃ…²7÷AMð%ã$öûÝ&VÉ+×ØXå¡„¥K³Lµm±¤ +f‰´žÃ%ÏÀSg׎áÛê‰åênþjÇ\„}È°:LôòtWvÈ~GDnYûÔvjö)r
$ ¦¶â^ixò˜öe3 dÀ³†·Ùà‘\$±EÓÈÙj.e‘ήÊa:ìJÛv·A°píÊ j!qf :˜:ã´ j%?¦Ú.]•E»Æ¾”NÁ‘³+JœTl:Éå2‘´{ùÃsv§¹Aǘᇴ¡cé½^ F<ˆ¢¨/9™x&0EÕv:$¿^_3@‹Ñ¤Í“Ž9hÜu)$}fº!1w#ϵxsì)—§¿°Ëw'×ïŠ÷ŽÚv«6¼Ap¡VAD‰Žñ t¼Xjá%5¼dÈý!µÎԾį§(SÎ ¨› G>Î…LÝ|`Û¦Þª¦|š‡>OâÀwLXÈOÀœÇæÀ¾0ή¯;½:A͉ٱ4;¾]W~?»¦ìäxB«D`r8¼I»žFúÚ>¨T½h”ê±nPGºàò¼ gÔbÖ*û@¨ ¨ñxrM¼Ó‹[Ï]hl£HǶ0‘K—†-8Ú Pb=ŠÜús¼œj9Tóv5~ ¶Jâ¯÷Dü'ûG^4*ƒÆxºˆf¯-ÚÊ^3¡î[6í#_u a,h~TéèH½¼2ú„˜ZÆ<Š&»=“Ã^²Pó‘¾o›ÏÅVU@ÄÑ!í^mvX¶¢F ¶)ŠÚfÓƒ@ ýq„=#¹w-…À”è«ýß6
Z³]W”E§õè 0£ÔA¹ìÌ')
8Œ}vôjD;zh¹‰ï ="ð¡}?¾±J`~Ø'"þú°å‡ÃÀ7ßÒöµaà ˜k<ÞŽL‘Ä 28¶WQ®û1„ï=[QøÓrš˜†_†-HŒÁæ—æZ±â>Ït쪘Þ=ŒCÏ.4[è¦*¤·¥|4Öà ~ Ãäó!l?áwÆ š¥Ê(óÃhK§ªKä¦[*ŸªLóZ™Vù¨GhWzZ6³h€
éóÞ-¨5#Ààª74ôǶo m½¡kSté8Äžb£$µµn%˜A˛ԯoJ/pÒ* ì\SIÏP
¤KXð§TÛP‰ì§j‡æÈi|Yl빤‰À
œGúId¢âõ A’² juÑßñœ*1EOh•f µÒhr*|@¤X¶9˜Ažï4WçoÎÎO_øBGØÂÿS#ǨµëŠ0n‰
M Æ yŽ£‡ž›cÉã'm'Tà‡ã.´
>9àõ‡¹4Ó‡“–EnîÔ²·Î BUÓó7¬
iqþ
ߪûa6¶ÒŠfã?ˆo÷§cWȽüÓØŠè6Ó(£~:PJÔ€7¼±êµ_úD'ÕwªÒÒ\éãl|¶˜ZôddÔ‘=ÂF‚D\bÛ…*·} æPH¢&&Šùä¯p¦]Ù¸öÒÞètÙbín»›îÈ+½>qþ ¸Éíï·oÎ!jƒö¸ƒò‹Í›3ç'ÚíÉÛÓ“wº¾&{¨š|ŒëA,
Ø0{R5@ØöŸ–¥Ž*ÕÜÔ‚~D ’ ¢úS ùOæõ‹I€„y4L.ŒÃ)GkCé÷›B=¢¼|¨*Ùöhû**NçH<šgåÿ×çJφ¢] ùѸÛÐÃñ_‰[¾6†@3tôk?f‚Ž1ïúáØIHÄê|ê°M*Ôœ-S(q
KRޗËà$é‡`[e)Ñç4K+êHzeæ”Z=^‰}]ó ?Í9¾›¤‡á·˜ót6§”ƒÅà¯PÚÐèúëEJH |k„j
†©éU…QD¯û¶þPO¹y˜\¬»YßÍ+ ú~W謁çò~èÆ`éû{eßmµÓ¤k¼¸ÐdQ-·ìq?IöGÿqðaÿÆÁûöâzù¢tcOYSO¡ŠlÒB×™û /zΤ½º'¹ˆÃÙ4ë×€‚¦¿þ•£øyO 2b öÙèAzFý_Ò³Óåìoøû [F%éendstream
endobj
215 0 obj
2575
endobj
219 0 obj
<>
stream
xœ•XírÛ¶ý¯§ÀûÃT+ÁøݹŽ“ºuãÔVo¦“ÜñÐ$,±¥H•¤ìºÏÇÉÞ³ ARŠ3iÇ3qL‹ÅîÙ³gùs¹`.ýô¿³íìô:bëvæ²õì™Ð/Yÿ+Û²ÿ¬° ¦«û™Ù#X$Y”xÌYYÜÑ‹ùR.wÝÈù)öiÉž]=ÿßê‡Xz![åpK^mŠ–aIQW,Wj¶E¥Zö¸QÝF5öö0w… :ª)>bA·I;ü£X«óÒ<¼d™j:›÷usô>‰é}¡ßþ^Õs8K[®=“>[]ÎVß¼wÞmTÅ*5]×]‘vEµf)»¹¹dY]U*#‡'÷ðw•·XKž ³´S¬¨ò"36Š®eE®ª®èžæaï—qAŸnC1ºR„§J?=«·[˜“nû¨ÊœŽFZ÷w¿á`ö¢+ÄBŸG7º47rÆ
…14bÚeeœØÔˆhE‹ûuHÙáí»F´ûc8²n (¹ç
}â;ëò^¢¾ü@šDЩ—¤å^Q*ÄÂ``€ péI›ãr<L$y‰~í{ç±(KÖ¨nß 6*¦š†"TåÚ•¾P æ’Røƽ¥ª;vgâ¶aÌeh!!y|¿Ù&Ö*çìBû°$²Ze3?á‰Å½·)½ë7e3!xºýÕvG/ÝþE(c{ÇFƒ1â0Û/vƒÄÀñ¡¨÷mùÄ>8ÈJÄQU®¾“J›²P
¨,ûÜÍ%aNúÎ~m¯Zß³¶F6ÛºéÚ»›‹ÄÜ|ßõTRÕ¬¬qÆÜ=vyˆû ×Ã~·ƒ 1GÀøûFý± À©R¥91žîšzݤÛ- ¼-Ú.ý}ŽÓ‚¹úÊ fAà.Žk¨Ýg™Rࢦϋ«ù ¡K\žôeí¬Ó!¤ ÷bT¬
i^ª¶¥]Âtû9ø¹N¤tÁ [†sÍê
ñœÔð¾ì&Þn ‰ŸÈÉ–¸þÓÆ€;uM]¶ e–ý®ceëýd&û~Ð;šŸPhlÁƒÀ¾k³< 1ìé/3l•´Æ‹x&É6ËeB˜j,Ób‹äŽåy™Í‚„GǯF[ äX}¡¾Wê†VïAwŠ•O¸9·™Œi÷R&‘>b(µ$1¥¶·Œ‡Ä<ôãØò¸×¯1Q5v8W ±H$¸/"ùÅæóöüüš¶„°¨Ý™t!‰àÙŠæ´Šd…^%$šJlƒ_Nãê< ŒQ*ž^ ¦ü(0ûˆJ×sÍC pUT Þ777T×:F“‹PO ìýé"KÓ¹@}adcç|áv“Kr`Êæ=¤m©¦>æ`êi¨¥¿×¹Áh–¼ÈjZ¶5Ò¢[% )+K+P©º( q R Ô–\M±‡ÈDb/ÿ &Õ.§ÕÞ9kê9”Ü
MH@#dÚœ!*AbûêâÍ«+ Hsš7оóvJ,q`Ãæ÷Š¤%DÌi¯(è U¥w¥²º¯/H-bp »}ÿ™‚X\ï³r] à¬ûšiq N[FJ
´==°•bè6üÝx„Ö"íÖ¢Û3îæ‹A¨¢ÃÜ÷á—¦BcË ô‘s·ŸFÅ%Šƒ% ú‘¬_íT°,Ò öúæG4°æÏm§èWºçê\J5Ž†BmèÏ®I!hÊºÓ N1h SˆM EyÚ¥,½«÷Ý ã$®
Ù\úÆÒÈõÏÐ â}«at(‘9ÓD®ÏÛ¦O´¢"2ƒÂh
u T/<_ÃinJ7#ç ¿—C÷Po ®^µ÷øï¾³ •%Æ›À‹Â µÑzìµ …k ZÆ# ‡ÒúH$9oºÔÑ9¡Ç½(œ’' •©¬öÁÊòˆ7]A”ÔÃïƒ3åFPi΋<×7±Bžˆ t„„ ønÔùXÄC
_¿xóòê§ÛW—ç‡øjñÊh¬]¤¾aßPѦ†žÌô–’ÊùXÅ@éWú/
X$^C{¨ ¨ zK ÷‰ÌåõV;¥µÔ†Þaz–ªÖµ‚ ÐŒùmÝØFìT†!ÑxQ´FéEB¾Õ30Õîé‘Gk~°hÕG²üùž¿~ysuöãùê ÆOás$‡ŽC¸?™I¢_pNíz×K²ºBc“±ÙÓë)]ÅúÞª#Ýô2U4þ´u¦¥eìúàN‚Ü&Èй "ôâ£ÖbSw”-v”“/㎺ßÙÅÛïϯo//nþi죦±[°]9¯Wϟðíô7¹¬j,¡«‰³b·Ñ“cM >ÀÅçÐÜ òZoLÑ@vûTuà\ÌÒ%T}V7žmAÜzNm
Ó4Š³4 ½—-âºKµ2˜öM?hô5îÈ ZeËõüš¶d¡Ý¥(9… -Rˆý]§»'Âκ!Å„É:'±QôzZßw½Mm¡¢î@nSŽì_ ³À´0½ßfg™NII
Ù`”ø-i”¡ÔÉÙ2ÞðƒŒ/íö~lp^Õ†ýØ2ÞØŠ›«ñÔ€»4$_%ú!ÏtLÝÞ^WûÕåž8¸+¤ÄØQ`Ú3_$0¼ý™nwnF èLRËÊ}®ØÉõ™¿¼ùþÅœ$Ÿë†ÎÉ‚}ÂßâÛ—ç7Ÿ¶F F\yX#'8÷Aœh/N^ž¿êo èC¯yã,ûâ—þe"ûI uÚådD€º±…|bpgf+3Vi ê9´O!É)ý½ƒ¾6€Æv Ñë‰~|fðF´k6¿ÖÓC…†Ÿ½bê="ø}Ô|o|Äu5¤sÕÑ›^[ ·®Œf|wÔ,—°æ
õ†1¨ëvßž>>>Î#Ÿ†‚Ðá@QÕ¶%¯›¹Gä„F½>Íë¬=Mw»öÔ ¥Iæ–oºmy¨MÇ6k¾µàNfô‘3zpo¦3ZèF¶€‚ 2x#afæú‰E èc¦‹¼xÜš
_EÝ<èçå¦Mo›Ì¿2¾Ýæ¡ ¥ªÕÚMúiÁT—qöNŸè‰ˆ&¼QŽÐɧ9Ž½æcÆ$G^Wv䕺æ $"?´ú¦;àa?ví ç§
úÈ!{\Ķ*Éþ¨5C1)ÑÒÓfÀÓTŒ.dè¼Ñ | ТØî?Ûš/ÕÀáÄ`yÑj)>ÌKãh\;¨Ïº*I„Ö ü]Úö²•ö÷JÞPT_ T'³ 0Š ï+å@
†bÿwËÂs©
ÃÇSë¢ã÷*G ØÏÚèúÆž„Vv§uT·è ºdB·%“aÿé¶ÎoQMœþ¿+!áM%ÙÇT;ÿ~YP¥9Ôï T{¤„—ô%ßwMƒ7¡µ#F(ÀxÒ@$&~ϳà? 0ÛHyhÒf£çCjÚ ¾GÏÎW³Ÿñóó-æ?endstream
endobj
220 0 obj
2755
endobj
224 0 obj
<>
stream
xœ•YÛrÛF}×WL¥¶J`V c÷Ý'Yfl%Œ¥é¤\ò–
$!0 hþÁûÏ{z.¸Hr¼.W,‡fúrúôéæŸÌ傹ôÇü\ïŽ^]Eì®9rÙÝÑŸGBý’™ ë {½Ä1}°¼=ÒïI% ¶Ü éq7`ˇ£kg}¨‹›,m oš¬öí'Çû4aE¾¢_L¦2p¹ëFίiyH öâÓ“/>òB6ÅË
Î<ûp5¿¸\Þ,ó›Ål±8¿xþææìtâã0á‡ÎÙ»™zi
§`ÇZ½-$½í\¦“å ð
Ÿ&<`=>Å{‰O;MÃRVTå ƒ¬ð{üµÉ›tUdÖîc:Bò Q‡ /á¡/õINsè΂ûq û+}Eƪ[ãqEÓäU9=ÃÖéz›—wœ-èÚmÞе‚þÊJuuÞröú‘ΞŠÐåIu.m²[ú\H †Ib¯ó‚X]— Š–¥EÁÚ:-›Û¬†‡uÆ6U™±Cƒ;q]¦îÏ8û}›ã®²jÉ–©ël¥ ?g: 1]Aq”qûæ—uÓ NG±0¿ØV‡bÃîàßöP·lõÈÒ¶ÍvûVÙP©»d„WpqÍåRúHuv@àÆQkNÈv8ÓdÙŽbµÊت®î' O’@H'+Õùn_d»¬lÓ/6,/•Ï9ìi·iËvé#«³?y)àÐísòñ{¬C¨Üà€ªÞd5»jf hëu–m8ûäœn6Ù† Š¸¹ MC «X !ŒŸ@ðbëoöz Ô‡¼Ýâß«¼Ý¥Í=™ÒfH·Á*KWÕ¡eÍ>[ç_Ö* «l›N¤©•ÏyU7\—‹:J7&âi²òt>¿ #Ÿ›d
î†Í¿ß¼ž.–Œ‹˜VeñˆPì÷UÝ"0Š¥å†’zÒ™ÞšG‘ÏšrP({•ûê‚.÷€8Ý` c ¦
ý/!"-éMËH!N†<4%à<>ôH ¸ŒÚÚˆ"¡Ž®êû´®å¦Q™La$®ÊÛGößÔ +t)<´¿v ò‰'#T´S¶*têésOJÏÂ]¡ÕSî/ç DŒí몦è±änÜeÙã¯MZWEÃÙ¹ªhÏç à}ó„
ÈPFÔËcm¨z}
žiK® ‘‘'EŸ>CwÈ WGR®ðÃòžª-…—"}D¦lôFŒŠ>S1F”¸4Ф j ½(ážX COS’Š¹
¹ºYÑ }25B•ˆÄúðÐ㟊©c!:N;Q´ –»-(’íò»m 2#Ûò²ÍêjŸÕé*/(§?*x×èŠiª]†Z
Ô1Z Õù^ÂIRô„DÀ•!ˆhœÓ«÷çïßþƒ¥¶éH
E´…ض…ÏÕ°ŠÍ‡ù¦+F?æÛõ‹0,H§&bEU5Y©ËÇBU§_ĺ•RØLœ¤C*]†ž¤Î—D• úïÚoƒ4ÕŽˆêˆc(sÙ5Þí9ÿI×-ªž˜ô ûá@×4ð—ùï—«×óÙo³ùw‘ŸàAôÝz½Mkö#ìbû´Nw²®áä:&®ä~h}ç‹>&’ áǶ¨UãÍØýD¸NV¯€¦çƒ"+
áÆ<”£~Ø]8î‡Åí( ¡½ye?-/ÿ©óŸmõ
L v.|E²úacÐ(NiÈЉÖTrS_, RŸ
$‹ÐœZg%º(gK“û ¨w½N;¸ú1€žÜ´5prÂŽ×E–ÖÇøÇ$ðyG±Ó¤·}°®Ê/ÔFžÇD(Çû:ïªA,öxäZjþ<Ì«è£Õ[ØfÇ– Ó¾/žç¨"P¦YÚZÑÓaÄ»Óê| ´ÀM•Y¶ Ѻìµü¯RºOàiý´KÛõ–‘Z‚jÃMv¢ÝÓ©ÐÞ%h;®ü†stf¢ã
ïtë[©>¸±º¯óåöþÃ|>T YcÑ©û,•£¶p %Ò:qí ``)н;ºÉSw7ÒfùãµóÉYÚÉÄ$›Õt_V´´$‘‘óPR}
ªÖWeË{²PÉ ï¥BïÅúÛÅâôòüæÍl>{{ªm¡CʧÓ÷]ßÆ6$]YÓ]tÞø,ª•t)lüéЛŸæ§¦ƒ EÇ~„öbÕñµó¶E” §J-< ®b[OQT£3 Oti~8 kÌ÷:âŽèiØ_¢*69£¶™ëÌ
€„q§tAQ¾Æ›)#¶É
«¿]…1t‡°WÓwCy=È0s]L®É Ó
lù=;ù
zϾvvo¤ ›ªŸ˜1$‰Ñ¤EÒ¿a ¯æÌ댃àŸL#
'Ž_Ì´“Dñ'IØ#úyþ%òË‹ùùÙG•y…t@"TΡ´{šGæ%TR€Æ]mF™—6…γðˆÿ'<àeÃ6¹b vñËôt1 À*5oén¶œA Ýi6³‹pPž¯µŽa:3Á@AÎÐ6_«ž‘À 1}}°~a6f|¹ÍÒö€±)o†RýQ ip:V;JĶIS{ÉP& Q_JubIœqs¦Ó3LŠ šu3 fiÂùv ÓAž•éÄAéˆeIpt5üUšE×*ab°[W»=&Úi›ï2à-p]g,Pd'P^]% NCú-p—DÔe{ŲX¼cƒI_xOÀ©Çºw7§“Àè£Ëw7Ë—³Å÷-% N’èå¥D?íbš¼Q:W]ªf»ªVÝJpd
±˜ ³ôqŒºüðÉùeöqBbÕÅ8sb(\@Qzbì˜qÊtõþj4 :§‹Åïzr†j :B£Ó.®ÞœŒ‰Á˜D
:•tØ»‹ÅRI„GÅ'@2:0;'g=JhÎêá‘eqà«ÃàÓ닉è÷ôêa“Øí.¸G35Á{d^ä÷J\ÇJo—(ogï—ºg¡øU_b¥ø^P˜^Êî $ïI £P þþ#¥µÀvÌÚ£¤I{ òV©5Sº iJ¯ó©
¤få³C
aGZ|äŒj¶ÝØDJ¶ag[”Z ýy;!Å.¤tn³õS1R” É´æÔo`Ds1šÛ©wéjs)ÄA$€Nú}…žïÕ è.aˆZ¯4Ûizïà{ü+-õjAS$¡¯‘ñ™~§[Ð'ü »Nu‡ B¬Asð‹ 2S;´›_ßß5¿@«$&Ãf_ab5ÚÏŠnŠ@›æ%ýÝi; º6Ù:ß‘PÈïòViùN=6z׶ʔÃBÆÃýŽÆ]³_¡¹ .ÀŒl}ß vFç²:ÛUhdÛªiíŽ!Òý4Då$ÝÂs? ¨|4-»bˆŒô^ùZÏ4ý.1æ~¯À³ÇÑùÐ9^??‡Ø@„ýk!£”tý¡ BËL
3¶Ú¾%%%é—+ô>… d‡ƒ— ¬w› Q „¿ ‘úu‹îë4ÿ.Î.þÐØýnu'ÝêIn;¨žˆªç/ïúé|>û.HIhžÄcD}¡Í.ä•]Z¢Œ^L‡Ê§¬ùBj® ~> Ð ½Ûr´‹¦4óTÕ>)qRŠ4h¸~¢dacåžîÁºÇ YÏrÎßÞ]ü:{ÅA¯òÍͦI9¬ wbšÉ½¾Èbß|aT €»ãñÏy]•$qØçnÎIë\oÛ•Ì:Q þã |üÐ_úƒQ_väÒ—ö #;;¯5£>k€±ª• TFäÚdâÒ$£a,—¹0b®ÇÁ¨»O›Q8 þ:øè6ºáÒ#Äè]†û£&AÐÓ‘‰ÐZ¢%~hÕ–è·Å° #vãŽïkäå+$G²‡mŽy™(U‘g†ÇwûCK_b°ÛºÚiÿd„–.íýoˆ;’Öc¼*QŽàÚ¹ð„IÚîL4löU;ýÁÄšxí B_©u‹ÕuÓµóP
™OôÂÛ|cqX
… ´ wÿN÷y©·L´§‰‚^; y íbŸ•‹Åüi[
ûEæ@¡õ÷‹$ruþ›þ–ˆ e6äºç¹vl<]mî‡gö"ïL#Z¶}‹{ÂçÛ¸oRÏÓìCM$Þ÷'ŸBÓù`ÉJÿî®ë§T函Òû*U‘Œü:U þWL5f)5÷'Ý[ê]ÇŽ¢=Öà¡õŒ± ¿ÅX–˜¡#ÃZA„ xØ õ÷—TEí % Ãn¸ÇÈ -;×æцû>
stream
xœYÛnÛØ}÷Wœ·¡Z›Ãsxï›;qÌ%žÚJ‹". Š<²8¦HE¤b¸ß0 ݵϤ¬Ät†Dêp_ÖZûÂÏ,ð9 èŸù[nϾ¿IÙC°‡³Ïg\]dæO¹e_↌¾X®Ïôo8KKóÐÏr¶ÜžqúAÌ–OgŸ¼ò°oîeÑ?ß÷rèvÃÞ-XS¯èÂâBÄ ©÷KÑ Š†¼{ñŸågaÂ.ðYáÌ >Þü|ýëòþööÝýO ®aäçYĽ}xw}»¼U÷_À ˜Pª rA?ô~-Ëßà¾Íý,†áø6ðEblí{V°]W·ƒÜ³¡Ã‡ÿÊ}Çði[·Å +Öûº}`›®©èï°‘ì÷F²¶ØJÖÕçǶ[2(Ž¼§ö~Óõƒºç zékgÒÀOôã½åF’UaøQìl¥cð5üÔ¦jíÕ¹ý¦;4 ½“-â¢.»ý¶Xѳþ°Ûu{ò`õLÁïûðÙ{²¸ÖÇàO¿“e}¡ŒÑ5¶À.žëý.«s›<öT7
ëÚæ™e)w+»¶•åPwm‹Ã†i+‡
±7¡‰a>+ÚŠíö²—íÀêVß+ÎõÏ
$zøÏxxgÊk¸Rn(ê»Ãª©Kö¸ønÌrúIç&¦ò™¼}A?-Ï2\@ÌEÿ£C~žfÜ\èU"¾¿á7÷ã,µ—g¨»ú÷Û ~X¾¿þ ãø ?å©ÍX§:p„¦FÁ
9ªäzÁ ÷Qî‡f`+¹)<÷ó<Þ—ºÛ#¬*xÊ"Êý®Ø|¨pP U²l ÷3øéТn“ÏìÎ Ž}Îs&}ζîï6¶>n¾¬*àYI}˜”€ô¡Šs²!ñ³×âñÈÇ~2ã%÷” ¨s'yùQÏm™K2+Œ M³*ÊG¶>´
›ÀýÀ $€I—àêÓF¶#ucä%Ï u ê6E¯³AêGv„A¢\XIœSu-`¬ÒÝ( ?£ë€(÷ÓÄdÇ{¦ Ì ]:M©‘{ŠÝ@/Èhub9(âT i¥Øí¨¸qÒAÊ ÅBŸø‰ž%H\òÐëvÊõ\xšðÀÜåí»RÊÊg#æBF WÑyDp#PQ%mëõ}’Ôî/U;"¼‹t¦Ú"…HhhŒƒ8Mß1_Û$~sDD×9îÔ¡¬?‰›8õcž½›—`Ñ@Ù} #ä°ÐV¤V
4sBú£Ü ùsËÂõ˜ðÄwRE¦ë[öÝÖw¢.Æqêàb_WŠ8C`ó€y¤°îý~Ú&ŠdæLææc“‚Dp‹A{ µi/·Ý€RSx@Ý®;¶¦K}¦£J?áWX%÷î5ÔV†Å± F ·p@K‹Õ 4xP5àJä‚HÄi%~c¼
S•PèSXѾ\Ž>¾
çå\´ˆbÀ!º’Ž»…ÒŠ_>Þ.‚á°oáª+ôëŽNzÁs5rÜÜTv•ì‰±ƒ´hÄh‰x2'Ð1{u¶2?L‚yãÀëŠ q1§ó^9üMùŸ€ýGêüÓ»Û¥.çpP‘€;åEFžrûÈû·ï?\Ý_¾ys¿\ðLy×øòç+SŽ2€%Ÿàóб`ú×9þ"¤;
-¶"î
SÝN蜒Z$Ö¾˜&€NÙ¹Uvj:@KÂÙ¬'nJ|W*SaGÁ5O+ •Ô¸ u{¡ÝCo–çÙDÞ…Ö–eXõ'täØëfÖ½y2©TQi©8
!PFCçJbŽF,Ê)Gæ»Çòºíª›9„&3¹«T»®k\ëK]@Z FcK)'ª†“b¤ºïT7¶Û÷ÈΚ"øD¿AõˆÃØÒ¯èÛï `Sn,ŽFÊ
ÓBŸæ®Ðc4ì÷²¨ž]ÿöR DŽ‚ ‚UÅPXgM{J•í«4 É£‘N¨vº—Ýv×HðîdÜ5E9mÓusÉZ©»ÃP$º'Ê|Ç~ïi’ÕÅÛž¥Sg2‰µkæ‚ð¹yöó9ëç'£h&öànRñÁÇIÅ·¶ÃÊ }¯:h#3døê
¡9œ½¦$ ít˜õ¨«×…R5`ÿ·&hIЕ÷ùó×È Å¡«,Qþ‚ýôŠUšˆüû!È©‡}šåþŒ÷šÆùGXª›[U†]AòN1wÚÌŒ·üsI,WÙS}Ï æÚš1a.j¶zBˆe G˜bý5fbæGêYfF˜|Ä7™‰¨F)·áž3R' .f"–þ©˜º¹úñê‡å)Tq(Û7A…dÄ6"Ÿ!Šú/+£®Žzý~êzê2‰'eæ÷¿(ÔÏ UÉÖ šéSƒ ”™ï¼çY/’ÜFz=J½ƒf¡ “:|¥ÑÇ3x?™”ʦC·ùçÆúÍÕÛ«›ÓNÄkÎ\YFis‡¿ÐŽ–yx"Ü(a‘ã¯yØ'îs¶Z…Eä T-`´½˜zÿÞ#œÇʘӧQkÞÑ$ò¸ÈUMŠ0ESÏWA ºÜ±‹ü¢¢ ëcŽI°)´ß“†¬%ÚÛ½ÙÚ€óð0Êaj_j-£ýtÆDoæªÑ'É0ĪQì»DHÖBS3ÄÑúÁÊü$ !za7 «†S,ªÝƈhºñ©ä!´t”bm)e²Ÿ.²8¶0®‡C¡BaÄa×¼}U顧ä z_H)o‡D¶&méíæFP£šÏrðrûäí7$ª˜: ¤9ìôÜÑ—{5Xñ°PÓzšzEÝúvYKGÝúÚ>ƒºí¯î2Þ̆ÙÀ†òøRhå¿\²Ë™cIL{ãÁ˜Æuãν®®Ø_hW·+öÅVÒ¬¤V…~ÆΊð<øMÆIƒ?BªÝ§µ±slÑtè—§:%žÜ¯Š¡ÞÚå†`7ŒéÑÜMcj‰qYùU™jæƒ}d»²›ÂÜe·ŽñÉÔºa¦Í
±2
r‡vs’ÔëåÖaY2½»ºa0ÞÎA¤"᨜Ç~ýzóþŸ3H¤ªnd¯ÉîÕ æö` -¾¶Ksñ ´’ú*BD®Š}žûßM%gZÝ#L(jv¦Ë¦å«Ù"#€HWÖjÛmÚ( I©jë¡ê’H©ÈÊÄ|… Žb‡ºã·8,‹–õ‡U/? ÐgèíéF-t
)t«²/¦]tÒç:] ¦º„©ë áâñ:ølù˜¾™xpz,ÚnŒo Fhd m“Ý(›…“ë4 *ï?¼½~‰Ì«~ìúõW°f@Bv$´ÝNw°¶3©‡^6˜‘:Ù³¶6“Á”æ$$õx‹lÈó¢¡P¼}wy3Çêë‹Û0IÆÅm¿¡ý¾!´˜`T/&= LžirBŨ u¥y#ç'ªùgSÌ,ÌS4Ê¡¢ýhAG1iȹ«fd²ÑFZÔ–èyÍ ‘‚:_·ùýRw½E^HŸ •çnT00"kaŠ2îÉûº'¯®þ(š‹ ݦ›8ÜN©š£WA¤ßø˜¨ò«Ñp®E}[<•L•ÈÔ`l»ƒé(žD“‰?2[æ9¹Ýk$¥ k»ÿSÉ¨èž ³~åª}w$¹yÏAgÔm?˜â2ÌoùÎöv¶×06ƒ™l‹U<÷rÞ³©…ªx¥] 4÷æ%¢ñG7W
JšïõP^>*OBX>:’ÙŸÓ/U××ÛC38 \4Œás½£7{ŸúsöÜ ´ä䶞¹H´Gœ×›Pаç²JÙ$4]ùHA6]Õë7eZ*Ñh <Ò‰)g|v+ßgub¦~#lIû^¼s© qÃ8Bo *9uc¶ \m¤í:ž~í¢˜¨QÛj„ª6ô²QcnÊ®{¬¥Žàž‘&[<*ëxƒ¹Ü,7z’z0×;Ä'5¦Ú»dûP·Ò «R©'c~&JQ·¢!D ý´øîŒöeã¶*1‹JÈÙª‰µÒ
ÿKø Þê$Áf³mN˜«÷ä)$Ùny¦ d}¬C?Á7Õr'ˆ“(Ý-ô’ÿE˜ âÔ‘ÿUÝë ˜L ?@“„©.Ñ£¿©)˜¨¡
Ë5–¡3øS©ÇÞa„è †˜”ìÛj/Šé»«åÙ?ðïí œÀendstream
endobj
230 0 obj
3157
endobj
234 0 obj
<>
stream
xœåWmoÛ6þî_Áo‘„I½qè
d dK“ÌQ»É0¨“%W’d¿¡?zw¤(Én»õ{aÀNHÞñ^žçîø‰ø” ?ýo¶ž /crßÎ|r?û4cf“ô?Ùšü’ÂÒÕÌÊ0sKAIÒõŒqAý¤O³k/Û6åVíóm«»zÓÝxâfNÊâ7æG<ô©ïÇÞ[UmUI¾zzþWúë .8Ió™OÁQ¹÷ZuŠtªƒ/MÚÕhRß}ÔYGŠ–TuG@ éê~ë©(Kr§I®UÙÁ݃‘Û¶xóÓ<ý8~LýˆƒGp§žÍx]6KhœÈ$°›×Þ¡š !(gÂk û§/¼Ue¬E!†B‚Q)BÙk¬[Ôèãã”sÆìºÄŒKÖP<ÅcE¾“TFòH$°“#ÆÍê¶Õ9µ,F41˯Þ-Ï..ÓÛóÅ ·oNÏ·—‹åÛ+s² »¢AÉ¥Œ’4 EA"ŒEmK)ëêž(ük£µÖnŒTâ)Œ)‚¤7ö0›h”\ø¡ Z]uª¨
P†‘œó€JGž*·º•YÝèf]´mQWM®Ë›‚ÅûJç˜ÑJ›8óHP‰þÞ§ò¹P1ç!úl£›5Zu às©[RWæºF¯ëУ›Gf<¤\ö{ÖÍÐ*Èfà%“Òღc6‡d]{²Õœl OmoÖÙ„KëlÑŽ—Ì漢4–AÏ‚À†82 )Ç}æ»i˜‡Ä1Ó¨tÁ?ÀO@:
O"ÀFEÜënWÝæ§ãc{dð ‰%œíÉ»¬µ™“ät?xܤÐ)˜B?»½*ß7
5Ù= Ï7µ3ÊÆèÐoPŸ€Ý¾ï ?És@aQ‘˜i(qE KîÈãë "¿>].^¥s#çïb9Bê³ ò>ôüÆüüÔ°h‡àyÑ@¨›âÛ<#¨¯;4¬šÿ¢9xÃ]h.
Ù”æƒË_ÒÜP%p ùqÚ.“°ïà9C€¹4 Û{\ Ôph)IÈ¿BvAÃ!‘¾[(MHoá$À›„Ô6ˆêéé À‰ïZÙBþï¦>ÃîîÂóuê /%¨Áš —3ÉI?Ogç‹”@%8½8¿Ú
ÊÈó±\Øós–xNÄÌ$“ŠÐԆ冈2H;V=¹ÆBP”$£²ƒY[m?8YP°Â`”væSM¡î°Å‚èH¿HÁN— d@mxóéÝ×]¡:¬M ÖÞg4ñ]:œ¶~Î<‚ÉCk ëšKÛ‡z[æXF
KøUݬv/`Œ„ ~î‰Écò—ÔÍ ¤Ýn6uÓµFÈ nÉAš~¸\ ’ƒ?_Ÿ^]ž]¼: ŠåÆ<¼ú¬ú–æÅùûJ®´6*úlµ œWMŽv@™€²X¶t~°—k kÇz¿\¤ï–çäýœ °5bÞÉÙ»E_@¾L8Ð!LŒ˜øÅíÅoäÆûG75 Øk\u ݲƒ%ƒ %}ÖQ‡ L˜fZÒB}¶u6„n!Ât˜<âTÓj2™n«#¼½¿Ø®›|¯3s ·3ì„WÐñ`ÞP]¼˜cü¢/wq &Žƒ6ð¹þ\évˆúžæG-9T¹>ÕG`Ð<íPV7f>ê׎όñÂ(¡0ѹj³w6êÞ Ê¢k =käC®Û¬),xìDÎ$‡Õ,NEÿf9]‘çzKºæÙ{B*ÇvhùegÜ€2|ÊKó–wÌ„n‹?É:‡¦+„‹(ûu:‰Ñb t +5“P"\[¤³ßáó/" ^Kendstream
endobj
235 0 obj
1710
endobj
4 0 obj
<>
/Contents 5 0 R
>>
endobj
13 0 obj
<>
/Contents 14 0 R
>>
endobj
18 0 obj
<>
/Contents 19 0 R
>>
endobj
23 0 obj
<>
/Contents 24 0 R
>>
endobj
28 0 obj
<>
/Contents 29 0 R
>>
endobj
33 0 obj
<>
/Contents 34 0 R
>>
endobj
38 0 obj
<>
/Contents 39 0 R
>>
endobj
43 0 obj
<>
/Contents 44 0 R
>>
endobj
48 0 obj
<>
/Contents 49 0 R
>>
endobj
53 0 obj
<>
/Contents 54 0 R
>>
endobj
58 0 obj
<>
/Contents 59 0 R
>>
endobj
63 0 obj
<>
/Contents 64 0 R
>>
endobj
68 0 obj
<>
/Contents 69 0 R
>>
endobj
73 0 obj
<>
/Contents 74 0 R
>>
endobj
78 0 obj
<>
/Contents 79 0 R
>>
endobj
83 0 obj
<>
/Contents 84 0 R
>>
endobj
88 0 obj
<>
/Contents 89 0 R
>>
endobj
93 0 obj
<>
/Contents 94 0 R
>>
endobj
98 0 obj
<>
/Contents 99 0 R
>>
endobj
103 0 obj
<>
/Contents 104 0 R
>>
endobj
108 0 obj
<>
/Contents 109 0 R
>>
endobj
113 0 obj
<>
/Contents 114 0 R
>>
endobj
118 0 obj
<>
/Contents 119 0 R
>>
endobj
123 0 obj
<>
/Contents 124 0 R
>>
endobj
128 0 obj
<>
/Contents 129 0 R
>>
endobj
133 0 obj
<>
/Contents 134 0 R
>>
endobj
138 0 obj
<>
/Contents 139 0 R
>>
endobj
143 0 obj
<>
/Contents 144 0 R
>>
endobj
148 0 obj
<>
/Contents 149 0 R
>>
endobj
153 0 obj
<>
/Contents 154 0 R
>>
endobj
158 0 obj
<>
/Contents 159 0 R
>>
endobj
163 0 obj
<>
/Contents 164 0 R
>>
endobj
168 0 obj
<>
/Contents 169 0 R
>>
endobj
173 0 obj
<>
/Contents 174 0 R
>>
endobj
178 0 obj
<>
/Contents 179 0 R
>>
endobj
183 0 obj
<>
/Contents 184 0 R
>>
endobj
188 0 obj
<>
/Contents 189 0 R
>>
endobj
193 0 obj
<>
/Contents 194 0 R
>>
endobj
198 0 obj
<>
/Contents 199 0 R
>>
endobj
203 0 obj
<>
/Contents 204 0 R
>>
endobj
208 0 obj
<>
/Contents 209 0 R
>>
endobj
213 0 obj
<>
/Contents 214 0 R
>>
endobj
218 0 obj
<>
/Contents 219 0 R
>>
endobj
223 0 obj
<>
/Contents 224 0 R
>>
endobj
228 0 obj
<>
/Contents 229 0 R
>>
endobj
233 0 obj
<>
/Contents 234 0 R
>>
endobj
3 0 obj
<< /Type /Pages /Kids [
4 0 R
13 0 R
18 0 R
23 0 R
28 0 R
33 0 R
38 0 R
43 0 R
48 0 R
53 0 R
58 0 R
63 0 R
68 0 R
73 0 R
78 0 R
83 0 R
88 0 R
93 0 R
98 0 R
103 0 R
108 0 R
113 0 R
118 0 R
123 0 R
128 0 R
133 0 R
138 0 R
143 0 R
148 0 R
153 0 R
158 0 R
163 0 R
168 0 R
173 0 R
178 0 R
183 0 R
188 0 R
193 0 R
198 0 R
203 0 R
208 0 R
213 0 R
218 0 R
223 0 R
228 0 R
233 0 R
] /Count 46
>>
endobj
1 0 obj
<>
endobj
7 0 obj
<>endobj
11 0 obj
<>
endobj
12 0 obj
<>
endobj
16 0 obj
<>
endobj
17 0 obj
<>
endobj
21 0 obj
<>
endobj
22 0 obj
<>
endobj
26 0 obj
<>
endobj
27 0 obj
<>
endobj
31 0 obj
<>
endobj
32 0 obj
<>
endobj
36 0 obj
<>
endobj
37 0 obj
<>
endobj
41 0 obj
<>
endobj
42 0 obj
<>
endobj
46 0 obj
<>
endobj
47 0 obj
<>
endobj
51 0 obj
<>
endobj
52 0 obj
<>
endobj
56 0 obj
<>
endobj
57 0 obj
<>
endobj
61 0 obj
<>
endobj
62 0 obj
<>
endobj
66 0 obj
<>
endobj
67 0 obj
<>
endobj
71 0 obj
<>
endobj
72 0 obj
<>
endobj
76 0 obj
<>
endobj
77 0 obj
<>
endobj
81 0 obj
<>
endobj
82 0 obj
<>
endobj
86 0 obj
<>
endobj
87 0 obj
<>
endobj
91 0 obj
<>
endobj
92 0 obj
<>
endobj
96 0 obj
<>
endobj
97 0 obj
<>
endobj
101 0 obj
<>
endobj
102 0 obj
<>
endobj
106 0 obj
<>
endobj
107 0 obj
<>
endobj
111 0 obj
<>
endobj
112 0 obj
<>
endobj
116 0 obj
<>
endobj
117 0 obj
<>
endobj
121 0 obj
<>
endobj
122 0 obj
<>
endobj
126 0 obj
<>
endobj
127 0 obj
<>
endobj
131 0 obj
<>
endobj
132 0 obj
<>
endobj
136 0 obj
<>
endobj
137 0 obj
<>
endobj
141 0 obj
<>
endobj
142 0 obj
<>
endobj
146 0 obj
<>
endobj
147 0 obj
<>
endobj
151 0 obj
<>
endobj
152 0 obj
<>
endobj
156 0 obj
<>
endobj
157 0 obj
<>
endobj
161 0 obj
<>
endobj
162 0 obj
<>
endobj
166 0 obj
<>
endobj
167 0 obj
<>
endobj
171 0 obj
<>
endobj
172 0 obj
<>
endobj
176 0 obj
<>
endobj
177 0 obj
<>
endobj
181 0 obj
<>
endobj
182 0 obj
<>
endobj
186 0 obj
<>
endobj
187 0 obj
<>
endobj
191 0 obj
<>
endobj
192 0 obj
<>
endobj
196 0 obj
<>
endobj
197 0 obj
<>
endobj
201 0 obj
<>
endobj
202 0 obj
<>
endobj
206 0 obj
<>
endobj
207 0 obj
<>
endobj
211 0 obj
<>
endobj
212 0 obj
<>
endobj
216 0 obj
<>
endobj
217 0 obj
<>
endobj
221 0 obj
<>
endobj
222 0 obj
<>
endobj
226 0 obj
<>
endobj
227 0 obj
<>
endobj
231 0 obj
<>
endobj
232 0 obj
<>
endobj
236 0 obj
<>
endobj
237 0 obj
<>
endobj
10 0 obj
<>
endobj
238 0 obj
<>
endobj
9 0 obj
<>
endobj
239 0 obj
<>
endobj
8 0 obj
<>
endobj
240 0 obj
<>
endobj
241 0 obj
<>stream
2014-01-29T08:09:44+01:00
2014-01-29T08:09:44+01:00
groff version 1.22.2
Untitled
endstream
endobj
2 0 obj
<>endobj
xref
0 242
0000000000 65535 f
0000138056 00000 n
0000143682 00000 n
0000137654 00000 n
0000130094 00000 n
0000000015 00000 n
0000003092 00000 n
0000138122 00000 n
0000142071 00000 n
0000141915 00000 n
0000141760 00000 n
0000138163 00000 n
0000138193 00000 n
0000130254 00000 n
0000003112 00000 n
0000005942 00000 n
0000138243 00000 n
0000138273 00000 n
0000130416 00000 n
0000005963 00000 n
0000009176 00000 n
0000138323 00000 n
0000138353 00000 n
0000130578 00000 n
0000009197 00000 n
0000012212 00000 n
0000138403 00000 n
0000138433 00000 n
0000130740 00000 n
0000012233 00000 n
0000015293 00000 n
0000138483 00000 n
0000138513 00000 n
0000130902 00000 n
0000015314 00000 n
0000017296 00000 n
0000138563 00000 n
0000138593 00000 n
0000131064 00000 n
0000017317 00000 n
0000020584 00000 n
0000138643 00000 n
0000138673 00000 n
0000131226 00000 n
0000020605 00000 n
0000023424 00000 n
0000138723 00000 n
0000138753 00000 n
0000131388 00000 n
0000023445 00000 n
0000026698 00000 n
0000138803 00000 n
0000138833 00000 n
0000131550 00000 n
0000026719 00000 n
0000029738 00000 n
0000138883 00000 n
0000138913 00000 n
0000131712 00000 n
0000029759 00000 n
0000032208 00000 n
0000138963 00000 n
0000138993 00000 n
0000131874 00000 n
0000032229 00000 n
0000034240 00000 n
0000139043 00000 n
0000139073 00000 n
0000132036 00000 n
0000034261 00000 n
0000036623 00000 n
0000139112 00000 n
0000139142 00000 n
0000132198 00000 n
0000036644 00000 n
0000038931 00000 n
0000139181 00000 n
0000139211 00000 n
0000132360 00000 n
0000038952 00000 n
0000042222 00000 n
0000139261 00000 n
0000139291 00000 n
0000132522 00000 n
0000042243 00000 n
0000045664 00000 n
0000139341 00000 n
0000139371 00000 n
0000132684 00000 n
0000045685 00000 n
0000048978 00000 n
0000139421 00000 n
0000139451 00000 n
0000132846 00000 n
0000048999 00000 n
0000051783 00000 n
0000139501 00000 n
0000139531 00000 n
0000133008 00000 n
0000051804 00000 n
0000054152 00000 n
0000139581 00000 n
0000139612 00000 n
0000133172 00000 n
0000054174 00000 n
0000057301 00000 n
0000139663 00000 n
0000139694 00000 n
0000133338 00000 n
0000057323 00000 n
0000060117 00000 n
0000139736 00000 n
0000139767 00000 n
0000133504 00000 n
0000060139 00000 n
0000063186 00000 n
0000139809 00000 n
0000139840 00000 n
0000133670 00000 n
0000063208 00000 n
0000066418 00000 n
0000139891 00000 n
0000139922 00000 n
0000133836 00000 n
0000066440 00000 n
0000069299 00000 n
0000139973 00000 n
0000140004 00000 n
0000134002 00000 n
0000069321 00000 n
0000072261 00000 n
0000140046 00000 n
0000140077 00000 n
0000134168 00000 n
0000072283 00000 n
0000075206 00000 n
0000140128 00000 n
0000140159 00000 n
0000134334 00000 n
0000075228 00000 n
0000077876 00000 n
0000140201 00000 n
0000140232 00000 n
0000134500 00000 n
0000077898 00000 n
0000080952 00000 n
0000140283 00000 n
0000140314 00000 n
0000134666 00000 n
0000080974 00000 n
0000083895 00000 n
0000140365 00000 n
0000140396 00000 n
0000134832 00000 n
0000083917 00000 n
0000087075 00000 n
0000140438 00000 n
0000140469 00000 n
0000134998 00000 n
0000087097 00000 n
0000089959 00000 n
0000140511 00000 n
0000140542 00000 n
0000135164 00000 n
0000089981 00000 n
0000093370 00000 n
0000140593 00000 n
0000140624 00000 n
0000135330 00000 n
0000093392 00000 n
0000096544 00000 n
0000140666 00000 n
0000140697 00000 n
0000135496 00000 n
0000096566 00000 n
0000098555 00000 n
0000140748 00000 n
0000140779 00000 n
0000135662 00000 n
0000098577 00000 n
0000100838 00000 n
0000140830 00000 n
0000140861 00000 n
0000135828 00000 n
0000100860 00000 n
0000103627 00000 n
0000140903 00000 n
0000140934 00000 n
0000135994 00000 n
0000103649 00000 n
0000106300 00000 n
0000140985 00000 n
0000141016 00000 n
0000136160 00000 n
0000106322 00000 n
0000108942 00000 n
0000141058 00000 n
0000141089 00000 n
0000136326 00000 n
0000108964 00000 n
0000111023 00000 n
0000141140 00000 n
0000141171 00000 n
0000136492 00000 n
0000111045 00000 n
0000113678 00000 n
0000141213 00000 n
0000141244 00000 n
0000136658 00000 n
0000113700 00000 n
0000116072 00000 n
0000141295 00000 n
0000141326 00000 n
0000136824 00000 n
0000116094 00000 n
0000118743 00000 n
0000141368 00000 n
0000141399 00000 n
0000136990 00000 n
0000118765 00000 n
0000121594 00000 n
0000141441 00000 n
0000141472 00000 n
0000137156 00000 n
0000121616 00000 n
0000125013 00000 n
0000141514 00000 n
0000141545 00000 n
0000137322 00000 n
0000125035 00000 n
0000128266 00000 n
0000141596 00000 n
0000141627 00000 n
0000137488 00000 n
0000128288 00000 n
0000130072 00000 n
0000141678 00000 n
0000141709 00000 n
0000141845 00000 n
0000141997 00000 n
0000142154 00000 n
0000142258 00000 n
trailer
<< /Size 242 /Root 1 0 R /Info 2 0 R
/ID [<0100AB9B3BE4118E409A02C3A5B87024><0100AB9B3BE4118E409A02C3A5B87024>]
>>
startxref
143836
%%EOF
curl-7.35.0/docs/libcurl/curl_formget.html 0000644 0001750 0001750 00000006325 12272124467 015453 0000000 0000000
curl_formget man page
NAME
curl_formget - serialize a previously built multipart/formdata HTTP POST chain
SYNOPSIS
#include <curl/curl.h>
void curl_formget(struct curl_httppost * form, void *userp,
curl_formget_callback append );
DESCRIPTION
curl_formget() is used to serialize data previously built/appended with curl_formadd(3). Accepts a void pointer as second argument named userp which will be passed as the first argument to the curl_formget_callback function.
typedef size_t (*curl_formget_callback)(void * userp, const char * buf, size_t len );
The curl_formget_callback will be executed for each part of the HTTP POST chain. The character buffer passed to the callback must not be freed. The callback should return the buffer length passed to it on success.
If the CURLFORM_STREAM option is used in the formpost, it will prevent curl_formget(3) from working until you've performed the actual HTTP request as only then will libcurl get the actual read callback to use!
RETURN VALUE
0 means everything was ok, non-zero means an error occurred
EXAMPLE
size_t print_httppost_callback(void *arg, const char *buf, size_t len)
{
fwrite(buf, len, 1, stdout);
(*(size_t *) arg) += len;
return len;
}
size_t print_httppost(struct curl_httppost *post)
{
size_t total_size = 0;
if(curl_formget(post, &total_size, print_httppost_callback)) {
return (size_t) -1;
}
return total_size;
}
AVAILABILITY
This function was added in libcurl 7.15.5
SEE ALSO
curl_formadd (3)
This HTML page was made with roffit.
curl-7.35.0/docs/libcurl/curl_global_init.pdf 0000644 0001750 0001750 00000011745 12272124472 016076 0000000 0000000 %PDF-1.4
%Çì¢
5 0 obj
<>
stream
xœXkoÛÈý®_1@?„¬ ‡‘D‹NâMÕ*öÖR,œÂS#™ŠTøˆVû òŸ{î Ÿ²ÝM ‰ÍÇ}œ{î¹wø•Ù\0›~šÿãýäõmÀvåÄf»É׉Ð7Yó_¼goÖx ¤ ëíļ#Xà° ry±õ~"œ9w¶>N.Òû]š?Èô>É’ê³å~ž²4y Ó™ãÛܶëƒÌj™²gŸžþ{ý÷ÉÌ掀õÎ#8ç‘OþÝ9[/'ÖõåôâÅ]ás?rÓz3±>\M׿¢ulîÙ› ‡nÛá“ ÙŒ½×µA2ºšÈ4)e•ä™±8a†fbÎCírõËõÍϫŪ¬ ³qjý)Éâ´Þ(ö2þšþá¥Ç Oçòöãí2ÎñÀS0Ò<Û!Ñ×·Ânñ÷<.<“îõ]N…míJXï]DÜžÛNÊçéŸŸæ ¢ˆ;ƒ4Þ]ÞÞ.~^/n®Çö™ óÐyý˜”l[g1ÄJU•¬>°êQ±C‘ï
¹g*›z¨´ˆ|ë[RäÙ^e U‡r¦Ô¦äÓ™ò„Â!›Ù–oJ"K&3¦tZ®çð¹I…"Ð4³~«TV’oŽF) 9[õ)pÓƒbb¶T¥kJày6}×{-—à7)ÈkR<œØÍm’ítE¿uHÉ´ÖÑî1OÇæ ð<¸ 1…ä LB‹l×%EÓUVD8ç¾ 4Þ¨XÖ¥2c½[$@üÏÃN¹ŸYÜ°‰VÀç®ÓXE ýÐìSZx[ÆhÖ™0ÍLNH(R¢s™€Ê²€º59ÔQé‚j çuº!>O ¶Äu]‡Æiå¨ÁÆ“áÙ³ŸÔ^<ô,BËžkTÁ(ÀtÛ ÖJ™Ùl¤·QõÁjHð„!;E°Úw¼†Üí8{g™Ý€ØÛ) 9Á`
êk
Ù¥ßK=57ª’Iª~Ì[JiBa ;ícM±¼6ûŽ¾ßê_IÉ Úœ?Ý=[p ""ÁŸ–—S *±´Þ¯ÎÅ ,\½ð:M2Fo›W:,ºÞ²ÍÂý»:[ °É9}¿´Üa) ÍlÇyY&)zYwÞ^HB¾d9)ì13³k0kcu¨žlÏ (ך>ËÆvt6 2ðö ÷W‹ëõíYruóvÒy2ómÆýòýd«ÕAFÏ èçþ»ñO‹k×yÑüÝÐ>ñþ“Y=a%°)óøË”.ø®O«Ã {ÎÍ„r}cŽ
XÎ×[\¿ÿ¨@`Œ]rÔÒÇq ÚC*Qèÿ'˜wW?µ •‘ÜêÖådžž‘ÓLš¨§çrmæ“ç;ã‰8#eðIMšâ]–ãÔ鶱Èo† o@d4; 82{‘%±ër¶ qLÍ)•= "€Þ >uêAEâì6Ù=Ò oˆ8@ÛÚ
Ñ1ãÅp+†æ¶ÇGŠÉœ”]h‘LÍߊÊQšmÿœ‡sŒÏûŸ¥A`2¶ÜÚËòËy ’¥ð‹Ù´)XûB›:ƒùî›ãÁ'Z5´:bƒg†Púhn`—1‰
Y/Béº-à '¡»87îÓÞhšm=,ôƒ?3œ$ˆ¶Ðq}é¨ÛÈöK&ú¾Y¬Œý&>-ño#+0ý†fÖmpA‘t.îêÕ†qMÀ%ãX²*IQ7:¦&{•×S©<”ã¶í¾¸´‘1¾½Z¼½fÿš
°Î þxu†èàÃÇb;ž2˜d8ËdÔÙìwUät€Û+ÓÆGuG̼¦2í¿±Ìh¬K#AfN뼺eã™Á5þ8suÅ.—«›?Îœ/=÷ØåÆ#›>r…]ë‰}16oóþkËÐbœbo«cƒØÍæýšðƒ•,O:À±¹=4sfÅÃê¬üñ:ÒÛ˜¹¾Ã]}$j†`{H
¸p¦€W8à£%û O g+O³À›·ßᙹZOþ‰Ÿÿ »Jjendstream
endobj
6 0 obj
2190
endobj
4 0 obj
<>
/Contents 5 0 R
>>
endobj
3 0 obj
<< /Type /Pages /Kids [
4 0 R
] /Count 1
>>
endobj
1 0 obj
<>
endobj
7 0 obj
<>endobj
11 0 obj
<>
endobj
12 0 obj
<>
endobj
10 0 obj
<>
endobj
13 0 obj
<>
endobj
9 0 obj
<>
endobj
8 0 obj
<>
endobj
14 0 obj
<>
endobj
15 0 obj
<>stream
2014-01-29T08:09:46+01:00
2014-01-29T08:09:46+01:00
groff version 1.22.2
Untitled
endstream
endobj
2 0 obj
<>endobj
xref
0 16
0000000000 65535 f
0000002514 00000 n
0000004466 00000 n
0000002455 00000 n
0000002295 00000 n
0000000015 00000 n
0000002275 00000 n
0000002579 00000 n
0000002905 00000 n
0000002840 00000 n
0000002700 00000 n
0000002620 00000 n
0000002650 00000 n
0000002784 00000 n
0000002987 00000 n
0000003043 00000 n
trailer
<< /Size 16 /Root 1 0 R /Info 2 0 R
/ID [<70BE4C84F4A06B6D8EE5DD0246AE9890><70BE4C84F4A06B6D8EE5DD0246AE9890>]
>>
startxref
4620
%%EOF
curl-7.35.0/docs/libcurl/curl_share_cleanup.pdf 0000644 0001750 0001750 00000007056 12272124473 016425 0000000 0000000 %PDF-1.4
%Çì¢
5 0 obj
<>
stream
xœ…UÛnÚ@}÷WŒÔ‡ÚU¼Ù]ßÕªM‘š–@
N¥
ªÈ˜ ›ØF(ý†~tgwͽQeÉ6žÙ3gÎœ]žT^í3]×à µAaa<L¡}¤+øcB(?ÄsC¯ap"‡„Ä+ƒ1N<ñÖ›é¦Ê ëeR‰Ç4I±YOLgbAžMeȲ¹G ¥y‡±$‡Wò_ñWæ„3¬" È“ âžaö;Ö[äŒQæ/rW<3Ì»®? 1攸4 ›q¦’å?H‚
7ò
ð5šA9}i£áŽêÛHÀf> U½ÑÏþà~t;:¤µ ۊ曬HóÍLÀYöZÞÈò£Lç®l$~76o †½Ñ—´Ä¬=7‹…„2™GÊè>
/Contents 5 0 R
>>
endobj
3 0 obj
<< /Type /Pages /Kids [
4 0 R
] /Count 1
>>
endobj
1 0 obj
<>
endobj
7 0 obj
<>endobj
11 0 obj
<>
endobj
12 0 obj
<>
endobj
10 0 obj
<>
endobj
9 0 obj
<>
endobj
8 0 obj
<>
endobj
13 0 obj
<>
endobj
14 0 obj
<>stream
2014-01-29T08:09:47+01:00
2014-01-29T08:09:47+01:00
groff version 1.22.2
Untitled
endstream
endobj
2 0 obj
<>endobj
xref
0 15
0000000000 65535 f
0000001143 00000 n
0000003023 00000 n
0000001084 00000 n
0000000924 00000 n
0000000015 00000 n
0000000905 00000 n
0000001208 00000 n
0000001462 00000 n
0000001397 00000 n
0000001329 00000 n
0000001249 00000 n
0000001279 00000 n
0000001544 00000 n
0000001600 00000 n
trailer
<< /Size 15 /Root 1 0 R /Info 2 0 R
/ID []
>>
startxref
3177
%%EOF
curl-7.35.0/docs/libcurl/curl_free.html 0000644 0001750 0001750 00000003052 12272124467 014723 0000000 0000000
curl_free man page
NAME
curl_free - reclaim memory that has been obtained through a libcurl call
SYNOPSIS
#include <curl/curl.h>
void curl_free( char * ptr );
DESCRIPTION
curl_free reclaims memory that has been obtained through a libcurl call. Use curl_free() instead of free() to avoid anomalies that can result from differences in memory management between your application and libcurl.
SEE ALSO
curl_unescape(3)
This HTML page was made with roffit.
curl-7.35.0/docs/libcurl/curl_mprintf.html 0000644 0001750 0001750 00000011710 12272124467 015461 0000000 0000000
curl_printf man page
NAME
curl_maprintf, curl_mfprintf, curl_mprintf, curl_msnprintf, curl_msprintf curl_mvaprintf, curl_mvfprintf, curl_mvprintf, curl_mvsnprintf, curl_mvsprintf - formatted output conversion
SYNOPSIS
#include <curl/mprintf.h>
int curl_mprintf(const char * format , ...);
int curl_mfprintf(FILE * fd , const char * format , ...);
int curl_msprintf(char * buffer , const char * format , ...);
int curl_msnprintf(char * buffer , size_t maxlength , const char * format , ...);
int curl_mvprintf(const char * format , va_list args );
int curl_mvfprintf(FILE * fd , const char * format , va_list args );
int curl_mvsprintf(char * buffer , const char * format , va_list args );
int curl_mvsnprintf(char * buffer , size_t maxlength , const char * format , va_list args );
char *curl_maprintf(const char * format , ...);
char *curl_mvaprintf(const char * format , va_list args );
DESCRIPTION
These are all functions that produce output according to a format string and given arguments. These are mostly clones of the well-known C-style functions and there will be no detailed explanation of all available formatting rules and usage here.
See this table for notable exceptions.
curl_mprintf() Normal printf() clone.
curl_mfprintf() Normal fprintf() clone.
curl_msprintf() Normal sprintf() clone.
curl_msnprintf() snprintf() clone. Many systems don't have this. It is just like sprintf but with an extra argument after the buffer that specifies the length of the target buffer.
curl_mvprintf() Normal vprintf() clone.
curl_mvfprintf() Normal vfprintf() clone.
curl_mvsprintf() Normal vsprintf() clone.
curl_mvsnprintf() vsnprintf() clone. Many systems don't have this. It is just like vsprintf but with an extra argument after the buffer that specifies the length of the target buffer.
curl_maprintf() Like printf() but returns the output string as a malloc()ed string. The returned string must be free()ed by the receiver.
curl_mvaprintf() Like curl_maprintf() but takes a va_list pointer argument instead of a variable amount of arguments.
To easily use all these cloned functions instead of the normal ones, #define _MPRINTF_REPLACE before you include the <curl/mprintf.h> file. Then all the normal names like printf, fprintf, sprintf etc will use the curl-functions instead.
AVAILABILITY
These function will be removed from the public libcurl API in a near future. They will instead be made "available" by source code access only, and then as curlx_-prefixed functions. See lib/README.curlx for further details.
RETURN VALUE
The curl_maprintf and curl_mvaprintf functions return a pointer to a newly allocated string, or NULL if it failed.
All other functions return the number of characters they actually outputted.
SEE ALSO
printf (3) sprintf (3) fprintf (3) vprintf (3)
This HTML page was made with roffit.
curl-7.35.0/docs/libcurl/curl_easy_setopt.3 0000644 0001750 0001750 00000423501 12271241025 015531 0000000 0000000 .\" **************************************************************************
.\" * _ _ ____ _
.\" * Project ___| | | | _ \| |
.\" * / __| | | | |_) | |
.\" * | (__| |_| | _ <| |___
.\" * \___|\___/|_| \_\_____|
.\" *
.\" * Copyright (C) 1998 - 2014, Daniel Stenberg, , et al.
.\" *
.\" * This software is licensed as described in the file COPYING, which
.\" * you should have received as part of this distribution. The terms
.\" * are also available at http://curl.haxx.se/docs/copyright.html.
.\" *
.\" * You may opt to use, copy, modify, merge, publish, distribute and/or sell
.\" * copies of the Software, and permit persons to whom the Software is
.\" * furnished to do so, under the terms of the COPYING file.
.\" *
.\" * This software is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY
.\" * KIND, either express or implied.
.\" *
.\" **************************************************************************
.\"
.TH curl_easy_setopt 3 "1 Jan 2010" "libcurl 7.20.0" "libcurl Manual"
.SH NAME
curl_easy_setopt \- set options for a curl easy handle
.SH SYNOPSIS
#include
CURLcode curl_easy_setopt(CURL *handle, CURLoption option, parameter);
.SH DESCRIPTION
curl_easy_setopt() is used to tell libcurl how to behave. By using the
appropriate options to \fIcurl_easy_setopt\fP, you can change libcurl's
behavior. All options are set with the \fIoption\fP followed by a
\fIparameter\fP. That parameter can be a \fBlong\fP, a \fBfunction pointer\fP,
an \fBobject pointer\fP or a \fBcurl_off_t\fP, depending on what the specific
option expects. Read this manual carefully as bad input values may cause
libcurl to behave badly! You can only set one option in each function call. A
typical application uses many curl_easy_setopt() calls in the setup phase.
Options set with this function call are valid for all forthcoming transfers
performed using this \fIhandle\fP. The options are not in any way reset
between transfers, so if you want subsequent transfers with different options,
you must change them between the transfers. You can optionally reset all
options back to internal default with \fIcurl_easy_reset(3)\fP.
Strings passed to libcurl as 'char *' arguments, are copied by the library;
thus the string storage associated to the pointer argument may be overwritten
after curl_easy_setopt() returns. Exceptions to this rule are described in
the option details below.
Before version 7.17.0, strings were not copied. Instead the user was forced
keep them available until libcurl no longer needed them.
The \fIhandle\fP is the return code from a \fIcurl_easy_init(3)\fP or
\fIcurl_easy_duphandle(3)\fP call.
.SH BEHAVIOR OPTIONS
.IP CURLOPT_VERBOSE
Set the parameter to 1 to get the library to display a lot of verbose
information about its operations. Very useful for libcurl and/or protocol
debugging and understanding. The verbose information will be sent to stderr,
or the stream set with \fICURLOPT_STDERR\fP. The default value for this
parameter is 0.
You hardly ever want this set in production use, you will almost always want
this when you debug/report problems. Another neat option for debugging is the
\fICURLOPT_DEBUGFUNCTION\fP.
.IP CURLOPT_HEADER
A parameter set to 1 tells the library to include the header in the body
output. This is only relevant for protocols that actually have headers
preceding the data (like HTTP). The default value for this parameter is 0.
.IP CURLOPT_NOPROGRESS
Pass a long. If set to 1, it tells the library to shut off the progress meter
completely. It will also prevent the \fICURLOPT_PROGRESSFUNCTION\fP from
getting called. The default value for this parameter is 1.
Future versions of libcurl are likely to not have any built-in progress meter
at all.
.IP CURLOPT_NOSIGNAL
Pass a long. If it is 1, libcurl will not use any functions that
install signal handlers or any functions that cause signals to be sent to the
process. This option is mainly here to allow multi-threaded unix applications
to still set/use all timeout options etc, without risking getting signals.
The default value for this parameter is 0.
(Added in 7.10)
If this option is set and libcurl has been built with the standard name
resolver, timeouts will not occur while the name resolve takes place.
Consider building libcurl with c-ares support to enable asynchronous DNS
lookups, which enables nice timeouts for name resolves without signals.
Setting \fICURLOPT_NOSIGNAL\fP to 1 makes libcurl NOT ask the system to ignore
SIGPIPE signals, which otherwise are sent by the system when trying to send
data to a socket which is closed in the other end. libcurl makes an effort to
never cause such SIGPIPEs to trigger, but some operating systems have no way
to avoid them and even on those that have there are some corner cases when
they may still happen, contrary to our desire. In addition, using
\fICURLAUTH_NTLM_WB\fP authentication could cause a SIGCHLD signal to be
raised.
.IP CURLOPT_WILDCARDMATCH
Set this option to 1 if you want to transfer multiple files according to a
file name pattern. The pattern can be specified as part of the
\fICURLOPT_URL\fP option, using an fnmatch-like pattern (Shell Pattern
Matching) in the last part of URL (file name).
By default, libcurl uses its internal wildcard matching implementation. You
can provide your own matching function by the \fICURLOPT_FNMATCH_FUNCTION\fP
option.
This feature is only supported by the FTP download for now.
A brief introduction of its syntax follows:
.RS
.IP "* - ASTERISK"
\&ftp://example.com/some/path/\fB*.txt\fP (for all txt's from the root
directory)
.RE
.RS
.IP "? - QUESTION MARK"
Question mark matches any (exactly one) character.
\&ftp://example.com/some/path/\fBphoto?.jpeg\fP
.RE
.RS
.IP "[ - BRACKET EXPRESSION"
The left bracket opens a bracket expression. The question mark and asterisk have
no special meaning in a bracket expression. Each bracket expression ends by the
right bracket and matches exactly one character. Some examples follow:
\fB[a-zA-Z0\-9]\fP or \fB[f\-gF\-G]\fP \- character interval
\fB[abc]\fP - character enumeration
\fB[^abc]\fP or \fB[!abc]\fP - negation
\fB[[:\fP\fIname\fP\fB:]]\fP class expression. Supported classes are
\fBalnum\fP,\fBlower\fP, \fBspace\fP, \fBalpha\fP, \fBdigit\fP, \fBprint\fP,
\fBupper\fP, \fBblank\fP, \fBgraph\fP, \fBxdigit\fP.
\fB[][-!^]\fP - special case \- matches only '\-', ']', '[', '!' or '^'. These
characters have no special purpose.
\fB[\\[\\]\\\\]\fP - escape syntax. Matches '[', ']' or '\\'.
Using the rules above, a file name pattern can be constructed:
\&ftp://example.com/some/path/\fB[a-z[:upper:]\\\\].jpeg\fP
.RE
.PP
(This was added in 7.21.0)
.SH CALLBACK OPTIONS
.IP CURLOPT_WRITEFUNCTION
Pass a pointer to a function that matches the following prototype:
\fBsize_t function( char *ptr, size_t size, size_t nmemb, void *userdata);\fP
This function gets called by libcurl as soon as there is data received that
needs to be saved. The size of the data pointed to by \fIptr\fP is \fIsize\fP
multiplied with \fInmemb\fP, it will not be zero terminated. Return the number
of bytes actually taken care of. If that amount differs from the amount passed
to your function, it'll signal an error to the library. This will abort the
transfer and return \fICURLE_WRITE_ERROR\fP.
From 7.18.0, the function can return CURL_WRITEFUNC_PAUSE which then will
cause writing to this connection to become paused. See
\fIcurl_easy_pause(3)\fP for further details.
This function may be called with zero bytes data if the transferred file is
empty.
Set this option to NULL to get the internal default function. The internal
default function will write the data to the FILE * given with
\fICURLOPT_WRITEDATA\fP.
Set the \fIuserdata\fP argument with the \fICURLOPT_WRITEDATA\fP option.
The callback function will be passed as much data as possible in all invokes,
but you cannot possibly make any assumptions. It may be one byte, it may be
thousands. The maximum amount of body data that can be passed to the write
callback is defined in the curl.h header file: CURL_MAX_WRITE_SIZE (the usual
default is 16K). If you however have \fICURLOPT_HEADER\fP set, which sends
header data to the write callback, you can get up to
\fICURL_MAX_HTTP_HEADER\fP bytes of header data passed into it. This usually
means 100K.
.IP CURLOPT_WRITEDATA
Data pointer to pass to the file write function. If you use the
\fICURLOPT_WRITEFUNCTION\fP option, this is the pointer you'll get as
input. If you don't use a callback, you must pass a 'FILE *' (cast
to 'void *') as libcurl will pass this to fwrite() when writing data.
By default, the value of this parameter is unspecified.
The internal \fICURLOPT_WRITEFUNCTION\fP will write the data to the FILE *
given with this option, or to stdout if this option hasn't been set.
If you're using libcurl as a win32 DLL, you \fBMUST\fP use the
\fICURLOPT_WRITEFUNCTION\fP if you set this option or you will experience
crashes.
This option is also known with the older name \fICURLOPT_FILE\fP, the name
\fICURLOPT_WRITEDATA\fP was introduced in 7.9.7.
.IP CURLOPT_READFUNCTION
Pass a pointer to a function that matches the following prototype:
\fBsize_t function( void *ptr, size_t size, size_t nmemb, void *userdata);\fP
This function gets called by libcurl as soon as it needs to read data in order
to send it to the peer. The data area pointed at by the pointer \fIptr\fP may
be filled with at most \fIsize\fP multiplied with \fInmemb\fP number of
bytes. Your function must return the actual number of bytes that you stored in
that memory area. Returning 0 will signal end-of-file to the library and cause
it to stop the current transfer.
If you stop the current transfer by returning 0 "pre-maturely" (i.e before the
server expected it, like when you've said you will upload N bytes and you
upload less than N bytes), you may experience that the server "hangs" waiting
for the rest of the data that won't come.
The read callback may return \fICURL_READFUNC_ABORT\fP to stop the current
operation immediately, resulting in a \fICURLE_ABORTED_BY_CALLBACK\fP error
code from the transfer (Added in 7.12.1)
From 7.18.0, the function can return CURL_READFUNC_PAUSE which then will cause
reading from this connection to become paused. See \fIcurl_easy_pause(3)\fP
for further details.
\fBBugs\fP: when doing TFTP uploads, you must return the exact amount of data
that the callback wants, or it will be considered the final packet by the
server end and the transfer will end there.
If you set this callback pointer to NULL, or don't set it at all, the default
internal read function will be used. It is doing an fread() on the FILE *
userdata set with \fICURLOPT_READDATA\fP.
.IP CURLOPT_READDATA
Data pointer to pass to the file read function. If you use the
\fICURLOPT_READFUNCTION\fP option, this is the pointer you'll get as input. If
you don't specify a read callback but instead rely on the default internal
read function, this data must be a valid readable FILE * (cast to 'void *').
If you're using libcurl as a win32 DLL, you MUST use a
\fICURLOPT_READFUNCTION\fP if you set this option.
This option was also known by the older name \fICURLOPT_INFILE\fP, the name
\fICURLOPT_READDATA\fP was introduced in 7.9.7.
.IP CURLOPT_IOCTLFUNCTION
Pass a pointer to a function that matches the following prototype:
\fBcurlioerr function(CURL *handle, int cmd, void *clientp);\fP. This function
gets called by libcurl when something special I/O-related needs to be done
that the library can't do by itself. For now, rewinding the read data stream
is the only action it can request. The rewinding of the read data stream may
be necessary when doing a HTTP PUT or POST with a multi-pass authentication
method. By default, this parameter is set to NULL. (Option added in 7.12.3).
Use \fICURLOPT_SEEKFUNCTION\fP instead to provide seeking! If
\fICURLOPT_SEEKFUNCTION\fP is set, this parameter will be ignored when seeking.
.IP CURLOPT_IOCTLDATA
Pass a pointer that will be untouched by libcurl and passed as the 3rd
argument in the ioctl callback set with \fICURLOPT_IOCTLFUNCTION\fP.
By default, the value of this parameter is unspecified. (Option added in
7.12.3)
.IP CURLOPT_SEEKFUNCTION
Pass a pointer to a function that matches the following prototype: \fBint
function(void *instream, curl_off_t offset, int origin);\fP This function gets
called by libcurl to seek to a certain position in the input stream and can be
used to fast forward a file in a resumed upload (instead of reading all
uploaded bytes with the normal read function/callback). It is also called to
rewind a stream when doing a HTTP PUT or POST with a multi-pass authentication
method. The function shall work like "fseek" or "lseek" and accepted SEEK_SET,
SEEK_CUR and SEEK_END as argument for origin, although libcurl currently only
passes SEEK_SET. The callback must return 0 (CURL_SEEKFUNC_OK) on success, 1
(CURL_SEEKFUNC_FAIL) to cause the upload operation to fail or 2
(CURL_SEEKFUNC_CANTSEEK) to indicate that while the seek failed, libcurl is
free to work around the problem if possible. The latter can sometimes be done
by instead reading from the input or similar.
By default, this parameter is unset.
If you forward the input arguments directly to "fseek" or "lseek", note that
the data type for \fIoffset\fP is not the same as defined for curl_off_t on
many systems! (Option added in 7.18.0)
.IP CURLOPT_SEEKDATA
Data pointer to pass to the file seek function. If you use the
\fICURLOPT_SEEKFUNCTION\fP option, this is the pointer you'll get as input. If
you don't specify a seek callback, NULL is passed. (Option added in 7.18.0)
.IP CURLOPT_SOCKOPTFUNCTION
Pass a pointer to a function that matches the following prototype: \fBint
function(void *clientp, curl_socket_t curlfd, curlsocktype purpose);\fP. By
default, this parameter is unset. If set, this
function gets called by libcurl after the socket() call but before the
connect() call. The callback's \fIpurpose\fP argument identifies the exact
purpose for this particular socket:
\fICURLSOCKTYPE_IPCXN\fP for actively created connections or since 7.28.0
\fICURLSOCKTYPE_ACCEPT\fP for FTP when the connection was setup with PORT/EPSV
(in earlier versions these sockets weren't passed to this callback).
Future versions of libcurl may support more purposes. It passes the newly
created socket descriptor so additional setsockopt() calls can be done at the
user's discretion. Return 0 (zero) from the callback on success. Return 1
from the callback function to signal an unrecoverable error to the library and
it will close the socket and return \fICURLE_COULDNT_CONNECT\fP. (Option
added in 7.16.0)
Added in 7.21.5, the callback function may return
\fICURL_SOCKOPT_ALREADY_CONNECTED\fP, which tells libcurl that the socket is
in fact already connected and then libcurl will not attempt to connect it.
.IP CURLOPT_SOCKOPTDATA
Pass a pointer that will be untouched by libcurl and passed as the first
argument in the sockopt callback set with \fICURLOPT_SOCKOPTFUNCTION\fP.
The default value of this parameter is unspecified.
(Option added in 7.16.0)
.IP CURLOPT_OPENSOCKETFUNCTION
Pass a pointer to a function that matches the following prototype:
\fBcurl_socket_t function(void *clientp, curlsocktype purpose, struct
curl_sockaddr *address);\fP. This function gets called by libcurl instead of
the \fIsocket(2)\fP call. The callback's \fIpurpose\fP argument identifies the
exact purpose for this particular socket: \fICURLSOCKTYPE_IPCXN\fP is for IP
based connections. Future versions of libcurl may support more purposes. It
passes the resolved peer address as a \fIaddress\fP argument so the callback
can modify the address or refuse to connect at all. The callback function
should return the socket or \fICURL_SOCKET_BAD\fP in case no connection could
be established or another error was detected. Any additional
\fIsetsockopt(2)\fP calls can be done on the socket at the user's discretion.
\fICURL_SOCKET_BAD\fP return value from the callback function will signal an
unrecoverable error to the library and it will return
\fICURLE_COULDNT_CONNECT\fP. This return code can be used for IP address
blacklisting. The default behavior is:
.nf
return socket(addr->family, addr->socktype, addr->protocol);
.fi
(Option added in 7.17.1.)
.IP CURLOPT_OPENSOCKETDATA
Pass a pointer that will be untouched by libcurl and passed as the first
argument in the opensocket callback set with \fICURLOPT_OPENSOCKETFUNCTION\fP.
The default value of this parameter is unspecified.
(Option added in 7.17.1.)
.IP CURLOPT_CLOSESOCKETFUNCTION
Pass a pointer to a function that matches the following prototype: \fBint
function(void *clientp, curl_socket_t item);\fP. This function gets called by
libcurl instead of the \fIclose(3)\fP or \fIclosesocket(3)\fP call when
sockets are closed (not for any other file descriptors). This is pretty much
the reverse to the \fICURLOPT_OPENSOCKETFUNCTION\fP option. Return 0 to signal
success and 1 if there was an error. (Option added in 7.21.7)
.IP CURLOPT_CLOSESOCKETDATA
Pass a pointer that will be untouched by libcurl and passed as the first
argument in the closesocket callback set with
\fICURLOPT_CLOSESOCKETFUNCTION\fP.
The default value of this parameter is unspecified.
(Option added in 7.21.7)
.IP CURLOPT_PROGRESSFUNCTION
Pass a pointer to a function that matches the following prototype:
\fBint function(void *clientp, double dltotal, double dlnow, double ultotal,
double ulnow);\fP
This function gets called by libcurl instead of its internal equivalent with a
frequent interval. While data is being transferred it will be called very
frequently, and during slow periods like when nothing is being transferred it
can slow down to about one call per second.
\fIclientp\fP is the pointer set with \fICURLOPT_PROGRESSDATA\fP, it is not
actually used by libcurl but is only passed along from the application to the
callback.
The callback gets told how much data libcurl will transfer and has
transferred, in number of bytes. \fIdltotal\fP is the total number of bytes
libcurl expects to download in this transfer. \fIdlnow\fP is the number of
bytes downloaded so far. \fIultotal\fP is the total number of bytes libcurl
expects to upload in this transfer. \fIulnow\fP is the number of bytes
uploaded so far.
Unknown/unused argument values passed to the callback will be set to zero
(like if you only download data, the upload size will remain 0). Many times
the callback will be called one or more times first, before it knows the data
sizes so a program must be made to handle that.
Returning a non-zero value from this callback will cause libcurl to abort the
transfer and return \fICURLE_ABORTED_BY_CALLBACK\fP.
If you transfer data with the multi interface, this function will not be
called during periods of idleness unless you call the appropriate libcurl
function that performs transfers.
\fICURLOPT_NOPROGRESS\fP must be set to 0 to make this function actually
get called.
.IP CURLOPT_XFERINFOFUNCTION
Pass a pointer to a function that matches the following prototype:
.nf
\fBint function(void *clientp, curl_off_t dltotal, curl_off_t dlnow,
curl_off_t ultotal, curl_off_t ulnow);\fP
.fi
This function gets called by libcurl instead of its internal equivalent with a
frequent interval. While data is being transferred it will be called very
frequently, and during slow periods like when nothing is being transferred it
can slow down to about one call per second.
\fIclientp\fP is the pointer set with \fICURLOPT_XFERINFODATA\fP, it is only
passed along from the application to the callback.
The callback gets told how much data libcurl will transfer and has
transferred, in number of bytes. \fIdltotal\fP is the total number of bytes
libcurl expects to download in this transfer. \fIdlnow\fP is the number of
bytes downloaded so far. \fIultotal\fP is the total number of bytes libcurl
expects to upload in this transfer. \fIulnow\fP is the number of bytes
uploaded so far.
Unknown/unused argument values passed to the callback will be set to zero
(like if you only download data, the upload size will remain 0). Many times
the callback will be called one or more times first, before it knows the data
sizes so a program must be made to handle that.
Returning a non-zero value from this callback will cause libcurl to abort the
transfer and return \fICURLE_ABORTED_BY_CALLBACK\fP.
If you transfer data with the multi interface, this function will not be
called during periods of idleness unless you call the appropriate libcurl
function that performs transfers.
\fICURLOPT_NOPROGRESS\fP must be set to 0 to make this function actually
get called.
(Added in 7.32.0)
.IP CURLOPT_PROGRESSDATA
Pass a pointer that will be untouched by libcurl and passed as the first
argument in the progress callback set with \fICURLOPT_PROGRESSFUNCTION\fP.
The default value of this parameter is unspecified.
.IP CURLOPT_XFERINFODATA
Pass a pointer that will be untouched by libcurl and passed as the first
argument in the progress callback set with \fICURLOPT_XFERINFOFUNCTION\fP.
The default value of this parameter is unspecified. This option is an alias
for CURLOPT_PROGRESSDATA. (Added in 7.32.0)
.IP CURLOPT_HEADERFUNCTION
Pass a pointer to a function that matches the following prototype:
\fBsize_t function( void *ptr, size_t size, size_t nmemb, void
*userdata);\fP. This function gets called by libcurl as soon as it has
received header data. The header callback will be called once for each header
and only complete header lines are passed on to the callback. Parsing headers
is very easy using this. The size of the data pointed to by \fIptr\fP is
\fIsize\fP multiplied with \fInmemb\fP. Do not assume that the header line is
zero terminated! The pointer named \fIuserdata\fP is the one you set with the
\fICURLOPT_WRITEHEADER\fP option. The callback function must return the number
of bytes actually taken care of. If that amount differs from the amount passed
to your function, it'll signal an error to the library. This will abort the
transfer and return \fICURL_WRITE_ERROR\fP.
A complete HTTP header that is passed to this function can be up to
\fICURL_MAX_HTTP_HEADER\fP (100K) bytes.
If this option is not set, or if it is set to NULL, but
\fICURLOPT_HEADERDATA\fP (\fICURLOPT_WRITEHEADER\fP) is set to anything but
NULL, the function used to accept response data will be used instead. That is,
it will be the function specified with \fICURLOPT_WRITEFUNCTION\fP, or if it
is not specified or NULL - the default, stream-writing function.
It's important to note that the callback will be invoked for the headers of
all responses received after initiating a request and not just the final
response. This includes all responses which occur during authentication
negotiation. If you need to operate on only the headers from the final
response, you will need to collect headers in the callback yourself and use
HTTP status lines, for example, to delimit response boundaries.
When a server sends a chunked encoded transfer, it may contain a trailer. That
trailer is identical to a HTTP header and if such a trailer is received it is
passed to the application using this callback as well. There are several ways
to detect it being a trailer and not an ordinary header: 1) it comes after the
response-body. 2) it comes after the final header line (CR LF) 3) a Trailer:
header among the regular response-headers mention what header(s) to expect in
the trailer.
For non-HTTP protocols like FTP, POP3, IMAP and SMTP this function will get
called with the server responses to the commands that libcurl sends.
.IP CURLOPT_WRITEHEADER
(This option is also known as \fBCURLOPT_HEADERDATA\fP) Pass a pointer to be
used to write the header part of the received data to. If you don't use
\fICURLOPT_WRITEFUNCTION\fP or \fICURLOPT_HEADERFUNCTION\fP to take care of
the writing, this must be a valid FILE * as the internal default will then be
a plain fwrite(). See also the \fICURLOPT_HEADERFUNCTION\fP option above on
how to set a custom get-all-headers callback.
.IP CURLOPT_DEBUGFUNCTION
Pass a pointer to a function that matches the following prototype: \fBint
curl_debug_callback (CURL *, curl_infotype, char *, size_t, void *);\fP
\fICURLOPT_DEBUGFUNCTION\fP replaces the standard debug function used when
\fICURLOPT_VERBOSE \fP is in effect. This callback receives debug information,
as specified with the \fBcurl_infotype\fP argument. This function must return
0. The data pointed to by the char * passed to this function WILL NOT be zero
terminated, but will be exactly of the size as told by the size_t argument.
Available curl_infotype values:
.RS
.IP CURLINFO_TEXT
The data is informational text.
.IP CURLINFO_HEADER_IN
The data is header (or header-like) data received from the peer.
.IP CURLINFO_HEADER_OUT
The data is header (or header-like) data sent to the peer.
.IP CURLINFO_DATA_IN
The data is protocol data received from the peer.
.IP CURLINFO_DATA_OUT
The data is protocol data sent to the peer.
.RE
.IP CURLOPT_DEBUGDATA
Pass a pointer to whatever you want passed in to your
\fICURLOPT_DEBUGFUNCTION\fP in the last void * argument. This pointer is not
used by libcurl, it is only passed to the callback.
.IP CURLOPT_SSL_CTX_FUNCTION
This option does only function for libcurl powered by OpenSSL. If libcurl was
built against another SSL library, this functionality is absent.
Pass a pointer to a function that matches the following prototype:
\fBCURLcode sslctxfun(CURL *curl, void *sslctx, void *parm);\fP This function
gets called by libcurl just before the initialization of a SSL connection
after having processed all other SSL related options to give a last chance to
an application to modify the behaviour of openssl's ssl initialization. The
\fIsslctx\fP parameter is actually a pointer to an openssl \fISSL_CTX\fP. If
an error is returned no attempt to establish a connection is made and the
perform operation will return the error code from this callback function. Set
the \fIparm\fP argument with the \fICURLOPT_SSL_CTX_DATA\fP option. This
option was introduced in 7.11.0.
This function will get called on all new connections made to a server, during
the SSL negotiation. The SSL_CTX pointer will be a new one every time.
To use this properly, a non-trivial amount of knowledge of the openssl
libraries is necessary. For example, using this function allows you to use
openssl callbacks to add additional validation code for certificates, and even
to change the actual URI of a HTTPS request (example used in the lib509 test
case). See also the example section for a replacement of the key, certificate
and trust file settings.
.IP CURLOPT_SSL_CTX_DATA
Data pointer to pass to the ssl context callback set by the option
\fICURLOPT_SSL_CTX_FUNCTION\fP, this is the pointer you'll get as third
parameter, otherwise \fBNULL\fP. (Added in 7.11.0)
.IP CURLOPT_CONV_TO_NETWORK_FUNCTION
.IP CURLOPT_CONV_FROM_NETWORK_FUNCTION
.IP CURLOPT_CONV_FROM_UTF8_FUNCTION
Pass a pointer to a function that matches the following prototype:
\fBCURLcode function(char *ptr, size_t length);\fP
These three options apply to non-ASCII platforms only. They are available
only if \fBCURL_DOES_CONVERSIONS\fP was defined when libcurl was built. When
this is the case, \fIcurl_version_info(3)\fP will return the CURL_VERSION_CONV
feature bit set.
The data to be converted is in a buffer pointed to by the ptr parameter. The
amount of data to convert is indicated by the length parameter. The converted
data overlays the input data in the buffer pointed to by the ptr parameter.
CURLE_OK should be returned upon successful conversion. A CURLcode return
value defined by curl.h, such as CURLE_CONV_FAILED, should be returned if an
error was encountered.
\fBCURLOPT_CONV_TO_NETWORK_FUNCTION\fP and
\fBCURLOPT_CONV_FROM_NETWORK_FUNCTION\fP convert between the host encoding and
the network encoding. They are used when commands or ASCII data are
sent/received over the network.
\fBCURLOPT_CONV_FROM_UTF8_FUNCTION\fP is called to convert from UTF8 into the
host encoding. It is required only for SSL processing.
If you set a callback pointer to NULL, or don't set it at all, the built-in
libcurl iconv functions will be used. If HAVE_ICONV was not defined when
libcurl was built, and no callback has been established, conversion will
return the CURLE_CONV_REQD error code.
If HAVE_ICONV is defined, CURL_ICONV_CODESET_OF_HOST must also be defined.
For example:
\&#define CURL_ICONV_CODESET_OF_HOST "IBM-1047"
The iconv code in libcurl will default the network and UTF8 codeset names as
follows:
\&#define CURL_ICONV_CODESET_OF_NETWORK "ISO8859-1"
\&#define CURL_ICONV_CODESET_FOR_UTF8 "UTF-8"
You will need to override these definitions if they are different on your
system.
.IP CURLOPT_INTERLEAVEFUNCTION
Pass a pointer to a function that matches the following prototype:
\fBsize_t function( void *ptr, size_t size, size_t nmemb, void
*userdata)\fP. This function gets called by libcurl as soon as it has received
interleaved RTP data. This function gets called for each $ block and therefore
contains exactly one upper-layer protocol unit (e.g. one RTP packet). Curl
writes the interleaved header as well as the included data for each call. The
first byte is always an ASCII dollar sign. The dollar sign is followed by a
one byte channel identifier and then a 2 byte integer length in network byte
order. See \fIRFC2326 Section 10.12\fP for more information on how RTP
interleaving behaves. If unset or set to NULL, curl will use the default write
function.
Interleaved RTP poses some challenges for the client application. Since the
stream data is sharing the RTSP control connection, it is critical to service
the RTP in a timely fashion. If the RTP data is not handled quickly,
subsequent response processing may become unreasonably delayed and the
connection may close. The application may use \fICURL_RTSPREQ_RECEIVE\fP to
service RTP data when no requests are desired. If the application makes a
request, (e.g. \fICURL_RTSPREQ_PAUSE\fP) then the response handler will
process any pending RTP data before marking the request as finished. (Added
in 7.20.0)
.IP CURLOPT_INTERLEAVEDATA
This is the userdata pointer that will be passed to
\fICURLOPT_INTERLEAVEFUNCTION\fP when interleaved RTP data is received. (Added
in 7.20.0)
.IP CURLOPT_CHUNK_BGN_FUNCTION
Pass a pointer to a function that matches the following prototype:
\fBlong function (const void *transfer_info, void *ptr, int remains)\fP. This
function gets called by libcurl before a part of the stream is going to be
transferred (if the transfer supports chunks).
This callback makes sense only when using the \fICURLOPT_WILDCARDMATCH\fP
option for now.
The target of transfer_info parameter is a "feature depended" structure. For
the FTP wildcard download, the target is curl_fileinfo structure (see
\fIcurl/curl.h\fP). The parameter ptr is a pointer given by
\fICURLOPT_CHUNK_DATA\fP. The parameter remains contains number of chunks
remaining per the transfer. If the feature is not available, the parameter has
zero value.
Return \fICURL_CHUNK_BGN_FUNC_OK\fP if everything is fine,
\fICURL_CHUNK_BGN_FUNC_SKIP\fP if you want to skip the concrete chunk or
\fICURL_CHUNK_BGN_FUNC_FAIL\fP to tell libcurl to stop if some error occurred.
(This was added in 7.21.0)
.IP CURLOPT_CHUNK_END_FUNCTION
Pass a pointer to a function that matches the following prototype:
\fBlong function(void *ptr)\fP. This function gets called by libcurl as soon
as a part of the stream has been transferred (or skipped).
Return \fICURL_CHUNK_END_FUNC_OK\fP if everything is fine or
\fBCURL_CHUNK_END_FUNC_FAIL\fP to tell the lib to stop if some error occurred.
(This was added in 7.21.0)
.IP CURLOPT_CHUNK_DATA
Pass a pointer that will be untouched by libcurl and passed as the ptr
argument to the \fICURL_CHUNK_BGN_FUNTION\fP and \fICURL_CHUNK_END_FUNTION\fP.
(This was added in 7.21.0)
.IP CURLOPT_FNMATCH_FUNCTION
Pass a pointer to a function that matches the following prototype: \fBint
function(void *ptr, const char *pattern, const char *string)\fP prototype (see
\fIcurl/curl.h\fP). It is used internally for the wildcard matching feature.
Return \fICURL_FNMATCHFUNC_MATCH\fP if pattern matches the string,
\fICURL_FNMATCHFUNC_NOMATCH\fP if not or \fICURL_FNMATCHFUNC_FAIL\fP if an
error occurred. (This was added in 7.21.0)
.IP CURLOPT_FNMATCH_DATA
Pass a pointer that will be untouched by libcurl and passed as the ptr argument
to the \fICURL_FNMATCH_FUNCTION\fP. (This was added in 7.21.0)
.SH ERROR OPTIONS
.IP CURLOPT_ERRORBUFFER
Pass a char * to a buffer that the libcurl may store human readable error
messages in. This may be more helpful than just the return code from
\fIcurl_easy_perform\fP. The buffer must be at least CURL_ERROR_SIZE big.
Although this argument is a 'char *', it does not describe an input string.
Therefore the (probably undefined) contents of the buffer is NOT copied by the
library. You must keep the associated storage available until libcurl no
longer needs it. Failing to do so will cause very odd behavior or even
crashes. libcurl will need it until you call \fIcurl_easy_cleanup(3)\fP or you
set the same option again to use a different pointer.
Use \fICURLOPT_VERBOSE\fP and \fICURLOPT_DEBUGFUNCTION\fP to better
debug/trace why errors happen.
If the library does not return an error, the buffer may not have been
touched. Do not rely on the contents in those cases.
.IP CURLOPT_STDERR
Pass a FILE * as parameter. Tell libcurl to use this stream instead of stderr
when showing the progress meter and displaying \fICURLOPT_VERBOSE\fP data.
.IP CURLOPT_FAILONERROR
A parameter set to 1 tells the library to fail silently if the HTTP code
returned is equal to or larger than 400. The default action would be to return
the page normally, ignoring that code.
This method is not fail-safe and there are occasions where non-successful
response codes will slip through, especially when authentication is involved
(response codes 401 and 407).
You might get some amounts of headers transferred before this situation is
detected, like when a "100-continue" is received as a response to a
POST/PUT and a 401 or 407 is received immediately afterwards.
.SH NETWORK OPTIONS
.IP CURLOPT_URL
Pass in a pointer to the actual URL to deal with. The parameter should be a
char * to a zero terminated string which must be URL-encoded in the following
format:
scheme://host:port/path
For a greater explanation of the format please see RFC3986.
If the given URL lacks the scheme (such as "http://" or "ftp://" etc) then
libcurl will attempt to resolve the protocol based on one of the following
given host names:
HTTP, FTP, DICT, LDAP, IMAP, POP3 or SMTP
(POP3 and SMTP added in 7.31.0)
Should the protocol, either that specified by the scheme or deduced by libcurl
from the host name, not be supported by libcurl then
(\fICURLE_UNSUPPORTED_PROTOCOL\fP) will be returned from either the
\fIcurl_easy_perform(3)\fP or \fIcurl_multi_perform(3)\fP functions when you
call them. Use \fIcurl_version_info(3)\fP for detailed information of which
protocols are supported by the build of libcurl you are using.
The host part of the URL contains the address of the server that you want to
connect to. This can be the fully qualified domain name of the server, the
local network name of the machine on your network or the IP address of the
server or machine represented by either an IPv4 or IPv6 address. For example:
http://www.example.com/
http://hostname/
http://192.168.0.1/
http://[2001:1890:1112:1::20]/
It is also possible to specify the user name, password and any supported login
options as part of the host, for the following protocols, when connecting to
servers that require authentication:
http://user:password@www.example.com
ftp://user:password@ftp.example.com
imap://user:password;options@mail.example.com
pop3://user:password;options@mail.example.com
smtp://user:password;options@mail.example.com
At present only IMAP, POP3 and SMTP support login options as part of the host.
For more information about the login options in URL syntax please see RFC2384,
RFC5092 and IETF draft draft-earhart-url-smtp-00.txt (Added in 7.31.0).
The port is optional and when not specified libcurl will use the default port
based on the determined or specified protocol: 80 for HTTP, 21 for FTP and 25
for SMTP, etc. The following examples show how to specify the port:
http://www.example.com:8080/ - This will connect to a web server using port
8080 rather than 80.
smtp://mail.example.com:587/ - This will connect to a SMTP server on the
alternative mail port.
The path part of the URL is protocol specific and whilst some examples are
given below this list is not conclusive:
.B HTTP
The path part of a HTTP request specifies the file to retrieve and from what
directory. If the directory is not specified then the web server's root
directory is used. If the file is omitted then the default document will be
retrieved for either the directory specified or the root directory. The
exact resource returned for each URL is entirely dependent on the server's
configuration.
http://www.example.com - This gets the main page from the web server.
http://www.example.com/index.html - This returns the main page by explicitly
requesting it.
http://www.example.com/contactus/ - This returns the default document from
the contactus directory.
.B FTP
The path part of an FTP request specifies the file to retrieve and from what
directory. If the file part is omitted then libcurl downloads the directory
listing for the directory specified. If the directory is omitted then
the directory listing for the root / home directory will be returned.
ftp://ftp.example.com - This retrieves the directory listing for the root
directory.
ftp://ftp.example.com/readme.txt - This downloads the file readme.txt from the
root directory.
ftp://ftp.example.com/libcurl/readme.txt - This downloads readme.txt from the
libcurl directory.
ftp://user:password@ftp.example.com/readme.txt - This retrieves the readme.txt
file from the user's home directory. When a username and password is
specified, everything that is specified in the path part is relative to the
user's home directory. To retrieve files from the root directory or a
directory underneath the root directory then the absolute path must be
specified by prepending an additional forward slash to the beginning of the
path.
ftp://user:password@ftp.example.com//readme.txt - This retrieves the readme.txt
from the root directory when logging in as a specified user.
.B SMTP
The path part of a SMTP request specifies the host name to present during
communication with the mail server. If the path is omitted then libcurl will
attempt to resolve the local computer's host name. However, this may not
return the fully qualified domain name that is required by some mail servers
and specifying this path allows you to set an alternative name, such as
your machine's fully qualified domain name, which you might have obtained
from an external function such as gethostname or getaddrinfo.
smtp://mail.example.com - This connects to the mail server at example.com and
sends your local computer's host name in the HELO / EHLO command.
smtp://mail.example.com/client.example.com - This will send client.example.com in
the HELO / EHLO command to the mail server at example.com.
.B POP3
The path part of a POP3 request specifies the message ID to retrieve. If the
ID is not specified then a list of waiting messages is returned instead.
pop3://user:password@mail.example.com - This lists the available messages for
the user
pop3://user:password@mail.example.com/1 - This retrieves the first message for
the user
.B IMAP
The path part of an IMAP request not only specifies the mailbox to list (Added
in 7.30.0) or select, but can also be used to check the UIDVALIDITY of the
mailbox and to specify the UID and SECTION of the message to fetch (Added in
7.30.0).
imap://user:password@mail.example.com - Performs a top level folder list
imap://user:password@mail.example.com/INBOX - Performs a folder list on the
user's inbox
imap://user:password@mail.example.com/INBOX/;UID=1 - Selects the user's inbox
and fetches message 1
imap://user:password@mail.example.com/INBOX;UIDVALIDITY=50/;UID=2 - Selects
the user's inbox, checks the UIDVALIDITY of the mailbox is 50 and fetches
message 2 if it is
imap://user:password@mail.example.com/INBOX/;UID=3/;SECTION=TEXT - Selects the
user's inbox and fetches message 3 with only the text portion of the message
For more information about the individual components of an IMAP URL please
see RFC5092.
.B SCP
The path part of a SCP request specifies the file to retrieve and from what
directory. The file part may not be omitted. The file is taken as an absolute
path from the root directory on the server. To specify a path relative to
the user's home directory on the server, prepend ~/ to the path portion.
If the user name is not embedded in the URL, it can be set with the
\fICURLOPT_USERPWD\fP or \fBCURLOPT_USERNAME\fP option.
scp://user@example.com/etc/issue - This specifies the file /etc/issue
scp://example.com/~/my-file - This specifies the file my-file in the
user's home directory on the server
.B SFTP
The path part of a SFTP request specifies the file to retrieve and from what
directory. If the file part is omitted then libcurl downloads the directory
listing for the directory specified. If the path ends in a / then a directory
listing is returned instead of a file. If the path is omitted entirely then
the directory listing for the root / home directory will be returned.
If the user name is not embedded in the URL, it can be set with the
\fICURLOPT_USERPWD\fP or \fBCURLOPT_USERNAME\fP option.
sftp://user:password@example.com/etc/issue - This specifies the file
/etc/issue
sftp://user@example.com/~/my-file - This specifies the file my-file in the
user's home directory
sftp://ssh.example.com/~/Documents/ - This requests a directory listing
of the Documents directory under the user's home directory
.B LDAP
The path part of a LDAP request can be used to specify the: Distinguished
Name, Attributes, Scope, Filter and Extension for a LDAP search. Each field
is separated by a question mark and when that field is not required an empty
string with the question mark separator should be included.
ldap://ldap.example.com/o=My%20Organisation - This will perform a LDAP search
with the DN as My Organisation.
ldap://ldap.example.com/o=My%20Organisation?postalAddress - This will perform
the same search but will only return postalAddress attributes.
ldap://ldap.example.com/?rootDomainNamingContext - This specifies an empty DN
and requests information about the rootDomainNamingContext attribute for an
Active Directory server.
For more information about the individual components of a LDAP URL please
see RFC4516.
.B RTMP
There's no official URL spec for RTMP so libcurl uses the URL syntax supported
by the underlying librtmp library. It has a syntax where it wants a
traditional URL, followed by a space and a series of space-separated
name=value pairs.
While space is not typically a "legal" letter, libcurl accepts them. When a
user wants to pass in a '#' (hash) character it will be treated as a fragment
and get cut off by libcurl if provided literally. You will instead have to
escape it by providing it as backslash and its ASCII value in hexadecimal:
"\\23".
.B NOTES
Starting with version 7.20.0, the fragment part of the URI will not be sent as
part of the path, which was previously the case.
\fICURLOPT_URL\fP is the only option that \fBmust\fP be set before
\fIcurl_easy_perform(3)\fP is called.
\fICURLOPT_PROTOCOLS\fP can be used to limit what protocols libcurl will use
for this transfer, independent of what libcurl has been compiled to
support. That may be useful if you accept the URL from an external source and
want to limit the accessibility.
.IP CURLOPT_PROTOCOLS
Pass a long that holds a bitmask of CURLPROTO_* defines. If used, this bitmask
limits what protocols libcurl may use in the transfer. This allows you to have
a libcurl built to support a wide range of protocols but still limit specific
transfers to only be allowed to use a subset of them. By default libcurl will
accept all protocols it supports. See also
\fICURLOPT_REDIR_PROTOCOLS\fP. (Added in 7.19.4)
.IP CURLOPT_REDIR_PROTOCOLS
Pass a long that holds a bitmask of CURLPROTO_* defines. If used, this bitmask
limits what protocols libcurl may use in a transfer that it follows to in a
redirect when \fICURLOPT_FOLLOWLOCATION\fP is enabled. This allows you to
limit specific transfers to only be allowed to use a subset of protocols in
redirections. By default libcurl will allow all protocols except for FILE and
SCP. This is a difference compared to pre-7.19.4 versions which
unconditionally would follow to all protocols supported. (Added in 7.19.4)
.IP CURLOPT_PROXY
Set HTTP proxy to use. The parameter should be a char * to a zero terminated
string holding the host name or dotted IP address. To specify port number in
this string, append :[port] to the end of the host name. The proxy string may
be prefixed with [protocol]:// since any such prefix will be ignored. The
proxy's port number may optionally be specified with the separate option. If
not specified, libcurl will default to using port 1080 for proxies.
\fICURLOPT_PROXYPORT\fP.
When you tell the library to use a HTTP proxy, libcurl will transparently
convert operations to HTTP even if you specify an FTP URL etc. This may have
an impact on what other features of the library you can use, such as
\fICURLOPT_QUOTE\fP and similar FTP specifics that don't work unless you
tunnel through the HTTP proxy. Such tunneling is activated with
\fICURLOPT_HTTPPROXYTUNNEL\fP.
libcurl respects the environment variables \fBhttp_proxy\fP, \fBftp_proxy\fP,
\fBall_proxy\fP etc, if any of those are set. The \fICURLOPT_PROXY\fP option
does however override any possibly set environment variables.
Setting the proxy string to "" (an empty string) will explicitly disable the
use of a proxy, even if there is an environment variable set for it.
Since 7.14.1, the proxy host string given in environment variables can be
specified the exact same way as the proxy can be set with \fICURLOPT_PROXY\fP,
include protocol prefix (http://) and embedded user + password.
Since 7.21.7, the proxy string may be specified with a protocol:// prefix to
specify alternative proxy protocols. Use socks4://, socks4a://, socks5:// or
socks5h:// (the last one to enable socks5 and asking the proxy to do the
resolving, also known as CURLPROXY_SOCKS5_HOSTNAME type) to request the
specific SOCKS version to be used. No protocol specified, http:// and all
others will be treated as HTTP proxies.
.IP CURLOPT_PROXYPORT
Pass a long with this option to set the proxy port to connect to unless it is
specified in the proxy string \fICURLOPT_PROXY\fP.
.IP CURLOPT_PROXYTYPE
Pass a long with this option to set type of the proxy. Available options for
this are \fICURLPROXY_HTTP\fP, \fICURLPROXY_HTTP_1_0\fP (added in 7.19.4),
\fICURLPROXY_SOCKS4\fP (added in 7.10), \fICURLPROXY_SOCKS5\fP,
\fICURLPROXY_SOCKS4A\fP (added in 7.18.0) and \fICURLPROXY_SOCKS5_HOSTNAME\fP
(added in 7.18.0). The HTTP type is default. (Added in 7.10)
If you set \fBCURLOPT_PROXYTYPE\fP to \fICURLPROXY_HTTP_1_0\fP, it will only
affect how libcurl speaks to a proxy when CONNECT is used. The HTTP version
used for "regular" HTTP requests is instead controlled with
\fICURLOPT_HTTP_VERSION\fP.
.IP CURLOPT_NOPROXY
Pass a pointer to a zero terminated string. The string consists of a comma
separated list of host names that do not require a proxy to get reached, even
if one is specified. The only wildcard available is a single * character,
which matches all hosts, and effectively disables the proxy. Each name in this
list is matched as either a domain which contains the hostname, or the
hostname itself. For example, example.com would match example.com,
example.com:80, and www.example.com, but not www.notanexample.com. (Added in
7.19.4)
.IP CURLOPT_HTTPPROXYTUNNEL
Set the parameter to 1 to make the library tunnel all operations through a
given HTTP proxy. There is a big difference between using a proxy and to
tunnel through it. If you don't know what this means, you probably don't want
this tunneling option.
.IP CURLOPT_SOCKS5_GSSAPI_SERVICE
Pass a char * as parameter to a string holding the name of the service. The
default service name for a SOCKS5 server is rcmd/server-fqdn. This option
allows you to change it. (Added in 7.19.4)
.IP CURLOPT_SOCKS5_GSSAPI_NEC
Pass a long set to 1 to enable or 0 to disable. As part of the gssapi
negotiation a protection mode is negotiated. The RFC1961 says in section
4.3/4.4 it should be protected, but the NEC reference implementation does not.
If enabled, this option allows the unprotected exchange of the protection mode
negotiation. (Added in 7.19.4).
.IP CURLOPT_INTERFACE
Pass a char * as parameter. This sets the interface name to use as outgoing
network interface. The name can be an interface name, an IP address, or a host
name.
Starting with 7.24.0: If the parameter starts with "if!" then it is treated as
only as interface name and no attempt will ever be named to do treat it as an
IP address or to do name resolution on it. If the parameter starts with
\&"host!" it is treated as either an IP address or a hostname. Hostnames are
resolved synchronously. Using the if! format is highly recommended when using
the multi interfaces to avoid allowing the code to block. If "if!" is
specified but the parameter does not match an existing interface,
CURLE_INTERFACE_FAILED is returned.
.IP CURLOPT_LOCALPORT
Pass a long. This sets the local port number of the socket used for
connection. This can be used in combination with \fICURLOPT_INTERFACE\fP and
you are recommended to use \fICURLOPT_LOCALPORTRANGE\fP as well when this is
set. Valid port numbers are 1 - 65535. (Added in 7.15.2)
.IP CURLOPT_LOCALPORTRANGE
Pass a long. This is the number of attempts libcurl will make to find a
working local port number. It starts with the given \fICURLOPT_LOCALPORT\fP
and adds one to the number for each retry. Setting this to 1 or below will
make libcurl do only one try for the exact port number. Port numbers by nature
are scarce resources that will be busy at times so setting this value to
something too low might cause unnecessary connection setup failures. (Added in
7.15.2)
.IP CURLOPT_DNS_CACHE_TIMEOUT
Pass a long, this sets the timeout in seconds. Name resolves will be kept in
memory for this number of seconds. Set to zero to completely disable
caching, or set to -1 to make the cached entries remain forever. By default,
libcurl caches this info for 60 seconds.
The name resolve functions of various libc implementations don't re-read name
server information unless explicitly told so (for example, by calling
\fIres_init(3)\fP). This may cause libcurl to keep using the older server even
if DHCP has updated the server info, and this may look like a DNS cache issue
to the casual libcurl-app user.
.IP CURLOPT_DNS_USE_GLOBAL_CACHE
Pass a long. If the value is 1, it tells curl to use a global DNS cache
that will survive between easy handle creations and deletions. This is not
thread-safe and this will use a global variable.
\fBWARNING:\fP this option is considered obsolete. Stop using it. Switch over
to using the share interface instead! See \fICURLOPT_SHARE\fP and
\fIcurl_share_init(3)\fP.
.IP CURLOPT_BUFFERSIZE
Pass a long specifying your preferred size (in bytes) for the receive buffer
in libcurl. The main point of this would be that the write callback gets
called more often and with smaller chunks. This is just treated as a request,
not an order. You cannot be guaranteed to actually get the given size. (Added
in 7.10)
This size is by default set as big as possible (CURL_MAX_WRITE_SIZE), so it
only makes sense to use this option if you want it smaller.
.IP CURLOPT_PORT
Pass a long specifying what remote port number to connect to, instead of the
one specified in the URL or the default port for the used protocol.
.IP CURLOPT_TCP_NODELAY
Pass a long specifying whether the TCP_NODELAY option is to be set or cleared
(1 = set, 0 = clear). The option is cleared by default. This will have no
effect after the connection has been established.
Setting this option will disable TCP's Nagle algorithm. The purpose of this
algorithm is to try to minimize the number of small packets on the network
(where "small packets" means TCP segments less than the Maximum Segment Size
(MSS) for the network).
Maximizing the amount of data sent per TCP segment is good because it
amortizes the overhead of the send. However, in some cases (most notably
telnet or rlogin) small segments may need to be sent without delay. This is
less efficient than sending larger amounts of data at a time, and can
contribute to congestion on the network if overdone.
.IP CURLOPT_ADDRESS_SCOPE
Pass a long specifying the scope_id value to use when connecting to IPv6
link-local or site-local addresses. (Added in 7.19.0)
.IP CURLOPT_TCP_KEEPALIVE
Pass a long. If set to 1, TCP keepalive probes will be sent. The delay and
frequency of these probes can be controlled by the \fICURLOPT_TCP_KEEPIDLE\fP
and \fICURLOPT_TCP_KEEPINTVL\fP options, provided the operating system supports
them. Set to 0 (default behavior) to disable keepalive probes (Added in
7.25.0).
.IP CURLOPT_TCP_KEEPIDLE
Pass a long. Sets the delay, in seconds, that the operating system will wait
while the connection is idle before sending keepalive probes. Not all operating
systems support this option. (Added in 7.25.0)
.IP CURLOPT_TCP_KEEPINTVL
Pass a long. Sets the interval, in seconds, that the operating system will wait
between sending keepalive probes. Not all operating systems support this
option. (Added in 7.25.0)
.SH NAMES and PASSWORDS OPTIONS (Authentication)
.IP CURLOPT_NETRC
This parameter controls the preference of libcurl between using user names and
passwords from your \fI~/.netrc\fP file, relative to user names and passwords
in the URL supplied with \fICURLOPT_URL\fP.
libcurl uses a user name (and supplied or prompted password) supplied with
\fICURLOPT_USERPWD\fP in preference to any of the options controlled by this
parameter.
Pass a long, set to one of the values described below.
.RS
.IP CURL_NETRC_OPTIONAL
The use of your \fI~/.netrc\fP file is optional, and information in the URL is
to be preferred. The file will be scanned for the host and user name (to
find the password only) or for the host only, to find the first user name and
password after that \fImachine\fP, which ever information is not specified in
the URL.
Undefined values of the option will have this effect.
.IP CURL_NETRC_IGNORED
The library will ignore the file and use only the information in the URL.
This is the default.
.IP CURL_NETRC_REQUIRED
This value tells the library that use of the file is required, to ignore the
information in the URL, and to search the file for the host only.
.RE
Only machine name, user name and password are taken into account
(init macros and similar things aren't supported).
libcurl does not verify that the file has the correct properties set (as the
standard Unix ftp client does). It should only be readable by user.
.IP CURLOPT_NETRC_FILE
Pass a char * as parameter, pointing to a zero terminated string containing
the full path name to the file you want libcurl to use as .netrc file. If this
option is omitted, and \fICURLOPT_NETRC\fP is set, libcurl will attempt to
find a .netrc file in the current user's home directory. (Added in 7.10.9)
.IP CURLOPT_USERPWD
Pass a char * as parameter, pointing to a zero terminated login details string
for the connection. The format of which is: [user name]:[password].
When using NTLM, you can set the domain by prepending it to the user name and
separating the domain and name with a forward (/) or backward slash (\\). Like
this: "domain/user:password" or "domain\\user:password". Some HTTP servers (on
Windows) support this style even for Basic authentication.
When using HTTP and \fICURLOPT_FOLLOWLOCATION\fP, libcurl might perform
several requests to possibly different hosts. libcurl will only send this user
and password information to hosts using the initial host name (unless
\fICURLOPT_UNRESTRICTED_AUTH\fP is set), so if libcurl follows locations to
other hosts it will not send the user and password to those. This is enforced
to prevent accidental information leakage.
Use \fICURLOPT_HTTPAUTH\fP to specify the authentication method for HTTP based
connections or \fICURLOPT_LOGIN_OPTIONS\fP to control IMAP, POP3 and SMTP
options.
The user and password strings are not URL decoded, so there's no way to send
in a user name containing a colon using this option. Use \fICURLOPT_USERNAME\fP
for that, or include it in the URL.
.IP CURLOPT_PROXYUSERPWD
Pass a char * as parameter, which should be [user name]:[password] to use for
the connection to the HTTP proxy. Both the name and the password will be URL
decoded before use, so to include for example a colon in the user name you
should encode it as %3A.
Use \fICURLOPT_PROXYAUTH\fP to specify the authentication method.
.IP CURLOPT_USERNAME
Pass a char * as parameter, which should be pointing to the zero terminated
user name to use for the transfer.
\fBCURLOPT_USERNAME\fP sets the user name to be used in protocol
authentication. You should not use this option together with the (older)
CURLOPT_USERPWD option.
To specify the password and login options, along with the user name, use the
\fICURLOPT_PASSWORD\fP and \fICURLOPT_LOGIN_OPTIONS\fP options. (Added in
7.19.1)
.IP CURLOPT_PASSWORD
Pass a char * as parameter, which should be pointing to the zero terminated
password to use for the transfer.
The CURLOPT_PASSWORD option should be used in conjunction with the
\fICURLOPT_USERNAME\fP option. (Added in 7.19.1)
.IP CURLOPT_LOGIN_OPTIONS
(Added in 7.34.0) Pass a char * as parameter, which should be pointing to the
zero terminated options string to use for the transfer.
At present only IMAP, POP3 and SMTP support login options. For more
information about the login options please see RFC2384, RFC5092 and IETF draft
draft-earhart-url-smtp-00.txt
\fBCURLOPT_LOGIN_OPTIONS\fP can be used to set protocol specific login options,
such as the preferred authentication mechanism via "AUTH=NTLM" or "AUTH=*",
and should be used in conjunction with the \fICURLOPT_USERNAME\fP option.
.IP CURLOPT_PROXYUSERNAME
Pass a char * as parameter, which should be pointing to the zero terminated
user name to use for the transfer while connecting to Proxy.
The CURLOPT_PROXYUSERNAME option should be used in same way as the
\fICURLOPT_PROXYUSERPWD\fP is used. In comparison to
\fICURLOPT_PROXYUSERPWD\fP the CURLOPT_PROXYUSERNAME allows the username to
contain a colon, like in the following example: "sip:user@example.com". The
CURLOPT_PROXYUSERNAME option is an alternative way to set the user name while
connecting to Proxy. There is no meaning to use it together with the
\fICURLOPT_PROXYUSERPWD\fP option.
In order to specify the password to be used in conjunction with the user name
use the \fICURLOPT_PROXYPASSWORD\fP option. (Added in 7.19.1)
.IP CURLOPT_PROXYPASSWORD
Pass a char * as parameter, which should be pointing to the zero terminated
password to use for the transfer while connecting to Proxy.
The CURLOPT_PROXYPASSWORD option should be used in conjunction with
the \fICURLOPT_PROXYUSERNAME\fP option. (Added in 7.19.1)
.IP CURLOPT_HTTPAUTH
Pass a long as parameter, which is set to a bitmask, to tell libcurl which
authentication method(s) you want it to use. The available bits are listed
below. If more than one bit is set, libcurl will first query the site to see
which authentication methods it supports and then pick the best one you allow
it to use. For some methods, this will induce an extra network round-trip. Set
the actual name and password with the \fICURLOPT_USERPWD\fP option or
with the \fICURLOPT_USERNAME\fP and the \fICURLOPT_PASSWORD\fP options.
(Added in 7.10.6)
.RS
.IP CURLAUTH_BASIC
HTTP Basic authentication. This is the default choice, and the only method
that is in wide-spread use and supported virtually everywhere. This sends
the user name and password over the network in plain text, easily captured by
others.
.IP CURLAUTH_DIGEST
HTTP Digest authentication. Digest authentication is defined in RFC2617 and
is a more secure way to do authentication over public networks than the
regular old-fashioned Basic method.
.IP CURLAUTH_DIGEST_IE
HTTP Digest authentication with an IE flavor. Digest authentication is
defined in RFC2617 and is a more secure way to do authentication over public
networks than the regular old-fashioned Basic method. The IE flavor is simply
that libcurl will use a special "quirk" that IE is known to have used before
version 7 and that some servers require the client to use. (This define was
added in 7.19.3)
.IP CURLAUTH_GSSNEGOTIATE
HTTP GSS-Negotiate authentication. The GSS-Negotiate (also known as plain
\&"Negotiate") method was designed by Microsoft and is used in their web
applications. It is primarily meant as a support for Kerberos5 authentication
but may also be used along with other authentication methods. For more
information see IETF draft draft-brezak-spnego-http-04.txt.
You need to build libcurl with a suitable GSS-API library for this to work.
.IP CURLAUTH_NTLM
HTTP NTLM authentication. A proprietary protocol invented and used by
Microsoft. It uses a challenge-response and hash concept similar to Digest, to
prevent the password from being eavesdropped.
You need to build libcurl with either OpenSSL, GnuTLS or NSS support for this
option to work, or build libcurl on Windows with SSPI support.
.IP CURLAUTH_NTLM_WB
NTLM delegating to winbind helper. Authentication is performed by a separate
binary application that is executed when needed. The name of the application
is specified at compile time but is typically /usr/bin/ntlm_auth
(Added in 7.22.0)
Note that libcurl will fork when necessary to run the winbind application and
kill it when complete, calling waitpid() to await its exit when done. On POSIX
operating systems, killing the process will cause a SIGCHLD signal to be
raised (regardless of whether \fICURLOPT_NOSIGNAL\fP is set), which must be
handled intelligently by the application. In particular, the application must
not unconditionally call wait() in its SIGCHLD signal handler to avoid being
subject to a race condition. This behavior is subject to change in future
versions of libcurl.
.IP CURLAUTH_ANY
This is a convenience macro that sets all bits and thus makes libcurl pick any
it finds suitable. libcurl will automatically select the one it finds most
secure.
.IP CURLAUTH_ANYSAFE
This is a convenience macro that sets all bits except Basic and thus makes
libcurl pick any it finds suitable. libcurl will automatically select the one
it finds most secure.
.IP CURLAUTH_ONLY
This is a meta symbol. Or this value together with a single specific auth
value to force libcurl to probe for un-restricted auth and if not, only that
single auth algorithm is acceptable. (Added in 7.21.3)
.RE
.IP CURLOPT_TLSAUTH_TYPE
Pass a long as parameter, which is set to a bitmask, to tell libcurl which
authentication method(s) you want it to use for TLS authentication.
.RS
.IP CURLOPT_TLSAUTH_SRP
TLS-SRP authentication. Secure Remote Password authentication for TLS is
defined in RFC5054 and provides mutual authentication if both sides have a
shared secret. To use TLS-SRP, you must also set the
\fICURLOPT_TLSAUTH_USERNAME\fP and \fICURLOPT_TLSAUTH_PASSWORD\fP options.
You need to build libcurl with GnuTLS or OpenSSL with TLS-SRP support for this
to work. (Added in 7.21.4)
.RE
.IP CURLOPT_TLSAUTH_USERNAME
Pass a char * as parameter, which should point to the zero terminated username
to use for the TLS authentication method specified with the
\fICURLOPT_TLSAUTH_TYPE\fP option. Requires that the
\fICURLOPT_TLS_PASSWORD\fP option also be set. (Added in 7.21.4)
.IP CURLOPT_TLSAUTH_PASSWORD
Pass a char * as parameter, which should point to the zero terminated password
to use for the TLS authentication method specified with the
\fICURLOPT_TLSAUTH_TYPE\fP option. Requires that the
\fICURLOPT_TLS_USERNAME\fP option also be set. (Added in 7.21.4)
.IP CURLOPT_PROXYAUTH
Pass a long as parameter, which is set to a bitmask, to tell libcurl which
authentication method(s) you want it to use for your proxy authentication. If
more than one bit is set, libcurl will first query the site to see what
authentication methods it supports and then pick the best one you allow it to
use. For some methods, this will induce an extra network round-trip. Set the
actual name and password with the \fICURLOPT_PROXYUSERPWD\fP option. The
bitmask can be constructed by or'ing together the bits listed above for the
\fICURLOPT_HTTPAUTH\fP option. \fICURLOPT_PROXYAUTH\fP was added in 7.10.7
.IP CURLOPT_SASL_IR
Pass a long. If the value is 1, curl will send the initial response to the
server in the first authentication packet in order to reduce the number of
ping pong requests. Only applicable to supporting SASL authentication
mechanisms and to the IMAP, POP3 and SMTP protocols. (Added in 7.31.0)
Note: Whilst IMAP supports this option there is no need to explicitly set it,
as libcurl can determine the feature itself when the server supports the
SASL-IR CAPABILITY.
.IP CURLOPT_XOAUTH2_BEARER
Pass a char * as parameter, which should point to the zero terminated OAuth
2.0 Bearer Access Token for use with IMAP, POP3 and SMTP servers that support
the OAuth 2.0 Authorization Framework. (Added in 7.33.0)
Note: The user name used to generate the Bearer Token should be supplied via
the \fICURLOPT_USERNAME\fP option.
.SH HTTP OPTIONS
.IP CURLOPT_AUTOREFERER
Pass a parameter set to 1 to enable this. When enabled, libcurl will
automatically set the Referer: field in requests where it follows a Location:
redirect.
.IP CURLOPT_ACCEPT_ENCODING
Sets the contents of the Accept-Encoding: header sent in a HTTP request, and
enables decoding of a response when a Content-Encoding: header is received.
Three encodings are supported: \fIidentity\fP, which does nothing,
\fIdeflate\fP which requests the server to compress its response using the
zlib algorithm, and \fIgzip\fP which requests the gzip algorithm. If a
zero-length string is set, then an Accept-Encoding: header containing all
supported encodings is sent.
This is a request, not an order; the server may or may not do it. This option
must be set (to any non-NULL value) or else any unsolicited encoding done by
the server is ignored. See the special file lib/README.encoding for details.
(This option was called CURLOPT_ENCODING before 7.21.6)
.IP CURLOPT_TRANSFER_ENCODING
Adds a request for compressed Transfer Encoding in the outgoing HTTP
request. If the server supports this and so desires, it can respond with the
HTTP response sent using a compressed Transfer-Encoding that will be
automatically uncompressed by libcurl on reception.
Transfer-Encoding differs slightly from the Content-Encoding you ask for with
\fBCURLOPT_ACCEPT_ENCODING\fP in that a Transfer-Encoding is strictly meant to
be for the transfer and thus MUST be decoded before the data arrives in the
client. Traditionally, Transfer-Encoding has been much less used and supported
by both HTTP clients and HTTP servers.
(Added in 7.21.6)
.IP CURLOPT_FOLLOWLOCATION
A parameter set to 1 tells the library to follow any Location: header that the
server sends as part of a HTTP header.
This means that the library will re-send the same request on the new location
and follow new Location: headers all the way until no more such headers are
returned. \fICURLOPT_MAXREDIRS\fP can be used to limit the number of redirects
libcurl will follow.
Since 7.19.4, libcurl can limit what protocols it will automatically
follow. The accepted protocols are set with \fICURLOPT_REDIR_PROTOCOLS\fP and
it excludes the FILE protocol by default.
.IP CURLOPT_UNRESTRICTED_AUTH
A parameter set to 1 tells the library it can continue to send authentication
(user+password) when following locations, even when hostname changed. This
option is meaningful only when setting \fICURLOPT_FOLLOWLOCATION\fP.
.IP CURLOPT_MAXREDIRS
Pass a long. The set number will be the redirection limit. If that many
redirections have been followed, the next redirect will cause an error
(\fICURLE_TOO_MANY_REDIRECTS\fP). This option only makes sense if the
\fICURLOPT_FOLLOWLOCATION\fP is used at the same time. Added in 7.15.1:
Setting the limit to 0 will make libcurl refuse any redirect. Set it to -1 for
an infinite number of redirects (which is the default)
.IP CURLOPT_POSTREDIR
Pass a bitmask to control how libcurl acts on redirects after POSTs that get a
301, 302 or 303 response back. A parameter with bit 0 set (value
\fBCURL_REDIR_POST_301\fP) tells the library to respect RFC2616/10.3.2 and not
convert POST requests into GET requests when following a 301 redirection.
Setting bit 1 (value \fBCURL_REDIR_POST_302\fP) makes libcurl maintain the
request method after a 302 redirect whilst setting bit 2 (value
\fBCURL_REDIR_POST_303\fP) makes libcurl maintain the request method after a
303 redirect. The value \fBCURL_REDIR_POST_ALL\fP is a convenience define that
sets all three bits.
The non-RFC behaviour is ubiquitous in web browsers, so the library does the
conversion by default to maintain consistency. However, a server may require a
POST to remain a POST after such a redirection. This option is meaningful only
when setting \fICURLOPT_FOLLOWLOCATION\fP. (Added in 7.17.1) (This option was
known as CURLOPT_POST301 up to 7.19.0 as it only supported the 301 then)
.IP CURLOPT_PUT
A parameter set to 1 tells the library to use HTTP PUT to transfer data. The
data should be set with \fICURLOPT_READDATA\fP and \fICURLOPT_INFILESIZE\fP.
This option is deprecated and starting with version 7.12.1 you should instead
use \fICURLOPT_UPLOAD\fP.
.IP CURLOPT_POST
A parameter set to 1 tells the library to do a regular HTTP post. This will
also make the library use a "Content-Type:
application/x-www-form-urlencoded" header. (This is by far the most commonly
used POST method).
Use one of \fICURLOPT_POSTFIELDS\fP or \fICURLOPT_COPYPOSTFIELDS\fP options to
specify what data to post and \fICURLOPT_POSTFIELDSIZE\fP or
\fICURLOPT_POSTFIELDSIZE_LARGE\fP to set the data size.
Optionally, you can provide data to POST using the \fICURLOPT_READFUNCTION\fP
and \fICURLOPT_READDATA\fP options but then you must make sure to not set
\fICURLOPT_POSTFIELDS\fP to anything but NULL. When providing data with a
callback, you must transmit it using chunked transfer-encoding or you must set
the size of the data with the \fICURLOPT_POSTFIELDSIZE\fP or
\fICURLOPT_POSTFIELDSIZE_LARGE\fP option. To enable chunked encoding, you
simply pass in the appropriate Transfer-Encoding header, see the
post-callback.c example.
You can override the default POST Content-Type: header by setting your own
with \fICURLOPT_HTTPHEADER\fP.
Using POST with HTTP 1.1 implies the use of a "Expect: 100-continue" header.
You can disable this header with \fICURLOPT_HTTPHEADER\fP as usual.
If you use POST to a HTTP 1.1 server, you can send data without knowing the
size before starting the POST if you use chunked encoding. You enable this by
adding a header like "Transfer-Encoding: chunked" with
\fICURLOPT_HTTPHEADER\fP. With HTTP 1.0 or without chunked transfer, you must
specify the size in the request.
When setting \fICURLOPT_POST\fP to 1, it will automatically set
\fICURLOPT_NOBODY\fP to 0 (since 7.14.1).
If you issue a POST request and then want to make a HEAD or GET using the same
re-used handle, you must explicitly set the new request type using
\fICURLOPT_NOBODY\fP or \fICURLOPT_HTTPGET\fP or similar.
.IP CURLOPT_POSTFIELDS
Pass a void * as parameter, which should be the full data to post in a HTTP
POST operation. You must make sure that the data is formatted the way you want
the server to receive it. libcurl will not convert or encode it for you. Most
web servers will assume this data to be url-encoded.
The pointed data are NOT copied by the library: as a consequence, they must
be preserved by the calling application until the transfer finishes.
This POST is a normal application/x-www-form-urlencoded kind (and libcurl will
set that Content-Type by default when this option is used), which is the most
commonly used one by HTML forms. See also the \fICURLOPT_POST\fP. Using
\fICURLOPT_POSTFIELDS\fP implies \fICURLOPT_POST\fP.
If you want to do a zero-byte POST, you need to set
\fICURLOPT_POSTFIELDSIZE\fP explicitly to zero, as simply setting
\fICURLOPT_POSTFIELDS\fP to NULL or "" just effectively disables the sending
of the specified string. libcurl will instead assume that you'll send the POST
data using the read callback!
Using POST with HTTP 1.1 implies the use of a "Expect: 100-continue" header.
You can disable this header with \fICURLOPT_HTTPHEADER\fP as usual.
To make multipart/formdata posts (aka RFC2388-posts), check out the
\fICURLOPT_HTTPPOST\fP option.
.IP CURLOPT_POSTFIELDSIZE
If you want to post data to the server without letting libcurl do a strlen()
to measure the data size, this option must be used. When this option is used
you can post fully binary data, which otherwise is likely to fail. If this
size is set to -1, the library will use strlen() to get the size.
.IP CURLOPT_POSTFIELDSIZE_LARGE
Pass a curl_off_t as parameter. Use this to set the size of the
\fICURLOPT_POSTFIELDS\fP data to prevent libcurl from doing strlen() on the
data to figure out the size. This is the large file version of the
\fICURLOPT_POSTFIELDSIZE\fP option. (Added in 7.11.1)
.IP CURLOPT_COPYPOSTFIELDS
Pass a char * as parameter, which should be the full data to post in a HTTP
POST operation. It behaves as the \fICURLOPT_POSTFIELDS\fP option, but the
original data are copied by the library, allowing the application to overwrite
the original data after setting this option.
Because data are copied, care must be taken when using this option in
conjunction with \fICURLOPT_POSTFIELDSIZE\fP or
\fICURLOPT_POSTFIELDSIZE_LARGE\fP: If the size has not been set prior to
\fICURLOPT_COPYPOSTFIELDS\fP, the data are assumed to be a NUL-terminated
string; else the stored size informs the library about the data byte count to
copy. In any case, the size must not be changed after
\fICURLOPT_COPYPOSTFIELDS\fP, unless another \fICURLOPT_POSTFIELDS\fP or
\fICURLOPT_COPYPOSTFIELDS\fP option is issued.
(Added in 7.17.1)
.IP CURLOPT_HTTPPOST
Tells libcurl you want a multipart/formdata HTTP POST to be made and you
instruct what data to pass on to the server. Pass a pointer to a linked list
of curl_httppost structs as parameter. The easiest way to create such a
list, is to use \fIcurl_formadd(3)\fP as documented. The data in this list
must remain intact until you close this curl handle again with
\fIcurl_easy_cleanup(3)\fP.
Using POST with HTTP 1.1 implies the use of a "Expect: 100-continue" header.
You can disable this header with \fICURLOPT_HTTPHEADER\fP as usual.
When setting \fICURLOPT_HTTPPOST\fP, it will automatically set
\fICURLOPT_NOBODY\fP to 0 (since 7.14.1).
.IP CURLOPT_REFERER
Pass a pointer to a zero terminated string as parameter. It will be used to
set the Referer: header in the http request sent to the remote server. This
can be used to fool servers or scripts. You can also set any custom header
with \fICURLOPT_HTTPHEADER\fP.
.IP CURLOPT_USERAGENT
Pass a pointer to a zero terminated string as parameter. It will be used to
set the User-Agent: header in the http request sent to the remote server. This
can be used to fool servers or scripts. You can also set any custom header
with \fICURLOPT_HTTPHEADER\fP.
.IP CURLOPT_HTTPHEADER
Pass a pointer to a linked list of HTTP headers to pass to the server in your
HTTP request. The linked list should be a fully valid list of \fBstruct
curl_slist\fP structs properly filled in. Use \fIcurl_slist_append(3)\fP to
create the list and \fIcurl_slist_free_all(3)\fP to clean up an entire
list. If you add a header that is otherwise generated and used by libcurl
internally, your added one will be used instead. If you add a header with no
content as in 'Accept:' (no data on the right side of the colon), the
internally used header will get disabled. Thus, using this option you can add
new headers, replace internal headers and remove internal headers. To add a
header with no content (nothing to the right side of the colon), use the
form 'MyHeader;' (note the ending semicolon).
The headers included in the linked list must not be CRLF-terminated, because
curl adds CRLF after each header item. Failure to comply with this will result
in strange bugs because the server will most likely ignore part of the headers
you specified.
The first line in a request (containing the method, usually a GET or POST) is
not a header and cannot be replaced using this option. Only the lines
following the request-line are headers. Adding this method line in this list
of headers will only cause your request to send an invalid header.
Pass a NULL to this to reset back to no custom headers.
The most commonly replaced headers have "shortcuts" in the options
\fICURLOPT_COOKIE\fP, \fICURLOPT_USERAGENT\fP and \fICURLOPT_REFERER\fP.
.IP CURLOPT_HTTP200ALIASES
Pass a pointer to a linked list of aliases to be treated as valid HTTP 200
responses. Some servers respond with a custom header response line. For
example, IceCast servers respond with "ICY 200 OK". By including this string
in your list of aliases, the response will be treated as a valid HTTP header
line such as "HTTP/1.0 200 OK". (Added in 7.10.3)
The linked list should be a fully valid list of struct curl_slist structs, and
be properly filled in. Use \fIcurl_slist_append(3)\fP to create the list and
\fIcurl_slist_free_all(3)\fP to clean up an entire list.
The alias itself is not parsed for any version strings. Before libcurl 7.16.3,
Libcurl used the value set by option \fICURLOPT_HTTP_VERSION\fP, but starting
with 7.16.3 the protocol is assumed to match HTTP 1.0 when an alias matched.
.IP CURLOPT_COOKIE
Pass a pointer to a zero terminated string as parameter. It will be used to
set a cookie in the http request. The format of the string should be
NAME=CONTENTS, where NAME is the cookie name and CONTENTS is what the cookie
should contain.
If you need to set multiple cookies, you need to set them all using a single
option and thus you need to concatenate them all in one single string. Set
multiple cookies in one string like this: "name1=content1; name2=content2;"
etc.
This option sets the cookie header explicitly in the outgoing request(s). If
multiple requests are done due to authentication, followed redirections or
similar, they will all get this cookie passed on.
Using this option multiple times will only make the latest string override the
previous ones.
.IP CURLOPT_COOKIEFILE
Pass a pointer to a zero terminated string as parameter. It should contain the
name of your file holding cookie data to read. The cookie data may be in
Netscape / Mozilla cookie data format or just regular HTTP-style headers
dumped to a file.
Given an empty or non-existing file or by passing the empty string (""), this
option will enable cookies for this curl handle, making it understand and
parse received cookies and then use matching cookies in future requests.
If you use this option multiple times, you just add more files to read.
Subsequent files will add more cookies.
.IP CURLOPT_COOKIEJAR
Pass a file name as char *, zero terminated. This will make libcurl write all
internally known cookies to the specified file when \fIcurl_easy_cleanup(3)\fP
is called. If no cookies are known, no file will be created. Specify "-" to
instead have the cookies written to stdout. Using this option also enables
cookies for this session, so if you for example follow a location it will make
matching cookies get sent accordingly.
If the cookie jar file can't be created or written to (when the
\fIcurl_easy_cleanup(3)\fP is called), libcurl will not and cannot report an
error for this. Using \fICURLOPT_VERBOSE\fP or \fICURLOPT_DEBUGFUNCTION\fP
will get a warning to display, but that is the only visible feedback you get
about this possibly lethal situation.
.IP CURLOPT_COOKIESESSION
Pass a long set to 1 to mark this as a new cookie "session". It will force
libcurl to ignore all cookies it is about to load that are "session cookies"
from the previous session. By default, libcurl always stores and loads all
cookies, independent if they are session cookies or not. Session cookies are
cookies without expiry date and they are meant to be alive and existing for
this "session" only.
.IP CURLOPT_COOKIELIST
Pass a char * to a cookie string. Cookie can be either in Netscape / Mozilla
format or just regular HTTP-style header (Set-Cookie: ...) format. If cURL
cookie engine was not enabled it will enable its cookie engine. Passing a
magic string \&"ALL" will erase all cookies known by cURL. (Added in 7.14.1)
Passing the special string \&"SESS" will only erase all session cookies known
by cURL. (Added in 7.15.4) Passing the special string \&"FLUSH" will write
all cookies known by cURL to the file specified by \fICURLOPT_COOKIEJAR\fP.
(Added in 7.17.1)
.IP CURLOPT_HTTPGET
Pass a long. If the long is 1, this forces the HTTP request to get back
to GET. Usable if a POST, HEAD, PUT, or a custom request has been used
previously using the same curl handle.
When setting \fICURLOPT_HTTPGET\fP to 1, it will automatically set
\fICURLOPT_NOBODY\fP to 0 and \fICURLOPT_UPLOAD\fP to 0.
.IP CURLOPT_HTTP_VERSION
Pass a long, set to one of the values described below. They force libcurl to
use the specific HTTP versions. This is not sensible to do unless you have a
good reason.
.RS
.IP CURL_HTTP_VERSION_NONE
We don't care about what version the library uses. libcurl will use whatever
it thinks fit.
.IP CURL_HTTP_VERSION_1_0
Enforce HTTP 1.0 requests.
.IP CURL_HTTP_VERSION_1_1
Enforce HTTP 1.1 requests.
.RE
.IP CURLOPT_IGNORE_CONTENT_LENGTH
Ignore the Content-Length header. This is useful for Apache 1.x (and similar
servers) which will report incorrect content length for files over 2
gigabytes. If this option is used, curl will not be able to accurately report
progress, and will simply stop the download when the server ends the
connection. (added in 7.14.1)
.IP CURLOPT_HTTP_CONTENT_DECODING
Pass a long to tell libcurl how to act on content decoding. If set to zero,
content decoding will be disabled. If set to 1 it is enabled. Libcurl has no
default content decoding but requires you to use \fICURLOPT_ACCEPT_ENCODING\fP
for that. (added in 7.16.2)
.IP CURLOPT_HTTP_TRANSFER_DECODING
Pass a long to tell libcurl how to act on transfer decoding. If set to zero,
transfer decoding will be disabled, if set to 1 it is enabled
(default). libcurl does chunked transfer decoding by default unless this
option is set to zero. (added in 7.16.2)
.SH SMTP OPTIONS
.IP CURLOPT_MAIL_FROM
Pass a pointer to a zero terminated string as parameter. This should be used
to specify the sender's email address when sending SMTP mail with libcurl.
An originator email address should be specified with angled brackets (<>)
around it, which if not specified, will be added by libcurl from version
7.21.4 onwards. Failing to provide such brackets may cause the server to
reject the email.
If this parameter is not specified then an empty address will be sent to the
mail server which may or may not cause the email to be rejected.
(Added in 7.20.0)
.IP CURLOPT_MAIL_RCPT
Pass a pointer to a linked list of recipients to pass to the server in your
SMTP mail request. The linked list should be a fully valid list of \fBstruct
curl_slist\fP structs properly filled in. Use \fIcurl_slist_append(3)\fP to
create the list and \fIcurl_slist_free_all(3)\fP to clean up an entire list.
When performing a mail transfer, each recipient should be specified within a
pair of angled brackets (<>), however, should you not use an angled bracket as
the first character libcurl will assume you provided a single email address and
enclose that address within brackets for you. (Added in 7.20.0)
When performing an address verification (VRFY command), each recipient should
be specified as the user name or user name and domain (as per Section 3.5 of
RFC5321). (Added in 7.34.0)
When performing a mailing list expand (EXPN command), each recipient should be
specified using the mailing list name, such as "Friends" or "London-Office".
(Added in 7.34.0)
.IP CURLOPT_MAIL_AUTH
Pass a pointer to a zero terminated string as parameter. This will be used
to specify the authentication address (identity) of a submitted message that
is being relayed to another server.
This optional parameter allows co-operating agents in a trusted environment to
communicate the authentication of individual messages and should only be used
by the application program, using libcurl, if the application is itself a
mail server acting in such an environment. If the application is operating as
such and the AUTH address is not known or is invalid, then an empty string
should be used for this parameter.
Unlike CURLOPT_MAIL_FROM and CURLOPT_MAIL_RCPT, the address should not be
specified within a pair of angled brackets (<>). However, if an empty string
is used then a pair of brackets will be sent by libcurl as required by
RFC2554.
(Added in 7.25.0)
.SH TFTP OPTIONS
.IP CURLOPT_TFTP_BLKSIZE
Specify block size to use for TFTP data transmission. Valid range as per
RFC2348 is 8-65464 bytes. The default of 512 bytes will be used if this option
is not specified. The specified block size will only be used pending support
by the remote server. If the server does not return an option acknowledgement
or returns an option acknowledgement with no blksize, the default of 512 bytes
will be used. (added in 7.19.4)
.SH FTP OPTIONS
.IP CURLOPT_FTPPORT
Pass a pointer to a zero terminated string as parameter. It will be used to
get the IP address to use for the FTP PORT instruction. The PORT instruction
tells the remote server to connect to our specified IP address. The string may
be a plain IP address, a host name, a network interface name (under Unix) or
just a '-' symbol to let the library use your system's default IP
address. Default FTP operations are passive, and thus won't use PORT.
The address can be followed by a ':' to specify a port, optionally followed by
a '-' to specify a port range. If the port specified is 0, the operating
system will pick a free port. If a range is provided and all ports in the
range are not available, libcurl will report CURLE_FTP_PORT_FAILED for the
handle. Invalid port/range settings are ignored. IPv6 addresses followed by
a port or portrange have to be in brackets. IPv6 addresses without port/range
specifier can be in brackets. (added in 7.19.5)
Examples with specified ports:
.nf
eth0:0
192.168.1.2:32000-33000
curl.se:32123
[::1]:1234-4567
.fi
You disable PORT again and go back to using the passive version by setting
this option to NULL.
.IP CURLOPT_QUOTE
Pass a pointer to a linked list of FTP or SFTP commands to pass to the server
prior to your FTP request. This will be done before any other commands are
issued (even before the CWD command for FTP). The linked list should be a
fully valid list of 'struct curl_slist' structs properly filled in with text
strings. Use \fIcurl_slist_append(3)\fP to append strings (commands) to the
list, and clear the entire list afterwards with
\fIcurl_slist_free_all(3)\fP. Disable this operation again by setting a NULL
to this option. When speaking to a FTP (or SFTP since 7.24.0) server, prefix
the command with an asterisk (*) to make libcurl continue even if the command
fails as by default libcurl will stop at first failure.
The set of valid FTP commands depends on the server (see RFC959 for a list of
mandatory commands).
The valid SFTP commands are: chgrp, chmod, chown, ln, mkdir, pwd, rename, rm,
rmdir, symlink (see
.BR curl (1))
(SFTP support added in 7.16.3)
.IP CURLOPT_POSTQUOTE
Pass a pointer to a linked list of FTP or SFTP commands to pass to the server
after your FTP transfer request. The commands will only be run if no error
occurred. The linked list should be a fully valid list of struct curl_slist
structs properly filled in as described for \fICURLOPT_QUOTE\fP. Disable this
operation again by setting a NULL to this option.
.IP CURLOPT_PREQUOTE
Pass a pointer to a linked list of FTP commands to pass to the server after
the transfer type is set. The linked list should be a fully valid list of
struct curl_slist structs properly filled in as described for
\fICURLOPT_QUOTE\fP. Disable this operation again by setting a NULL to this
option. Before version 7.16.0, if you also set \fICURLOPT_NOBODY\fP to 1, this
option didn't work.
.IP CURLOPT_DIRLISTONLY
A parameter set to 1 tells the library to just list the names of files in a
directory, instead of doing a full directory listing that would include file
sizes, dates etc. This works for FTP and SFTP URLs.
This causes an FTP NLST command to be sent on an FTP server. Beware that some
FTP servers list only files in their response to NLST; they might not include
subdirectories and symbolic links.
Setting this option to 1 also implies a directory listing even if the URL
doesn't end with a slash, which otherwise is necessary.
Do NOT use this option if you also use \fICURLOPT_WILDCARDMATCH\fP as it will
effectively break that feature then.
(This option was known as CURLOPT_FTPLISTONLY up to 7.16.4)
.IP CURLOPT_APPEND
A parameter set to 1 tells the library to append to the remote file instead of
overwrite it. This is only useful when uploading to an FTP site.
(This option was known as CURLOPT_FTPAPPEND up to 7.16.4)
.IP CURLOPT_FTP_USE_EPRT
Pass a long. If the value is 1, it tells curl to use the EPRT (and
LPRT) command when doing active FTP downloads (which is enabled by
\fICURLOPT_FTPPORT\fP). Using EPRT means that it will first attempt to use
EPRT and then LPRT before using PORT, but if you pass zero to this
option, it will not try using EPRT or LPRT, only plain PORT. (Added in 7.10.5)
If the server is an IPv6 host, this option will have no effect as of 7.12.3.
.IP CURLOPT_FTP_USE_EPSV
Pass a long. If the value is 1, it tells curl to use the EPSV command
when doing passive FTP downloads (which it always does by default). Using EPSV
means that it will first attempt to use EPSV before using PASV, but if you
pass zero to this option, it will not try using EPSV, only plain PASV.
If the server is an IPv6 host, this option will have no effect as of 7.12.3.
.IP CURLOPT_FTP_USE_PRET
Pass a long. If the value is 1, it tells curl to send a PRET command before
PASV (and EPSV). Certain FTP servers, mainly drftpd, require this non-standard
command for directory listings as well as up and downloads in PASV mode. Has
no effect when using the active FTP transfers mode. (Added in 7.20.0)
.IP CURLOPT_FTP_CREATE_MISSING_DIRS
Pass a long. If the value is 1, curl will attempt to create any remote
directory that it fails to CWD into. CWD is the command that changes working
directory. (Added in 7.10.7)
This setting also applies to SFTP-connections. curl will attempt to create
the remote directory if it can't obtain a handle to the target-location. The
creation will fail if a file of the same name as the directory to create
already exists or lack of permissions prevents creation. (Added in 7.16.3)
Starting with 7.19.4, you can also set this value to 2, which will make
libcurl retry the CWD command again if the subsequent MKD command fails. This
is especially useful if you're doing many simultaneous connections against the
same server and they all have this option enabled, as then CWD may first fail
but then another connection does MKD before this connection and thus MKD fails
but trying CWD works! 7.19.4 also introduced the \fICURLFTP_CREATE_DIR\fP and
\fICURLFTP_CREATE_DIR_RETRY\fP enum names for these arguments.
Before version 7.19.4, libcurl will simply ignore arguments set to 2 and act
as if 1 was selected.
.IP CURLOPT_FTP_RESPONSE_TIMEOUT
Pass a long. Causes curl to set a timeout period (in seconds) on the amount
of time that the server is allowed to take in order to generate a response
message for a command before the session is considered hung. While curl is
waiting for a response, this value overrides \fICURLOPT_TIMEOUT\fP. It is
recommended that if used in conjunction with \fICURLOPT_TIMEOUT\fP, you set
\fICURLOPT_FTP_RESPONSE_TIMEOUT\fP to a value smaller than
\fICURLOPT_TIMEOUT\fP. (Added in 7.10.8)
.IP CURLOPT_FTP_ALTERNATIVE_TO_USER
Pass a char * as parameter, pointing to a string which will be used to
authenticate if the usual FTP "USER user" and "PASS password" negotiation
fails. This is currently only known to be required when connecting to
Tumbleweed's Secure Transport FTPS server using client certificates for
authentication. (Added in 7.15.5)
.IP CURLOPT_FTP_SKIP_PASV_IP
Pass a long. If set to 1, it instructs libcurl to not use the IP address the
server suggests in its 227-response to libcurl's PASV command when libcurl
connects the data connection. Instead libcurl will re-use the same IP address
it already uses for the control connection. But it will use the port number
from the 227-response. (Added in 7.14.2)
This option has no effect if PORT, EPRT or EPSV is used instead of PASV.
.IP CURLOPT_FTPSSLAUTH
Pass a long using one of the values from below, to alter how libcurl issues
\&"AUTH TLS" or "AUTH SSL" when FTP over SSL is activated (see
\fICURLOPT_USE_SSL\fP). (Added in 7.12.2)
.RS
.IP CURLFTPAUTH_DEFAULT
Allow libcurl to decide.
.IP CURLFTPAUTH_SSL
Try "AUTH SSL" first, and only if that fails try "AUTH TLS".
.IP CURLFTPAUTH_TLS
Try "AUTH TLS" first, and only if that fails try "AUTH SSL".
.RE
.IP CURLOPT_FTP_SSL_CCC
If enabled, this option makes libcurl use CCC (Clear Command Channel). It
shuts down the SSL/TLS layer after authenticating. The rest of the
control channel communication will be unencrypted. This allows NAT routers
to follow the FTP transaction. Pass a long using one of the values below.
(Added in 7.16.1)
.RS
.IP CURLFTPSSL_CCC_NONE
Don't attempt to use CCC.
.IP CURLFTPSSL_CCC_PASSIVE
Do not initiate the shutdown, but wait for the server to do it. Do not send
a reply.
.IP CURLFTPSSL_CCC_ACTIVE
Initiate the shutdown and wait for a reply.
.RE
.IP CURLOPT_FTP_ACCOUNT
Pass a pointer to a zero terminated string (or NULL to disable). When an FTP
server asks for "account data" after user name and password has been provided,
this data is sent off using the ACCT command. (Added in 7.13.0)
.IP CURLOPT_FTP_FILEMETHOD
Pass a long that should have one of the following values. This option controls
what method libcurl should use to reach a file on a FTP(S) server. The
argument should be one of the following alternatives:
.RS
.IP CURLFTPMETHOD_MULTICWD
libcurl does a single CWD operation for each path part in the given URL. For
deep hierarchies this means many commands. This is how RFC1738 says it
should be done. This is the default but the slowest behavior.
.IP CURLFTPMETHOD_NOCWD
libcurl does no CWD at all. libcurl will do SIZE, RETR, STOR etc and give a
full path to the server for all these commands. This is the fastest behavior.
.IP CURLFTPMETHOD_SINGLECWD
libcurl does one CWD with the full target directory and then operates on the
file \&"normally" (like in the multicwd case). This is somewhat more standards
compliant than 'nocwd' but without the full penalty of 'multicwd'.
.RE
(Added in 7.15.1)
.SH RTSP OPTIONS
.IP CURLOPT_RTSP_REQUEST
Tell libcurl what kind of RTSP request to make. Pass one of the following RTSP
enum values. Unless noted otherwise, commands require the Session ID to be
initialized. (Added in 7.20.0)
.RS
.IP CURL_RTSPREQ_OPTIONS
Used to retrieve the available methods of the server. The application is
responsible for parsing and obeying the response. \fB(The session ID is not
needed for this method.)\fP (Added in 7.20.0)
.IP CURL_RTSPREQ_DESCRIBE
Used to get the low level description of a stream. The application should note
what formats it understands in the \fI'Accept:'\fP header. Unless set
manually, libcurl will automatically fill in \fI'Accept:
application/sdp'\fP. Time-condition headers will be added to Describe requests
if the \fICURLOPT_TIMECONDITION\fP option is active. \fB(The session ID is not
needed for this method)\fP (Added in 7.20.0)
.IP CURL_RTSPREQ_ANNOUNCE
When sent by a client, this method changes the description of the session. For
example, if a client is using the server to record a meeting, the client can
use Announce to inform the server of all the meta-information about the
session. ANNOUNCE acts like a HTTP PUT or POST just like
\fICURL_RTSPREQ_SET_PARAMETER\fP (Added in 7.20.0)
.IP CURL_RTSPREQ_SETUP
Setup is used to initialize the transport layer for the session. The
application must set the desired Transport options for a session by using the
\fICURLOPT_RTSP_TRANSPORT\fP option prior to calling setup. If no session ID
is currently set with \fICURLOPT_RTSP_SESSION_ID\fP, libcurl will extract and
use the session ID in the response to this request. \fB(The session ID is not
needed for this method).\fP (Added in 7.20.0)
.IP CURL_RTSPREQ_PLAY
Send a Play command to the server. Use the \fICURLOPT_RANGE\fP option to
modify the playback time (e.g. 'npt=10-15'). (Added in 7.20.0)
.IP CURL_RTSPREQ_PAUSE
Send a Pause command to the server. Use the \fICURLOPT_RANGE\fP option with a
single value to indicate when the stream should be halted. (e.g. npt='25')
(Added in 7.20.0)
.IP CURL_RTSPREQ_TEARDOWN
This command terminates an RTSP session. Simply closing a connection does not
terminate the RTSP session since it is valid to control an RTSP session over
different connections. (Added in 7.20.0)
.IP CURL_RTSPREQ_GET_PARAMETER
Retrieve a parameter from the server. By default, libcurl will automatically
include a \fIContent-Type: text/parameters\fP header on all non-empty requests
unless a custom one is set. GET_PARAMETER acts just like a HTTP PUT or POST
(see \fICURL_RTSPREQ_SET_PARAMETER\fP).
Applications wishing to send a heartbeat message (e.g. in the presence of a
server-specified timeout) should send use an empty GET_PARAMETER request.
(Added in 7.20.0)
.IP CURL_RTSPREQ_SET_PARAMETER
Set a parameter on the server. By default, libcurl will automatically include
a \fIContent-Type: text/parameters\fP header unless a custom one is set. The
interaction with SET_PARAMTER is much like a HTTP PUT or POST. An application
may either use \fICURLOPT_UPLOAD\fP with \fICURLOPT_READDATA\fP like a HTTP
PUT, or it may use \fICURLOPT_POSTFIELDS\fP like a HTTP POST. No chunked
transfers are allowed, so the application must set the
\fICURLOPT_INFILESIZE\fP in the former and \fICURLOPT_POSTFIELDSIZE\fP in the
latter. Also, there is no use of multi-part POSTs within RTSP. (Added in
7.20.0)
.IP CURL_RTSPREQ_RECORD
Used to tell the server to record a session. Use the \fICURLOPT_RANGE\fP
option to modify the record time. (Added in 7.20.0)
.IP CURL_RTSPREQ_RECEIVE
This is a special request because it does not send any data to the server. The
application may call this function in order to receive interleaved RTP
data. It will return after processing one read buffer of data in order to give
the application a chance to run. (Added in 7.20.0)
.RE
.IP CURLOPT_RTSP_SESSION_ID
Pass a char * as a parameter to set the value of the current RTSP Session ID
for the handle. Useful for resuming an in-progress session. Once this value is
set to any non-NULL value, libcurl will return \fICURLE_RTSP_SESSION_ERROR\fP
if ID received from the server does not match. If unset (or set to NULL),
libcurl will automatically set the ID the first time the server sets it in a
response. (Added in 7.20.0)
.IP CURLOPT_RTSP_STREAM_URI
Set the stream URI to operate on by passing a char * . For example, a single
session may be controlling \fIrtsp://foo/twister/audio\fP and
\fIrtsp://foo/twister/video\fP and the application can switch to the
appropriate stream using this option. If unset, libcurl will default to
operating on generic server options by passing '*' in the place of the RTSP
Stream URI. This option is distinct from \fICURLOPT_URL\fP. When working with
RTSP, the \fICURLOPT_STREAM_URI\fP indicates what URL to send to the server in
the request header while the \fICURLOPT_URL\fP indicates where to make the
connection to. (e.g. the \fICURLOPT_URL\fP for the above examples might be
set to \fIrtsp://foo/twister\fP (Added in 7.20.0)
.IP CURLOPT_RTSP_TRANSPORT
Pass a char * to tell libcurl what to pass for the Transport: header for this
RTSP session. This is mainly a convenience method to avoid needing to set a
custom Transport: header for every SETUP request. The application must set a
Transport: header before issuing a SETUP request. (Added in 7.20.0)
.IP CURLOPT_RTSP_HEADER
This option is simply an alias for \fICURLOPT_HTTP_HEADER\fP. Use this to
replace the standard headers that RTSP and HTTP share. It is also valid to use
the shortcuts such as \fICURLOPT_USERAGENT\fP. (Added in 7.20.0)
.IP CURLOPT_RTSP_CLIENT_CSEQ
Manually set the the CSEQ number to issue for the next RTSP request. Useful if
the application is resuming a previously broken connection. The CSEQ will
increment from this new number henceforth. (Added in 7.20.0)
.IP CURLOPT_RTSP_SERVER_CSEQ
Manually set the CSEQ number to expect for the next RTSP Server->Client
request. At the moment, this feature (listening for Server requests) is
unimplemented. (Added in 7.20.0)
.SH PROTOCOL OPTIONS
.IP CURLOPT_TRANSFERTEXT
A parameter set to 1 tells the library to use ASCII mode for FTP transfers,
instead of the default binary transfer. For win32 systems it does not set the
stdout to binary mode. This option can be usable when transferring text data
between systems with different views on certain characters, such as newlines
or similar.
libcurl does not do a complete ASCII conversion when doing ASCII transfers
over FTP. This is a known limitation/flaw that nobody has rectified. libcurl
simply sets the mode to ASCII and performs a standard transfer.
.IP CURLOPT_PROXY_TRANSFER_MODE
Pass a long. If the value is set to 1 (one), it tells libcurl to set the
transfer mode (binary or ASCII) for FTP transfers done via a HTTP proxy, by
appending ;type=a or ;type=i to the URL. Without this setting, or it being set
to 0 (zero, the default), \fICURLOPT_TRANSFERTEXT\fP has no effect when doing
FTP via a proxy. Beware that not all proxies support this feature. (Added in
7.18.0)
.IP CURLOPT_CRLF
Pass a long. If the value is set to 1 (one), libcurl converts Unix newlines to
CRLF newlines on transfers. Disable this option again by setting the value to
0 (zero).
.IP CURLOPT_RANGE
Pass a char * as parameter, which should contain the specified range you
want. It should be in the format "X-Y", where X or Y may be left out. HTTP
transfers also support several intervals, separated with commas as in
\fI"X-Y,N-M"\fP. Using this kind of multiple intervals will cause the HTTP
server to send the response document in pieces (using standard MIME separation
techniques). For RTSP, the formatting of a range should follow RFC2326
Section 12.29. For RTSP, byte ranges are \fBnot\fP permitted. Instead, ranges
should be given in npt, utc, or smpte formats.
Pass a NULL to this option to disable the use of ranges.
Ranges work on HTTP, FTP, FILE (since 7.18.0), and RTSP (since 7.20.0)
transfers only.
.IP CURLOPT_RESUME_FROM
Pass a long as parameter. It contains the offset in number of bytes that you
want the transfer to start from. Set this option to 0 to make the transfer
start from the beginning (effectively disabling resume). For FTP, set this
option to -1 to make the transfer start from the end of the target file
(useful to continue an interrupted upload).
When doing uploads with FTP, the resume position is where in the local/source
file libcurl should try to resume the upload from and it will then append the
source file to the remote target file.
.IP CURLOPT_RESUME_FROM_LARGE
Pass a curl_off_t as parameter. It contains the offset in number of bytes that
you want the transfer to start from. (Added in 7.11.0)
.IP CURLOPT_CUSTOMREQUEST
Pass a pointer to a zero terminated string as parameter.
When you change the request method by setting \fBCURLOPT_CUSTOMREQUEST\fP to
something, you don't actually change how libcurl behaves or acts in regards
to the particular request method, it will only change the actual string sent
in the request.
Restore to the internal default by setting this to NULL.
This option can be used to specify the request:
.B HTTP
Instead of GET or HEAD when performing HTTP based requests. This is
particularly useful, for example, for performing a HTTP DELETE request.
For example:
When you tell libcurl to do a HEAD request, but then specify a GET though a
custom request libcurl will still act as if it sent a HEAD. To switch to a
proper HEAD use \fICURLOPT_NOBODY\fP, to switch to a proper POST use
\fICURLOPT_POST\fP or \fICURLOPT_POSTFIELDS\fP and to switch to a proper GET
use CURLOPT_HTTPGET.
Please don't perform this at will, on HTTP based requests, by making sure
your server supports the command you are sending first.
Many people have wrongly used this option to replace the entire request with
their own, including multiple headers and POST contents. While that might
work in many cases, it will cause libcurl to send invalid requests and it
could possibly confuse the remote server badly. Use \fICURLOPT_POST\fP and
\fICURLOPT_POSTFIELDS\fP to set POST data. Use \fICURLOPT_HTTPHEADER\fP to
replace or extend the set of headers sent by libcurl. Use
\fICURLOPT_HTTP_VERSION\fP to change HTTP version.
.B FTP
Instead of LIST and NLST when performing FTP directory listings.
.B IMAP
Instead of LIST when issuing IMAP based requests. (Added in 7.30.0)
.B POP3
Instead of LIST and RETR when issuing POP3 based requests. (Added in 7.26.0)
For example:
When you tell libcurl to use a custom request it will behave like a LIST or
RETR command was sent where it expects data to be returned by the server. As
such \fICURLOPT_NOBODY\fP should be used when specifying commands such as
DELE and NOOP for example.
.B SMTP
Instead of a HELP or VRFY when issuing SMTP based requests. (Added in 7.34.0)
For example:
Normally a multiline response is returned which can be used, in conjuection with
\fICURLOPT_MAIL_RCPT\fP, to specify an EXPN request. If the \fICURLOPT_NOBODY\fP
option is specified then the request can be used to issue NOOP and RSET
commands.
.IP CURLOPT_FILETIME
Pass a long. If it is 1, libcurl will attempt to get the modification date of
the remote document in this operation. This requires that the remote server
sends the time or replies to a time querying command. The
\fIcurl_easy_getinfo(3)\fP function with the \fICURLINFO_FILETIME\fP argument
can be used after a transfer to extract the received time (if any).
.IP CURLOPT_NOBODY
A parameter set to 1 tells the library to not include the body-part in the
output. This is only relevant for protocols that have separate header and
body parts. On HTTP(S) servers, this will make libcurl do a HEAD request.
To change request to GET, you should use \fICURLOPT_HTTPGET\fP. Change
request to POST with \fICURLOPT_POST\fP etc.
.IP CURLOPT_INFILESIZE
When uploading a file to a remote site, this option should be used to tell
libcurl what the expected size of the infile is. This value should be passed
as a long. See also \fICURLOPT_INFILESIZE_LARGE\fP.
For uploading using SCP, this option or \fICURLOPT_INFILESIZE_LARGE\fP is
mandatory.
To "unset" this value again, set it to -1.
When sending emails using SMTP, this command can be used to specify the
optional SIZE parameter for the MAIL FROM command. (Added in 7.23.0)
This option does not limit how much data libcurl will actually send, as that
is controlled entirely by what the read callback returns.
.IP CURLOPT_INFILESIZE_LARGE
When uploading a file to a remote site, this option should be used to tell
libcurl what the expected size of the infile is. This value should be passed
as a curl_off_t. (Added in 7.11.0)
For uploading using SCP, this option or \fICURLOPT_INFILESIZE\fP is mandatory.
To "unset" this value again, set it to -1.
When sending emails using SMTP, this command can be used to specify the
optional SIZE parameter for the MAIL FROM command. (Added in 7.23.0)
This option does not limit how much data libcurl will actually send, as that
is controlled entirely by what the read callback returns.
.IP CURLOPT_UPLOAD
A parameter set to 1 tells the library to prepare for an upload. The
\fICURLOPT_READDATA\fP and \fICURLOPT_INFILESIZE\fP or
\fICURLOPT_INFILESIZE_LARGE\fP options are also interesting for uploads. If
the protocol is HTTP, uploading means using the PUT request unless you tell
libcurl otherwise.
Using PUT with HTTP 1.1 implies the use of a "Expect: 100-continue" header.
You can disable this header with \fICURLOPT_HTTPHEADER\fP as usual.
If you use PUT to a HTTP 1.1 server, you can upload data without knowing the
size before starting the transfer if you use chunked encoding. You enable this
by adding a header like "Transfer-Encoding: chunked" with
\fICURLOPT_HTTPHEADER\fP. With HTTP 1.0 or without chunked transfer, you must
specify the size.
.IP CURLOPT_MAXFILESIZE
Pass a long as parameter. This allows you to specify the maximum size (in
bytes) of a file to download. If the file requested is larger than this value,
the transfer will not start and CURLE_FILESIZE_EXCEEDED will be returned.
The file size is not always known prior to download, and for such files this
option has no effect even if the file transfer ends up being larger than this
given limit. This concerns both FTP and HTTP transfers.
.IP CURLOPT_MAXFILESIZE_LARGE
Pass a curl_off_t as parameter. This allows you to specify the maximum size
(in bytes) of a file to download. If the file requested is larger than this
value, the transfer will not start and \fICURLE_FILESIZE_EXCEEDED\fP will be
returned. (Added in 7.11.0)
The file size is not always known prior to download, and for such files this
option has no effect even if the file transfer ends up being larger than this
given limit. This concerns both FTP and HTTP transfers.
.IP CURLOPT_TIMECONDITION
Pass a long as parameter. This defines how the \fICURLOPT_TIMEVALUE\fP time
value is treated. You can set this parameter to \fICURL_TIMECOND_IFMODSINCE\fP
or \fICURL_TIMECOND_IFUNMODSINCE\fP. This feature applies to HTTP, FTP, RTSP,
and FILE.
The last modification time of a file is not always known and in such instances
this feature will have no effect even if the given time condition would not
have been met. \fIcurl_easy_getinfo(3)\fP with the
\fICURLINFO_CONDITION_UNMET\fP option can be used after a transfer to learn if
a zero-byte successful "transfer" was due to this condition not matching.
.IP CURLOPT_TIMEVALUE
Pass a long as parameter. This should be the time in seconds since 1 Jan 1970,
and the time will be used in a condition as specified with
\fICURLOPT_TIMECONDITION\fP.
.SH CONNECTION OPTIONS
.IP CURLOPT_TIMEOUT
Pass a long as parameter containing the maximum time in seconds that you allow
the libcurl transfer operation to take. Normally, name lookups can take a
considerable time and limiting operations to less than a few minutes risk
aborting perfectly normal operations. This option will cause curl to use the
SIGALRM to enable time-outing system calls.
In unix-like systems, this might cause signals to be used unless
\fICURLOPT_NOSIGNAL\fP is set.
Default timeout is 0 (zero) which means it never times out.
.IP CURLOPT_TIMEOUT_MS
An alternative to \fICURLOPT_TIMEOUT\fP but takes number of milliseconds
instead. If libcurl is built to use the standard system name resolver, that
portion of the transfer will still use full-second resolution for timeouts
with a minimum timeout allowed of one second.
If both \fICURLOPT_TIMEOUT\fP and \fICURLOPT_TIMEOUT_MS\fP are set, the value
set last will be used.
(Added in 7.16.2)
.IP CURLOPT_LOW_SPEED_LIMIT
Pass a long as parameter. It contains the transfer speed in bytes per second
that the transfer should be below during \fICURLOPT_LOW_SPEED_TIME\fP seconds
for the library to consider it too slow and abort.
.IP CURLOPT_LOW_SPEED_TIME
Pass a long as parameter. It contains the time in seconds that the transfer
should be below the \fICURLOPT_LOW_SPEED_LIMIT\fP for the library to consider
it too slow and abort.
.IP CURLOPT_MAX_SEND_SPEED_LARGE
Pass a curl_off_t as parameter. If an upload exceeds this speed (counted in
bytes per second) on cumulative average during the transfer, the transfer will
pause to keep the average rate less than or equal to the parameter value.
Defaults to unlimited speed.
This option doesn't affect transfer speeds done with FILE:// URLs. (Added in
7.15.5)
.IP CURLOPT_MAX_RECV_SPEED_LARGE
Pass a curl_off_t as parameter. If a download exceeds this speed (counted in
bytes per second) on cumulative average during the transfer, the transfer will
pause to keep the average rate less than or equal to the parameter
value. Defaults to unlimited speed.
This option doesn't affect transfer speeds done with FILE:// URLs. (Added in
7.15.5)
.IP CURLOPT_MAXCONNECTS
Pass a long. The set number will be the persistent connection cache size. The
set amount will be the maximum amount of simultaneously open connections that
libcurl may cache in this easy handle. Default is 5, and there isn't much
point in changing this value unless you are perfectly aware of how this works
and changes libcurl's behaviour. This concerns connections using any of the
protocols that support persistent connections.
When reaching the maximum limit, curl closes the oldest one in the cache to
prevent increasing the number of open connections.
If you already have performed transfers with this curl handle, setting a
smaller MAXCONNECTS than before may cause open connections to get closed
unnecessarily.
If you add this easy handle to a multi handle, this setting is not
acknowledged, and you must instead use \fIcurl_multi_setopt(3)\fP and the
\fICURLMOPT_MAXCONNECTS\fP option.
.IP CURLOPT_CLOSEPOLICY
(Obsolete) This option does nothing.
.IP CURLOPT_FRESH_CONNECT
Pass a long. Set to 1 to make the next transfer use a new (fresh) connection
by force. If the connection cache is full before this connection, one of the
existing connections will be closed as according to the selected or default
policy. This option should be used with caution and only if you understand
what it does. Set this to 0 to have libcurl attempt re-using an existing
connection (default behavior).
.IP CURLOPT_FORBID_REUSE
Pass a long. Set to 1 to make the next transfer explicitly close the
connection when done. Normally, libcurl keeps all connections alive when done
with one transfer in case a succeeding one follows that can re-use them.
This option should be used with caution and only if you understand what it
does. Set to 0 to have libcurl keep the connection open for possible later
re-use (default behavior).
.IP CURLOPT_CONNECTTIMEOUT
Pass a long. It should contain the maximum time in seconds that you allow the
connection to the server to take. This only limits the connection phase, once
it has connected, this option is of no more use. Set to zero to switch to the
default built-in connection timeout - 300 seconds. See also the
\fICURLOPT_TIMEOUT\fP option.
In unix-like systems, this might cause signals to be used unless
\fICURLOPT_NOSIGNAL\fP is set.
.IP CURLOPT_CONNECTTIMEOUT_MS
Like \fICURLOPT_CONNECTTIMEOUT\fP but takes the number of milliseconds
instead. If libcurl is built to use the standard system name resolver,
that portion of the connect will still use full-second resolution for
timeouts with a minimum timeout allowed of one second.
(Added in 7.16.2)
.IP CURLOPT_IPRESOLVE
Allows an application to select what kind of IP addresses to use when
resolving host names. This is only interesting when using host names that
resolve addresses using more than one version of IP. The allowed values are:
.RS
.IP CURL_IPRESOLVE_WHATEVER
Default, resolves addresses to all IP versions that your system allows.
.IP CURL_IPRESOLVE_V4
Resolve to IPv4 addresses.
.IP CURL_IPRESOLVE_V6
Resolve to IPv6 addresses.
.RE
.IP CURLOPT_CONNECT_ONLY
Pass a long. If the parameter equals 1, it tells the library to perform all
the required proxy authentication and connection setup, but no data transfer.
This option is implemented for HTTP, SMTP and POP3.
The option can be used to simply test a connection to a server, but is more
useful when used with the \fICURLINFO_LASTSOCKET\fP option to
\fIcurl_easy_getinfo(3)\fP as the library can set up the connection and then
the application can obtain the most recently used socket for special data
transfers. (Added in 7.15.2)
.IP CURLOPT_USE_SSL
Pass a long using one of the values from below, to make libcurl use your
desired level of SSL for the transfer. (Added in 7.11.0)
This is for enabling SSL/TLS when you use FTP, SMTP, POP3, IMAP etc.
(This option was known as CURLOPT_FTP_SSL up to 7.16.4, and the constants
were known as CURLFTPSSL_*)
.RS
.IP CURLUSESSL_NONE
Don't attempt to use SSL.
.IP CURLUSESSL_TRY
Try using SSL, proceed as normal otherwise.
.IP CURLUSESSL_CONTROL
Require SSL for the control connection or fail with \fICURLE_USE_SSL_FAILED\fP.
.IP CURLUSESSL_ALL
Require SSL for all communication or fail with \fICURLE_USE_SSL_FAILED\fP.
.RE
.IP CURLOPT_RESOLVE
Pass a pointer to a linked list of strings with host name resolve information
to use for requests with this handle. The linked list should be a fully valid
list of \fBstruct curl_slist\fP structs properly filled in. Use
\fIcurl_slist_append(3)\fP to create the list and \fIcurl_slist_free_all(3)\fP
to clean up an entire list.
Each single name resolve string should be written using the format
HOST:PORT:ADDRESS where HOST is the name libcurl will try to resolve, PORT is
the port number of the service where libcurl wants to connect to the HOST and
ADDRESS is the numerical IP address. If libcurl is built to support IPv6,
ADDRESS can of course be either IPv4 or IPv6 style addressing.
This option effectively pre-populates the DNS cache with entries for the
host+port pair so redirects and everything that operations against the
HOST+PORT will instead use your provided ADDRESS. Addresses to set with
\fICURL_RESOLVE\fP will not time-out from the DNS cache like ordindary
entries.
You can remove names from the DNS cache again, to stop providing these fake
resolves, by including a string in the linked list that uses the format
\&"-HOST:PORT". The host name must be prefixed with a dash, and the host name
and port number must exactly match what was already added previously.
(Added in 7.21.3)
.IP CURLOPT_DNS_SERVERS
Set the list of DNS servers to be used instead of the system default.
The format of the dns servers option is:
host[:port][,host[:port]]...
For example:
192.168.1.100,192.168.1.101,3.4.5.6
This option requires that libcurl was built with a resolver backend that
supports this operation. The c-ares backend is the only such one.
(Added in 7.24.0)
.IP CURLOPT_DNS_INTERFACE
Pass a char * as parameter. Set the name of the network interface that
the DNS resolver should bind to. This must be an interface name (not an
address). Set this option to NULL to use the default setting (don't
bind to a specific interface).
This option requires that libcurl was built with a resolver backend that
supports this operation. The c-ares backend is the only such one.
(Added in 7.33.0)
.IP CURLOPT_DNS_LOCAL_IP4
Set the local IPv4 address that the resolver should bind to. The argument
should be of type char * and contain a single IPv4 address as a string.
Set this option to NULL to use the default setting (don't
bind to a specific IP address).
This option requires that libcurl was built with a resolver backend that
supports this operation. The c-ares backend is the only such one.
(Added in 7.33.0)
.IP CURLOPT_DNS_LOCAL_IP6
Set the local IPv6 address that the resolver should bind to. The argument
should be of type char * and contain a single IPv6 address as a string.
Set this option to NULL to use the default setting (don't
bind to a specific IP address).
This option requires that libcurl was built with a resolver backend that
supports this operation. The c-ares backend is the only such one.
(Added in 7.33.0)
.IP CURLOPT_ACCEPTTIMEOUT_MS
Pass a long telling libcurl the maximum number of milliseconds to wait for a
server to connect back to libcurl when an active FTP connection is used. If no
timeout is set, the internal default of 60000 will be used. (Added in 7.24.0)
.SH SSL and SECURITY OPTIONS
.IP CURLOPT_SSLCERT
Pass a pointer to a zero terminated string as parameter. The string should be
the file name of your certificate. The default format is "P12" on Secure
Transport and "PEM" on other engines, and can be changed with
\fICURLOPT_SSLCERTTYPE\fP.
With NSS or Secure Transport, this can also be the nickname of the certificate
you wish to authenticate with as it is named in the security database. If you
want to use a file from the current directory, please precede it with "./"
prefix, in order to avoid confusion with a nickname.
.IP CURLOPT_SSLCERTTYPE
Pass a pointer to a zero terminated string as parameter. The string should be
the format of your certificate. Supported formats are "PEM" and "DER", except
with Secure Transport. OpenSSL (versions 0.9.3 and later) and Secure Transport
(on iOS 5 or later, or OS X 10.7 or later) also support "P12" for
PKCS#12-encoded files. (Added in 7.9.3)
.IP CURLOPT_SSLKEY
Pass a pointer to a zero terminated string as parameter. The string should be
the file name of your private key. The default format is "PEM" and can be
changed with \fICURLOPT_SSLKEYTYPE\fP.
(iOS and Mac OS X only) This option is ignored if curl was built against Secure
Transport. Secure Transport expects the private key to be already present in
the keychain or PKCS#12 file containing the certificate.
.IP CURLOPT_SSLKEYTYPE
Pass a pointer to a zero terminated string as parameter. The string should be
the format of your private key. Supported formats are "PEM", "DER" and "ENG".
The format "ENG" enables you to load the private key from a crypto engine. In
this case \fICURLOPT_SSLKEY\fP is used as an identifier passed to the
engine. You have to set the crypto engine with \fICURLOPT_SSLENGINE\fP.
\&"DER" format key file currently does not work because of a bug in OpenSSL.
.IP CURLOPT_KEYPASSWD
Pass a pointer to a zero terminated string as parameter. It will be used as
the password required to use the \fICURLOPT_SSLKEY\fP or
\fICURLOPT_SSH_PRIVATE_KEYFILE\fP private key.
You never needed a pass phrase to load a certificate but you need one to
load your private key.
(This option was known as CURLOPT_SSLKEYPASSWD up to 7.16.4 and
CURLOPT_SSLCERTPASSWD up to 7.9.2)
.IP CURLOPT_SSLENGINE
Pass a pointer to a zero terminated string as parameter. It will be used as
the identifier for the crypto engine you want to use for your private
key.
If the crypto device cannot be loaded, \fICURLE_SSL_ENGINE_NOTFOUND\fP is
returned.
.IP CURLOPT_SSLENGINE_DEFAULT
Sets the actual crypto engine as the default for (asymmetric) crypto
operations.
If the crypto device cannot be set, \fICURLE_SSL_ENGINE_SETFAILED\fP is
returned.
Even though this option doesn't need any parameter, in some configurations
\fIcurl_easy_setopt\fP might be defined as a macro taking exactly three
arguments. Therefore, it's recommended to pass 1 as parameter to this option.
.IP CURLOPT_SSLVERSION
Pass a long as parameter to control what version of SSL/TLS to attempt to use.
(Added in 7.9.2)
The available options are:
.RS
.IP CURL_SSLVERSION_DEFAULT
The default action. This will attempt to figure out the remote SSL protocol
version, i.e. either SSLv3 or TLSv1 (but not SSLv2, which became disabled
by default with 7.18.1).
.IP CURL_SSLVERSION_TLSv1
Force TLSv1.x
.IP CURL_SSLVERSION_SSLv2
Force SSLv2
.IP CURL_SSLVERSION_SSLv3
Force SSLv3
.IP CURL_SSLVERSION_TLSv1_0
Force TLSv1.0 (Added in 7.34.0)
.IP CURL_SSLVERSION_TLSv1_1
Force TLSv1.1 (Added in 7.34.0)
.IP CURL_SSLVERSION_TLSv1_2
Force TLSv1.2 (Added in 7.34.0)
.RE
.IP CURLOPT_SSL_VERIFYPEER
Pass a long as parameter. By default, curl assumes a value of 1.
This option determines whether curl verifies the authenticity of the peer's
certificate. A value of 1 means curl verifies; 0 (zero) means it doesn't.
When negotiating a SSL connection, the server sends a certificate indicating
its identity. Curl verifies whether the certificate is authentic, i.e. that
you can trust that the server is who the certificate says it is. This trust
is based on a chain of digital signatures, rooted in certification authority
(CA) certificates you supply. curl uses a default bundle of CA certificates
(the path for that is determined at build time) and you can specify alternate
certificates with the \fICURLOPT_CAINFO\fP option or the \fICURLOPT_CAPATH\fP
option.
When \fICURLOPT_SSL_VERIFYPEER\fP is nonzero, and the verification fails to
prove that the certificate is authentic, the connection fails. When the
option is zero, the peer certificate verification succeeds regardless.
Authenticating the certificate is not by itself very useful. You typically
want to ensure that the server, as authentically identified by its
certificate, is the server you mean to be talking to. Use
\fICURLOPT_SSL_VERIFYHOST\fP to control that. The check that the host name in
the certificate is valid for the host name you're connecting to is done
independently of the \fICURLOPT_SSL_VERIFYPEER\fP option.
.IP CURLOPT_CAINFO
Pass a char * to a zero terminated string naming a file holding one or more
certificates to verify the peer with. This makes sense only when used in
combination with the \fICURLOPT_SSL_VERIFYPEER\fP option. If
\fICURLOPT_SSL_VERIFYPEER\fP is zero, \fICURLOPT_CAINFO\fP need not
even indicate an accessible file.
This option is by default set to the system path where libcurl's cacert bundle
is assumed to be stored, as established at build time.
If curl is built against the NSS SSL library, the NSS PEM PKCS#11 module
(libnsspem.so) needs to be available for this option to work properly.
.IP CURLOPT_ISSUERCERT
Pass a char * to a zero terminated string naming a file holding a CA
certificate in PEM format. If the option is set, an additional check against
the peer certificate is performed to verify the issuer is indeed the one
associated with the certificate provided by the option. This additional check
is useful in multi-level PKI where one needs to enforce that the peer
certificate is from a specific branch of the tree.
This option makes sense only when used in combination with the
\fICURLOPT_SSL_VERIFYPEER\fP option. Otherwise, the result of the check is not
considered as failure.
A specific error code (CURLE_SSL_ISSUER_ERROR) is defined with the option,
which is returned if the setup of the SSL/TLS session has failed due to a
mismatch with the issuer of peer certificate (\fICURLOPT_SSL_VERIFYPEER\fP has
to be set too for the check to fail). (Added in 7.19.0)
.IP CURLOPT_CAPATH
Pass a char * to a zero terminated string naming a directory holding multiple
CA certificates to verify the peer with. If libcurl is built against OpenSSL,
the certificate directory must be prepared using the openssl c_rehash utility.
This makes sense only when used in combination with the
\fICURLOPT_SSL_VERIFYPEER\fP option. If \fICURLOPT_SSL_VERIFYPEER\fP is zero,
\fICURLOPT_CAPATH\fP need not even indicate an accessible path. The
\fICURLOPT_CAPATH\fP function apparently does not work in Windows due to some
limitation in openssl. This option is OpenSSL-specific and does nothing if
libcurl is built to use GnuTLS. NSS-powered libcurl provides the option only
for backward compatibility.
.IP CURLOPT_CRLFILE
Pass a char * to a zero terminated string naming a file with the concatenation
of CRL (in PEM format) to use in the certificate validation that occurs during
the SSL exchange.
When curl is built to use NSS or GnuTLS, there is no way to influence the use
of CRL passed to help in the verification process. When libcurl is built with
OpenSSL support, X509_V_FLAG_CRL_CHECK and X509_V_FLAG_CRL_CHECK_ALL are both
set, requiring CRL check against all the elements of the certificate chain if
a CRL file is passed.
This option makes sense only when used in combination with the
\fICURLOPT_SSL_VERIFYPEER\fP option.
A specific error code (CURLE_SSL_CRL_BADFILE) is defined with the option. It
is returned when the SSL exchange fails because the CRL file cannot be loaded.
A failure in certificate verification due to a revocation information found in
the CRL does not trigger this specific error. (Added in 7.19.0)
.IP CURLOPT_SSL_VERIFYHOST
Pass a long as parameter.
This option determines whether libcurl verifies that the server cert is for
the server it is known as.
When negotiating a SSL connection, the server sends a certificate indicating
its identity.
When \fICURLOPT_SSL_VERIFYHOST\fP is 2, that certificate must indicate that
the server is the server to which you meant to connect, or the connection
fails.
Curl considers the server the intended one when the Common Name field or a
Subject Alternate Name field in the certificate matches the host name in the
URL to which you told Curl to connect.
When the value is 1, \fIcurl_easy_setopt\fP will return an error and the option
value will not be changed. It was previously (in 7.28.0 and earlier) a debug
option of some sorts, but it is no longer supported due to frequently leading
to programmer mistakes.
When the value is 0, the connection succeeds regardless of the names in the
certificate.
The default value for this option is 2.
This option controls checking the server's certificate's claimed identity.
The server could be lying. To control lying, see
\fICURLOPT_SSL_VERIFYPEER\fP. If libcurl is built against NSS and
\fICURLOPT_SSL_VERIFYPEER\fP is zero, \fICURLOPT_SSL_VERIFYHOST\fP is also set
to zero and cannot be overridden.
.IP CURLOPT_CERTINFO
Pass a long set to 1 to enable libcurl's certificate chain info gatherer. With
this enabled, libcurl (if built with OpenSSL, NSS, GSKit or QsoSSL) will
extract lots of information
and data about the certificates in the certificate chain used in the SSL
connection. This data may then be retrieved after a transfer using
\fIcurl_easy_getinfo(3)\fP and its option \fICURLINFO_CERTINFO\fP. (Added in
7.19.1)
.IP CURLOPT_RANDOM_FILE
Pass a char * to a zero terminated file name. The file will be used to read
from to seed the random engine for SSL. The more random the specified file is,
the more secure the SSL connection will become.
.IP CURLOPT_EGDSOCKET
Pass a char * to the zero terminated path name to the Entropy Gathering Daemon
socket. It will be used to seed the random engine for SSL.
.IP CURLOPT_SSL_CIPHER_LIST
Pass a char *, pointing to a zero terminated string holding the list of
ciphers to use for the SSL connection. The list must be syntactically correct,
it consists of one or more cipher strings separated by colons. Commas or
spaces are also acceptable separators but colons are normally used, \&!, \&-
and \&+ can be used as operators.
For OpenSSL and GnuTLS valid examples of cipher lists include 'RC4-SHA',
\'SHA1+DES\', 'TLSv1' and 'DEFAULT'. The default list is normally set when you
compile OpenSSL.
You'll find more details about cipher lists on this URL:
\fIhttp://www.openssl.org/docs/apps/ciphers.html\fP
For NSS, valid examples of cipher lists include 'rsa_rc4_128_md5',
\'rsa_aes_128_sha\', etc. With NSS you don't add/remove ciphers. If one uses
this option then all known ciphers are disabled and only those passed in
are enabled.
You'll find more details about the NSS cipher lists on this URL:
\fIhttp://git.fedorahosted.org/cgit/mod_nss.git/plain/docs/mod_nss.html#Directives\fP
.IP CURLOPT_SSL_SESSIONID_CACHE
Pass a long set to 0 to disable libcurl's use of SSL session-ID caching. Set
this to 1 to enable it. By default all transfers are done using the
cache. While nothing ever should get hurt by attempting to reuse SSL
session-IDs, there seem to be broken SSL implementations in the wild that may
require you to disable this in order for you to succeed. (Added in 7.16.0)
.IP CURLOPT_SSL_OPTIONS
Pass a long with a bitmask to tell libcurl about specific SSL behaviors.
CURLSSLOPT_ALLOW_BEAST is the only supported bit and by setting this the user
will tell libcurl to not attempt to use any workarounds for a security flaw
in the SSL3 and TLS1.0 protocols. If this option isn't used or this bit is
set to 0, the SSL layer libcurl uses may use a work-around for this flaw
although it might cause interoperability problems with some (older) SSL
implementations. WARNING: avoiding this work-around loosens the security, and
by setting this option to 1 you ask for exactly that. (Added in 7.25.0)
.IP CURLOPT_KRBLEVEL
Pass a char * as parameter. Set the kerberos security level for FTP; this also
enables kerberos awareness. This is a string, \&'clear', \&'safe',
\&'confidential' or \&'private'. If the string is set but doesn't match one
of these, 'private' will be used. Set the string to NULL to disable kerberos
support for FTP.
(This option was known as CURLOPT_KRB4LEVEL up to 7.16.3)
.IP CURLOPT_GSSAPI_DELEGATION
Set the parameter to CURLGSSAPI_DELEGATION_FLAG to allow unconditional GSSAPI
credential delegation. The delegation is disabled by default since 7.21.7.
Set the parameter to CURLGSSAPI_DELEGATION_POLICY_FLAG to delegate only if
the OK-AS-DELEGATE flag is set in the service ticket in case this feature is
supported by the GSSAPI implementation and the definition of
GSS_C_DELEG_POLICY_FLAG was available at compile-time.
(Added in 7.22.0)
.SH SSH OPTIONS
.IP CURLOPT_SSH_AUTH_TYPES
Pass a long set to a bitmask consisting of one or more of
CURLSSH_AUTH_PUBLICKEY, CURLSSH_AUTH_PASSWORD, CURLSSH_AUTH_HOST,
CURLSSH_AUTH_KEYBOARD and CURLSSH_AUTH_AGENT. Set CURLSSH_AUTH_ANY to let
libcurl pick a suitable one. Currently CURLSSH_AUTH_HOST has no effect. (Added
in 7.16.1) If CURLSSH_AUTH_AGENT is used, libcurl attempts to connect to
ssh-agent or pageant and let the agent attempt the authentication. (Added in
7.28.0)
.IP CURLOPT_SSH_HOST_PUBLIC_KEY_MD5
Pass a char * pointing to a string containing 32 hexadecimal digits. The
string should be the 128 bit MD5 checksum of the remote host's public key, and
libcurl will reject the connection to the host unless the md5sums match. This
option is only for SCP and SFTP transfers. (Added in 7.17.1)
.IP CURLOPT_SSH_PUBLIC_KEYFILE
Pass a char * pointing to a file name for your public key. If not used,
libcurl defaults to \fB$HOME/.ssh/id_dsa.pub\fP if the HOME environment
variable is set, and just "id_dsa.pub" in the current directory if HOME is not
set. (Added in 7.16.1)
If an empty string is passed, libcurl will pass no public key to libssh2
which then tries to compute it from the private key, this is known to work
when libssh2 1.4.0+ is linked against OpenSSL. (Added in 7.26.0)
.IP CURLOPT_SSH_PRIVATE_KEYFILE
Pass a char * pointing to a file name for your private key. If not used,
libcurl defaults to \fB$HOME/.ssh/id_dsa\fP if the HOME environment variable
is set, and just "id_dsa" in the current directory if HOME is not set. If the
file is password-protected, set the password with
\fICURLOPT_KEYPASSWD\fP. (Added in 7.16.1)
.IP CURLOPT_SSH_KNOWNHOSTS
Pass a pointer to a zero terminated string holding the file name of the
known_host file to use. The known_hosts file should use the OpenSSH file
format as supported by libssh2. If this file is specified, libcurl will only
accept connections with hosts that are known and present in that file, with a
matching public key. Use \fICURLOPT_SSH_KEYFUNCTION\fP to alter the default
behavior on host and key (mis)matching. (Added in 7.19.6)
.IP CURLOPT_SSH_KEYFUNCTION
Pass a pointer to a curl_sshkeycallback function. It gets called when the
known_host matching has been done, to allow the application to act and decide
for libcurl how to proceed. The callback will only be called if
\fICURLOPT_SSH_KNOWNHOSTS\fP is also set.
The curl_sshkeycallback function gets passed the CURL handle, the key from the
known_hosts file, the key from the remote site, info from libcurl on the
matching status and a custom pointer (set with \fICURLOPT_SSH_KEYDATA\fP). It
MUST return one of the following return codes to tell libcurl how to act:
.RS
.IP CURLKHSTAT_FINE_ADD_TO_FILE
The host+key is accepted and libcurl will append it to the known_hosts file
before continuing with the connection. This will also add the host+key combo
to the known_host pool kept in memory if it wasn't already present there. The
adding of data to the file is done by completely replacing the file with a new
copy, so the permissions of the file must allow this.
.IP CURLKHSTAT_FINE
The host+key is accepted libcurl will continue with the connection. This will
also add the host+key combo to the known_host pool kept in memory if it wasn't
already present there.
.IP CURLKHSTAT_REJECT
The host+key is rejected. libcurl will deny the connection to continue and it
will be closed.
.IP CURLKHSTAT_DEFER
The host+key is rejected, but the SSH connection is asked to be kept alive.
This feature could be used when the app wants to somehow return back and act
on the host+key situation and then retry without needing the overhead of
setting it up from scratch again.
.RE
(Added in 7.19.6)
.IP CURLOPT_SSH_KEYDATA
Pass a void * as parameter. This pointer will be passed along verbatim to the
callback set with \fICURLOPT_SSH_KEYFUNCTION\fP. (Added in 7.19.6)
.SH OTHER OPTIONS
.IP CURLOPT_PRIVATE
Pass a void * as parameter, pointing to data that should be associated with
this curl handle. The pointer can subsequently be retrieved using
\fIcurl_easy_getinfo(3)\fP with the CURLINFO_PRIVATE option. libcurl itself
does nothing with this data. (Added in 7.10.3)
.IP CURLOPT_SHARE
Pass a share handle as a parameter. The share handle must have been created by
a previous call to \fIcurl_share_init(3)\fP. Setting this option, will make
this curl handle use the data from the shared handle instead of keeping the
data to itself. This enables several curl handles to share data. If the curl
handles are used simultaneously in multiple threads, you \fBMUST\fP use the
locking methods in the share handle. See \fIcurl_share_setopt(3)\fP for
details.
If you add a share that is set to share cookies, your easy handle will use
that cookie cache and get the cookie engine enabled. If you unshare an object
that was using cookies (or change to another object that doesn't share
cookies), the easy handle will get its cookie engine disabled.
Data that the share object is not set to share will be dealt with the usual
way, as if no share was used.
.IP CURLOPT_NEW_FILE_PERMS
Pass a long as a parameter, containing the value of the permissions that will
be assigned to newly created files on the remote server. The default value is
\fI0644\fP, but any valid value can be used. The only protocols that can use
this are \fIsftp://\fP, \fIscp://\fP, and \fIfile://\fP. (Added in 7.16.4)
.IP CURLOPT_NEW_DIRECTORY_PERMS
Pass a long as a parameter, containing the value of the permissions that will
be assigned to newly created directories on the remote server. The default
value is \fI0755\fP, but any valid value can be used. The only protocols that
can use this are \fIsftp://\fP, \fIscp://\fP, and \fIfile://\fP.
(Added in 7.16.4)
.SH TELNET OPTIONS
.IP CURLOPT_TELNETOPTIONS
Provide a pointer to a curl_slist with variables to pass to the telnet
negotiations. The variables should be in the format . libcurl
supports the options 'TTYPE', 'XDISPLOC' and 'NEW_ENV'. See the TELNET
standard for details.
.SH RETURN VALUE
CURLE_OK (zero) means that the option was set properly, non-zero means an
error occurred as \fI\fP defines. See the \fIlibcurl-errors(3)\fP
man page for the full list with descriptions.
If you try to set an option that libcurl doesn't know about, perhaps because
the library is too old to support it or the option was removed in a recent
version, this function will return \fICURLE_FAILED_INIT\fP.
.SH "SEE ALSO"
.BR curl_easy_init "(3), " curl_easy_cleanup "(3), " curl_easy_reset "(3)"
curl-7.35.0/docs/libcurl/libcurl-multi.html 0000644 0001750 0001750 00000022241 12272124467 015542 0000000 0000000
libcurl-multi man page
NAME
libcurl-multi - how to use the multi interface
DESCRIPTION
This is an overview on how to use the libcurl multi interface in your C programs. There are specific man pages for each function mentioned in here. There's also the libcurl-tutorial(3) man page for a complete tutorial to programming with libcurl and the libcurl-easy(3) man page for an overview of the libcurl easy interface.
All functions in the multi interface are prefixed with curl_multi.
OBJECTIVES
The multi interface offers several abilities that the easy interface doesn't. They are mainly:
1. Enable a "pull" interface. The application that uses libcurl decides where and when to ask libcurl to get/send data.
2. Enable multiple simultaneous transfers in the same thread without making it complicated for the application.
3. Enable the application to wait for action on its own file descriptors and curl's file descriptors simultaneous easily.
ONE MULTI HANDLE MANY EASY HANDLES
To use the multi interface, you must first create a 'multi handle' with curl_multi_init(3). This handle is then used as input to all further curl_multi_* functions.
Each single transfer is built up with an easy handle. You must create them, and setup the appropriate options for each easy handle, as outlined in the libcurl(3) man page, using curl_easy_setopt(3).
When the easy handle is setup for a transfer, then instead of using curl_easy_perform(3) (as when using the easy interface for transfers), you should instead add the easy handle to the multi handle using curl_multi_add_handle(3). The multi handle is sometimes referred to as a ´multi stack´ because of the fact that it may hold a large amount of easy handles.
Should you change your mind, the easy handle is again removed from the multi stack using curl_multi_remove_handle(3). Once removed from the multi handle, you can again use other easy interface functions like curl_easy_perform(3) on the handle or whatever you think is necessary.
Adding the easy handle to the multi handle does not start the transfer. Remember that one of the main ideas with this interface is to let your application drive. You drive the transfers by invoking curl_multi_perform(3). libcurl will then transfer data if there is anything available to transfer. It'll use the callbacks and everything else you have setup in the individual easy handles. It'll transfer data on all current transfers in the multi stack that are ready to transfer anything. It may be all, it may be none.
Your application can acquire knowledge from libcurl when it would like to get invoked to transfer data, so that you don't have to busy-loop and call that curl_multi_perform(3) like crazy. curl_multi_fdset(3) offers an interface using which you can extract fd_sets from libcurl to use in select() or poll() calls in order to get to know when the transfers in the multi stack might need attention. This also makes it very easy for your program to wait for input on your own private file descriptors at the same time or perhaps timeout every now and then, should you want that.
curl_multi_perform(3) stores the number of still running transfers in one of its input arguments, and by reading that you can figure out when all the transfers in the multi handles are done. 'done' does not mean successful. One or more of the transfers may have failed. Tracking when this number changes, you know when one or more transfers are done.
To get information about completed transfers, to figure out success or not and similar, curl_multi_info_read(3) should be called. It can return a message about a current or previous transfer. Repeated invokes of the function get more messages until the message queue is empty. The information you receive there includes an easy handle pointer which you may use to identify which easy handle the information regards.
When a single transfer is completed, the easy handle is still left added to the multi stack. You need to first remove the easy handle with curl_multi_remove_handle(3) and then close it with curl_easy_cleanup(3), or possibly set new options to it and add it again with curl_multi_add_handle(3) to start another transfer.
When all transfers in the multi stack are done, cleanup the multi handle with curl_multi_cleanup(3). Be careful and please note that you MUST invoke separate curl_easy_cleanup(3) calls on every single easy handle to clean them up properly.
If you want to re-use an easy handle that was added to the multi handle for transfer, you must first remove it from the multi stack and then re-add it again (possibly after having altered some options at your own choice).
MULTI_SOCKET
curl_multi_socket_action(3) function offers a way for applications to not only avoid being forced to use select(), but it also offers a much more high-performance API that will make a significant difference for applications using large numbers of simultaneous connections.
curl_multi_socket_action(3) is then used instead of curl_multi_perform(3).
When using this API, you add easy handles to the multi handle just as with the normal multi interface. Then you also set two callbacks with the CURLMOPT_SOCKETFUNCTION and CURLMOPT_TIMERFUNCTION options to curl_multi_setopt(3).
The API is then designed to inform your application about which sockets libcurl is currently using and for what activities (read and/or write) on those sockets your application is expected to wait for.
Your application must then make sure to receive all sockets informed about in the CURLMOPT_SOCKETFUNCTION callback and make sure it reacts on the given activity on them. When a socket has the given activity, you call curl_multi_socket_action(3) specifying which socket and action there are.
The CURLMOPT_TIMERFUNCTION callback is called to set a timeout. When that timeout expires, your application should call the curl_multi_socket_action(3) function saying it was due to a timeout.
BLOCKING
A few areas in the code are still using blocking code, even when used from the multi interface. While we certainly want and intend for these to get fixed in the future, you should be aware of the following current restrictions:
- Name resolves unless the c-ares or threaded-resolver backends are used
- NSS SSL connections
- HTTP proxy CONNECT operations
- SOCKS proxy handshakes
- file:// transfers
- TELNET transfers
This HTML page was made with roffit.
curl-7.35.0/docs/libcurl/curl_getdate.html 0000644 0001750 0001750 00000011557 12272124467 015430 0000000 0000000
curl_getdate man page
NAME
curl_getdate - Convert a date string to number of seconds
SYNOPSIS
#include <curl/curl.h>
time_t curl_getdate(char * datestring , time_t *now );
DESCRIPTION
curl_getdate(3) returns the number of seconds since the Epoch, January 1st 1970 00:00:00 in the UTC time zone, for the date and time that the datestring parameter specifies. The now parameter is not used, pass a NULL there.
PARSING DATES AND TIMES
A "date" is a string containing several items separated by whitespace. The order of the items is immaterial. A date string may contain many flavors of items:
calendar date items Can be specified several ways. Month names can only be three-letter english abbreviations, numbers can be zero-prefixed and the year may use 2 or 4 digits. Examples: 06 Nov 1994, 06-Nov-94 and Nov-94 6.
time of the day items This string specifies the time on a given day. You must specify it with 6 digits with two colons: HH:MM:SS. To not include the time in a date string, will make the function assume 00:00:00. Example: 18:19:21.
time zone items Specifies international time zone. There are a few acronyms supported, but in general you should instead use the specific relative time compared to UTC. Supported formats include: -1200, MST, +0100.
day of the week items Specifies a day of the week. Days of the week may be spelled out in full (using english): `Sunday', `Monday', etc or they may be abbreviated to their first three letters. This is usually not info that adds anything.
pure numbers If a decimal number of the form YYYYMMDD appears, then YYYY is read as the year, MM as the month number and DD as the day of the month, for the specified calendar date.
EXAMPLES
Sun, 06 Nov 1994 08:49:37 GMT
Sunday, 06-Nov-94 08:49:37 GMT
Sun Nov 6 08:49:37 1994
06 Nov 1994 08:49:37 GMT
06-Nov-94 08:49:37 GMT
Nov 6 08:49:37 1994
06 Nov 1994 08:49:37
06-Nov-94 08:49:37
1994 Nov 6 08:49:37
GMT 08:49:37 06-Nov-94 Sunday
94 6 Nov 08:49:37
1994 Nov 6
06-Nov-94
Sun Nov 6 94
1994.Nov.6
Sun/Nov/6/94/GMT
Sun, 06 Nov 1994 08:49:37 CET
06 Nov 1994 08:49:37 EST
Sun, 12 Sep 2004 15:05:58 -0700
Sat, 11 Sep 2004 21:32:11 +0200
20040912 15:05:58 -0700
20040911 +0200
STANDARDS
This parser was written to handle date formats specified in RFC 822 (including the update in RFC 1123) using time zone name or time zone delta and RFC 850 (obsoleted by RFC 1036) and ANSI C's asctime() format. These formats are the only ones RFC 2616 says HTTP applications may use.
RETURN VALUE
This function returns -1 when it fails to parse the date string. Otherwise it returns the number of seconds as described.
If the year is larger than 2037 on systems with 32 bit time_t, this function will return 0x7fffffff (since that is the largest possible signed 32 bit number).
Having a 64 bit time_t is not a guarantee that dates beyond 03:14:07 UTC, January 19, 2038 will work fine. On systems with a 64 bit time_t but with a crippled mktime(), curl_getdate will return -1 in this case.
This HTML page was made with roffit.
curl-7.35.0/docs/libcurl/curl_slist_append.3 0000644 0001750 0001750 00000004170 12213173003 015650 0000000 0000000 .\" **************************************************************************
.\" * _ _ ____ _
.\" * Project ___| | | | _ \| |
.\" * / __| | | | |_) | |
.\" * | (__| |_| | _ <| |___
.\" * \___|\___/|_| \_\_____|
.\" *
.\" * Copyright (C) 1998 - 2011, Daniel Stenberg, , et al.
.\" *
.\" * This software is licensed as described in the file COPYING, which
.\" * you should have received as part of this distribution. The terms
.\" * are also available at http://curl.haxx.se/docs/copyright.html.
.\" *
.\" * You may opt to use, copy, modify, merge, publish, distribute and/or sell
.\" * copies of the Software, and permit persons to whom the Software is
.\" * furnished to do so, under the terms of the COPYING file.
.\" *
.\" * This software is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY
.\" * KIND, either express or implied.
.\" *
.\" **************************************************************************
.TH curl_slist_append 3 "19 Jun 2003" "libcurl 7.10.4" "libcurl Manual"
.SH NAME
curl_slist_append - add a string to an slist
.SH SYNOPSIS
.B #include
.sp
.BI "struct curl_slist *curl_slist_append(struct curl_slist *" list,
.BI "const char * "string ");"
.ad
.SH DESCRIPTION
curl_slist_append() appends a specified string to a linked list of
strings. The existing \fIlist\fP should be passed as the first argument while
the new list is returned from this function. The specified \fIstring\fP has
been appended when this function returns. curl_slist_append() copies the
string.
The list should be freed again (after usage) with
\fBcurl_slist_free_all(3)\fP.
.SH RETURN VALUE
A null pointer is returned if anything went wrong, otherwise the new list
pointer is returned.
.SH EXAMPLE
.nf
CURL handle;
struct curl_slist *slist=NULL;
slist = curl_slist_append(slist, "pragma:");
curl_easy_setopt(handle, CURLOPT_HTTPHEADER, slist);
curl_easy_perform(handle);
curl_slist_free_all(slist); /* free the list again */
.fi
.SH "SEE ALSO"
.BR curl_slist_free_all "(3), "
curl-7.35.0/docs/libcurl/curl_global_init.html 0000644 0001750 0001750 00000010162 12272124467 016265 0000000 0000000
curl_global_init man page
NAME
curl_global_init - Global libcurl initialisation
SYNOPSIS
#include <curl/curl.h>
CURLcode curl_global_init(long flags );
DESCRIPTION
This function sets up the program environment that libcurl needs. Think of it as an extension of the library loader.
This function must be called at least once within a program (a program is all the code that shares a memory space) before the program calls any other function in libcurl. The environment it sets up is constant for the life of the program and is the same for every program, so multiple calls have the same effect as one call.
The flags option is a bit pattern that tells libcurl exactly what features to init, as described below. Set the desired bits by ORing the values together. In normal operation, you must specify CURL_GLOBAL_ALL. Don't use any other value unless you are familiar with it and mean to control internal operations of libcurl.
This function is not thread safe. You must not call it when any other thread in the program (i.e. a thread sharing the same memory) is running. This doesn't just mean no other thread that is using libcurl. Because curl_global_init() calls functions of other libraries that are similarly thread unsafe, it could conflict with any other thread that uses these other libraries.
See the description in libcurl(3) of global environment requirements for details of how to use this function.
FLAGS
CURL_GLOBAL_ALL Initialize everything possible. This sets all known bits except CURL_GLOBAL_ACK_EINTR.
CURL_GLOBAL_SSL Initialize SSL
CURL_GLOBAL_WIN32 Initialize the Win32 socket libraries.
CURL_GLOBAL_NOTHING Initialise nothing extra. This sets no bit.
CURL_GLOBAL_DEFAULT A sensible default. It will init both SSL and Win32. Right now, this equals the functionality of the CURL_GLOBAL_ALL mask.
CURL_GLOBAL_ACK_EINTR When this flag is set, curl will acknowledge EINTR condition when connecting or when waiting for data. Otherwise, curl waits until full timeout elapses.
RETURN VALUE
If this function returns non-zero, something went wrong and you cannot use the other curl functions.
SEE ALSO
curl_global_init_mem (3) curl_global_cleanup (3) curl_easy_init (3) libcurl (3)
This HTML page was made with roffit.
curl-7.35.0/docs/libcurl/curl_easy_getinfo.pdf 0000644 0001750 0001750 00000041601 12272124470 016257 0000000 0000000 %PDF-1.4
%Çì¢
5 0 obj
<>
stream
xœ¥XÛnÛH}÷W4°¡«Ã滋< yã _´=ÀÀY4Õ¶8¡H…;žoØÞSÝMŠ’d“A€È ›ÝU§ªNêOÌæ‚ÙôÏüfëƒwW!{hlöpðé@¨—ÌüdköS‚=Hîô7‚… c—G1KÖBD<,y:¸±²®.neÚ<ß>È6/ï«–ûaŠüŽÞL¦ŽosÛó´ìÒ‚½¾|òŸä_S›;ûg8>Æñ<öÉ7`ÉÙuq4y‹ñVøÜ]X•,¬óÙ$ù}d¯csÏÙT8ôÚþ‚lÊäûÀ0×úÜÖiÖ2z^¯Ó6¯Jv_Wk–*cÙ*-—…TîØ5…aSðHÙ±øíâr¾8]hkbcZ¢,±þ’—YÑ-%û;íúŽþã«ÐrÇ#“·7ÖñõÕYVa;ÁÇãqä{à¢Eì-8dô÷éÅÉ%ë×ÄNhU‡ŒsÎ>Lþö£Èýólq|u:ON//vQÜÚ-¸ï†„¢u%?u²!œZY—å ÀÚ•¶œ5²ièéSÞ®ð4oØ}Wf´+‡ãÛŽ í ¨ý|µõ’¥5BÞˆ~•õÐeÙîëqÛõã>®Éž ßáN²”ÞO=ï"oH˜¢ ÜTÊ5ÖV}Q•‡øÝy˜Òš½}ñ¸ië ¤‚Ö90z˪zÕ²êî
É>Xi£1YVY7%“È3""eyªQ]Ê&«ó;IøÕ@·Æ7¨á8¨í—ÃýÕSùaÂ@¤ =Á½ oØx™¶½MË)lzÊ‹‚—ÿ…\"œ,Ͳª^æåCñÌõ,KKz_Ë"Ç‚nS•
A¸<ØÖa ë¬*ña~¯¡8¾n»ºlT®În/á“©/B*a뺑»éÁŽN’Ù!'kJ.œŠâ,›{¸Ž}Ÿ«Ž=Mb*×·Ò²%dQ!*Ï~%r¸OLáÚÜuãÈdÀ´"ë5…ØQ“6ë©wÈ¢ü
ÿ|îŠ-—aí)LŽ~eGƒCí,œf7ÖéÙÑOg3Ftu~4‰Á@¡ïXŠP4÷ }gx8Ý$Í*÷ûª€Ùü~l=!ñvHŤ <7̦™Z.ÿª6×ö¢5ô,x;;9™ '§¿Înñi 0„cËÃótð(æ‘o̯ÕúèI-3™+ûM…çsP‡©1W!öˆÐnSÀã~Ðç†A ^)¢k5¹%í{‰˜÷Ôû‡ w^ì~½Ý=lA^é;qÄãQ_°¹š-æ—‹Ùíñåϳ ?¾¸$Ôùð%¢É/ ƒ°ºNÔoš-v
ižØ?¦Çèå¦è ž öiý¨¸ÎEιÚbç™—Ë÷ãcÄ ’d¾ó^C¬Ã“íWÚËÖ/Ô1HæÄí‹süÖ²%‚èg÷æŽïó(µÐ8è r£[qXl;.õ‚M-u„õ˜W]ƒÂþXVó'ðr3túÛ÷p@ÅÛ¨,¢UòPq¶Lk°uRÉCUˆC—{=l<Ùúèr;4)léÖA*La=u£€ûþÀóÖã89Äjp)QùWtrè*Ⱥ"Ò.+èúQÑ—ð ©³ Vƒõ²4ñÞ©Ç…Tˆý€Û¯›³‹ª%ZM[JѺúüüF‡ÙÕtù|ئ9 ;ýóË‹ ЇÁE=GFZƒÕ&sÕÓ¥R9Zy»g;äA™ì‡NÒWá˜!!ªû,¥HR³ †`
; ¹ã MhÑm6Un²ŸŒ(ÑåR·s| Ìõç;bõ«ýÒü
¨ðY~…<è‡-÷é´0
y/16ãzî
§ôØKBe¾A¯”Ô5À{ Gí¿‚ÞÉéÙ,9=ÿ>ÔP-¾ûlŠv
L)ü×DÊ:îþ)+ÊÒµ*Ž|-Y¥ÕDÏ^„\üåïq«ë{¯ º ë»ñöTMá¶$N v‘‡e·¾ƒ‹8º‘ÙTƒ]}w«!}×|X.Ö`V’:‡ qhS2“Õÿ]á¼Ê>f@ýÿ€Â\â(z•œAœÑAÑ yÛªM M@, ÊüÞÔR@&=”ÂljAè±E@Û
¿¯…Ã|89"÷:Fݳ #LßÃ4c»»¼L×DMU<æ4æ'ÇsddY"#© ^vÌ›m¨.&®™ÃŽÎgg——¿\Ïu0vtË·5µãF?hˆ`{wòz ";Œ¶Å}# Ž" زªÛû›¦MÁ# æJ]»•N^Èñ»7kˆÐ´ jŽƒœm
‰IkX^W ¦Ý¾Ìåo÷P‹ ÊbŸ‡Ñ0²yf“} ¼Jý ðúœj+!”O íAØn;ôªj¨e¢,”‚ªÿ? GóùŸÀÔÜÃ}/¤ Q=ç¼ tD¤ý)?èbqön±xoÐÄT9HtË`ýŽ®k›UúQ÷ûP5Ñ•â÷71²¸!¦XX•n@úzòp¸ÈAÕyƒ£'7'ˆö‚2
€ƒ-‹†@CtèPôIußb¶1ÞvÐ ŸY‰)ð„O:ž±Çí`Ü•½P_JίfÉÕÑÅâdve SåÓ%Ø0y¡¦Ï™Üè‘ KihºlEÃ#É|¶É7Yä¥*Ö•4
uCJÐôTev¦¥ÒÔœ°›«PUKY¤ÏtOÖ©Œ’·žIK¹¥ö\)•¢X£‹ïµFºÄè¯ÿCL7»ÌýÐh´¹7A¸!3-!؉¼cŽmÇz &&AVÏ’ƒãßÿ K¼É¡endstream
endobj
6 0 obj
2527
endobj
14 0 obj
<>
stream
xœYÛrÛÈ}×WÌ›Á” c÷¼)6 +%KZ
ÊV"§T 8¢° 4.Ò*ßàÎé @Ò”l)[*[.Ó=§»OŸ ~eŽÍ™C?ýïl}ôn ²Usä°ÕÑ×#®n²þW¶fKð@D’Û#ýg¡`aìÚQÌ’õç‘ p–< ][YW72m oV²ÍËÛê‹å~™°"_ÐÉTøŽí8¡õ9-»´`‡ Ÿü'ùÇ‘°)þ%Ë#ëýÕüôäìãùÍÅ|–ÌÏ.?Îæ7ÉÉçÙ$ùíhŠø,ÉÔ \¨.RºãÐÕØŽ|¸Œ«Žíú!yi5
KÙ¦ÊËVÖ¬ðDzꅤϵÌd¾³. {±Y$è¹ÇãƒîÙ±÷íÜá‘|-ß²¼d̪rÙàs 3Õï춮֬Å#M›Ö-ëÊ6/ÔßßÈ‘:-›©rƒûÜÅ°7ÇŽ _c} ïó†ýÖ5-KUG ³…œ3‘ïY«¼´Yr‡Gò2+º¥Ä¶‹‚mj9UëÓûYµ^§ð‹á?VJ¼#l/0›‰@mfUµyÚæUÙÀËk¸¾‘ÚÉþ•ÁG—Gê¥,ÿ–‘W´¯
¶™g]‘Öp¡j«¬*¾X
’#/{¼…†Ò¡¼RÖûj;ýÅâž.†và:Ž¹&—6;iGÙÐÍwsîô)ëyväzýceÕêÛCBû¶ ›Ev m7
<㉰#Ún¶ïÒVz éÝÐlŠb.Ëe^®Xu«¡éñ˜¢„™òCø®=bªc^˯D¼UÚ:_dMÙl:ñûàÛ*”SU Æ×c!]&”¯ƒÜ²Žç“À¡±•ì—Zàç«ËqýWU—gñX¢ý"ûÕ8>ß7ôÊòªßⱕ¨ ]`^L¾˜Ý p÷#‡›Dt qO# ¢8êóëÚZ.&^Àm7ö¬ÇB!¨v B°^$ôSÂæô.v Yq¿HŸ¤;U¤iÑèz¢½Óå«ïÛ^ñ½lid}¯éÀã¢QJ‰RG ²´ JlÕˆJÓíŒf>ûp2Ÿ½O^N» Ã÷^“® NÌ"A¿ÈnbøxÄö
8U‹öòLzTµ"ÃZ.sØ&^C¦ÈMŸ~l‡Ž0C¥¸‘F´+S€_`¥nó$Z–Xã-QëÀ¬«á…„Aä^INÑÅT›|˜58qd¥ÎT™ŠY>Åžxèª= Ž™nÓ\q²$2ßA•“7#Âõl_ô¹gý!·b´•ºdI£—uÊ5•^Ó¹‘cÝm¬[3”
ÀÅNÖY_¬ãåR. öÐŽèçªE<ŸWïϯΒ&–àü‰Ä**ë|ãÚ^š%ü~‰ý´
#' ÍìfUÙ0îÞFDSòƒD˜\ˆ›âð…êšZ ˆpF t{Ý:‚‰¡¢‡ª+–»
[D6`3P¶éït›˜"ÐѷƦÑÊÇÑ ×vƒ^ÓXUGÛÊoÙ#>=Ð3 ì{|¸¯"@¢¿¥k„Ö¹–,S".ŠÃùEróñüôôœÞà é›u~==¬üƒÊðM‹HNÎÏzÊÏÒ’ŠV²ûA´Éú‘Ý; í]^þκ†äùBуp!¸C]^´½ côб"m'ê[MiDø =ªd•ghƒå-cüÈÓj%ÆGV»Ú–1n`Pº¶ªjÉdYu«;Åäìb"”¾w-¨Q®&3³ã
<Ò©G8ƒõr-JoûüÛÑ`1”Iü¬ÌQ*D{k‰_®4
.Œ€Îv
‹èž \§´kTï·UW+FÊ7JÙà ‰æ›<¼1À0àŠq~j³‚Å($úŠå1åÂaùuòïÙÍÕr™¡à:þð2¹õ
•å"ë Äò´³Ëw麂|"ÄH6m]·)ªtièŒGÚáÓþ@Ûµ~=ë·Í½àÅÛvlÏy•˜ ÿŠ02‹„Î!1
Ýh4äê–ÿ8,«‰ @z±õPö ÂeÿŠÞ#÷ANŽØ“h`ªT¢VIH¢Œôý¶Œx
Y(&1x&=ßBçW/Ê4»3Ó[Ÿ¿c£?ðèÖ.é~_ÀOÍ •èá8^Ìf þœ@¾N‚þ…k–€ª=Øx8wâÑÌнÓÝ¥4.¾«ê¿—EÒJ˜@&À4¨¡æU
(R]Ë´éÀ¬C ÁëÓ>ð`1ñ]àµRë3‡¦/½°Í>›•\•hï´zýÁD§"óq
87~í‰/FÄãÃ$Q`ÐhèPT¼0üAPtL4ùüT Öš£BLbÜÝí z¥çZ}š ÀxF÷ÂÓ( <%ÀžQ¯p€Þ3 R^ž º~<š vé¼Éÿ+‰ÄL?¼“ૺ9dÍãj úA4öä± ÐCo ÜR¸~èõ¶¦ýS‘u5»L4¬/=‡ˆ^1Ð9P8 àE‡ˆ3¿ÏÅž™ëï%Pó¦é G\Ó˜ C^ÅnÇ¡¯ ÉÿS’\ô|á‘z‰ØÁ“ ,uV©¹€hÑuúHÍaM&®–XRÃ$"µ85D5)tªÒ¡äQ[wòÜryzóÏÙüäã¿æ³Ë«ÓI,°VXÉËBƒ)ÀyÍÀêàã°á æü8ä|ßÌp´a¢’ɺͿeê“©³;ZÝu· mYÏé6¯bÆcŸõ \¹Ôû¡RûcÜ(Ù͘0Ⲟ³j£×¯öf A$hÓxBŽÞ7ôùÎH„öâ¹ÃùÔ—I_].Gƒ>
stream
xœZÛVÛH}ç+ê-r¯X*Ýç!ô43bz&+Ìb » Ô‘%G’!ô7ôGÏ>uÑŤW.€,UË>ûìSâ+ó\Î<úc¾ÎW{?ŸÇìs³ç±Ï{_÷¸ú™/óûû 7$ta¶ÜÓÏp §¾›¤l¶ÚãüÀ —=àÃÝ€D’noGaí—ÖQÎGM„ëE‘ñì±t:-j$k3–5M5ϳ ºËцhEÕ¨U¤#ôõ¸c#ŽV¦a“• 0é¥Ó ¶Ýs”‡Ó³ÙÃ4ðˆ2–ŒÒ ]‰ ©¨F% ƒu›W%|¦>çžÑ#>@àùöé^MÀ°jÝj1¡ž°&N‡¸œ¸ì¬À’•b¢°»¬je¾ï¡4x0pߊ •€òµßTeóvÐœ=èæܱ;b›5[ÀPu€Dº|¡#Rn½xÛ'sWx¼CJ ÚioªÍç&—*”b¨%Hn nÔ}ºßÊ$Ä Å=»–yù–¾±ˆR=É ÃîñjXæ"Xá§7º:‰O¸HÆ ìÒÙ_ç%u?Ï5Y™ª¾ò ŒÍÎŒ¡r 9󒾌/úð A‰UW´Ã¾Á¯ &èºãoûǼþ¡£ãqñ§x&L“çÊŸÇÁ#å_Tá«¢ïYeŸ±ëníQ£ØÚ(oWYó\äó¬¥4ä²
þ/[u å±’ Æe Å=æy±Þõ‡GY!/2($j‘Rç'D¬Â¨¯ n$u(²Á´Ûë¼U-U¢M9ßÖE–—:ÛCZPi5
WçUøà—äù´²JW¿)ÌAùGÜ
_[û¯Lø4Z“'Ñzvn é>ï·8ý¯Á£f:d¶›ð@¤5æÇ}6p
›wâú/A4é=/~ÐÑ+à þèpš>‚å´‹†Ý㇑ º `ŸArOåaJ#Ë0ÍPaÕ¦&‘òí~kw’ìž·z”Ù „ÓW‡çç'§/Tξ—¼"ô0È6yÄÕ,1› xÄl£³¬ë²Î’u®£E"6#A]¢‰°¥ò–ûh ¡—@·Õ{ey±©A'h›´'$M""ñ`»N
šî¤¶;šX¢õ‰8ÙJMU¢‘¸ ªŸp£3õžJ"ƒlаºi³Æmk6ó¹lšå¦ aÈúñTbǧSyrñž†¡“Ãه¦3H Ó…O¥31ùý˜Ð¥óf ý˜BÕ—œ¹¯ºc«¾äTZl»uVêaQݺÝðïËñêt[÷¤¼có K X-î'_»±Â ¢ÜØó vƒY>Î!ŒZ5jgó›\Ž½ÀGI²ÃÛñ¨ Æ–Ñl7J"·oFκV—av¯nÐY„Ñh·yµÁUc”Z"—Sjžêqb Ž\Õ4Hn4!@CÝ œƒjuš©\™¡ø„@´ç=xÎß MµÁ@–דç€`uq2·¥R?ô;xä«€ÐXHfeæÐâKYédFtTQŒÙnp·…ÒKÈ,¹”€fí1RÌâ[Hdéü-[¡ˆW²A `D¼–jü“Ýû-oëëØOÍ¡Dšº¡ßimòÃLø„/Ý0[¢æ)9`’$‰RÚ™Û ‘®5 «åv²x‚xY‚ú µ€A
¥›©+ð
Òä Ž ÀŽn®¹+†ãe y
ÓøttÚ:G¬°Þ*SG6Ìq/ ÔSD`¤KÀi
b‡>eq«\%˲q…yfÏü;{CÙšQÓ8™·¢TŒNGpVUh ,}Zý.(§ñÎC= ï÷Ï'%=LWGg/=’õRñ#6Ä–Ù¥|³Ô6ÉD‘U0ývã;cȺšâ§U^ª9¹Aß›ªXXñr¤ç SÜû^æò”ëf¹X S5V.¯ª¦U62ÉU)í47Œ©£@ÊøpÌ cUÉÆ^Œñt8§›#/c÷*£9&ßFú7kÕ¸G'ÈhÏf‹ÆÀX0ê Òóç'G–ÄJ ÝþõÔlO±¶Rµ’«ª¾'"Ëô}wyQµœ*bÀ¥r@˜¯‰ 5©5¶=6,¥Ô-¦ZOÞØ£¤ ÚÉTÃSP"~ \ ¹ÝAW€öZÅô½”k• z
Q¯´|`cå i•B£–ÿ.ðŸâ'£bf/=цÐ~…¤ •ÜñtÀw 1˜¾Ò 4 ü’Z quøözÜNy J:é½»qßÀG¸ _p|ò2 õ#;¤ÛñéÁþñÕÑÙ(ßóÖ€¿žkÀÂïYêỾ½Û+¨¦¨æYaØÆwS‘ŠÓ [b²™K´Ì£3öp†ZêÍ‘@†SëÜœcNo#XôG
~ª¡ù€èíbj ÂNö: ¶YÑ‘ÒJZIZnšQÉg+¢²Ã´Ël½†*Éš‡g‰<]H6KÛÕ õ&~з22PÉê–Ñy;KÝKg€µX$Ü·g Õf6чz™8Búp>ù´rb ¶i*â—³Jðš‰_½d´8vÃ|0ðQ‡s…[6€æKˆEã=ðé<Ùºõ§ˆS>Õ"_J31ÉáÝ4spzú¯£Ã㣳— èú0ðo&a¨[àºÁ ®DjS@ó±ŸÞô)%šÇ‘Ëýî( ö‡Š½ …Ö÷ûÊË/frŠ’A²¬er1U{"9YA3Rõ…ë ¾«!¤{AÝ rú Q`Љ‡oë¼ÖrêÇ4/ Ê=ôC3;J:6¯*:‚Wé·št@¦¼ŠbüN·ËaSçÝ;XGŸî$
}ȃº6Ú5¿¡ ¢zµ¬'~Dõ#Ðü¯àlÿÛƒ9
Âî >ô#{²TSœ²%¥0o1ü6 9Yª^˜S¢ÐwÃ$uŽÊi”«é=ƒN ˆ¡¯g?¡“ÃÁ6=%è·Ä“)1:Àý/òš ÏKõ›ƒÈR‰OÎ Îöþ?ÿªÑæÇendstream
endobj
20 0 obj
2906
endobj
24 0 obj
<>
stream
xœÅXÛrÛF}çWLåE`JB0¸#yRdfW±B9"³[)yK‚#k PŠò
ùè=Ý3¸Rì8/[vY29Ó3Ý}úôéù( [
‡þ˜ŸÙvòÍM$ š‰# & '’¿æG¶ß/± ¦–÷½GŠÈQâÙq"–Û‰”± J±|šÜZÙ¾.îTÚ<ß=¨6/ï«÷–÷~*Š|EßLÏÜÀ± '²~JË}Zˆ×—Oÿ³üq‚#μP,×Çè—§‰•UÕ‡\5â}ÿÛ}U‹v£Ä&-×ý˜.ÿ;9ƒsXfé%¶—àÆl%ö¶ò¨DIË ^ÙžtK³¤jÅJ©R¨2]j-pJ“owų(«òå1¾c»ò•cVŸ9†Ž¨U¦òs^h;‰o®
3½‘Ävã$öÍkÄõ„¾“¾-ý~}ÓÖû¬eƒ^äÙQ,ΤËÇêRÄ›"oZñõ‰xÊ‹žŠFµ¢Ä®ÊKþeþËÕ•0Ÿ¯×ð>/EdÓ)H
Û
a3´c>ïâ—›«Ëù×wWç‹åâúâílyäMwë]:r%6Ѷx|µ¦©¾‚ªé©(ªò~{#éú¶ ËÎDhL æíóÀN\ïø€¥Há}Se h©¨†á°Ê×@F@ö
|_=_yÃHE˜š&¯J[\Þ3êØFb'I ]ÚueÅè=“Ibnçºo{À3&ŸàßãÔ
lGº®•ùú iwÚ}]ªµ-þ½6ž«½ø£Ì›xb«®+íØ5—%›¦êªúCŽH=åíæà^1€†{²¡í ^giQè v¶:tØIášÌ
…2ݽ·€´´A<¨dQh¢€¯¦¤EVTNED]T],ýìI˜h°·¼×¶Ôp¸©öu†JNìÏÏ8Ës7‰zàèYi‹”ônꢷŒ„¿íó.'Ÿuê Û¬Ú®ò2m‘4ÞFÖ¿¹‘Ž¡37sEE· åëwË»‹ëù|v±¼»ž_M]â«$¶~娘 Œ
¸,[—1päa½ ÖP`»º†\Àìjbͯ§'T¿Ž—Ä]¼|ë¬.gßjì¿»ÔÐj/öïi*q/™]êÙ¿2ôOÁSe¦ó¡‹‘¢¢úïÉþ]åH`Z³O@¦ té² ”ö%í ð|¹µž69H6otÊ'd±*q'Ï%³á5æˆÛ$~X¾»›Í—7ÓÐï‡Ö¯wïLÁØRrÕJŽáë|9T³ ŽM:–ûçœ% …øò“Lã€&þ„h²MZ?y…pиü¨ÇtOñ0Ô Eí9òè´ñ9 gÊÖ¦*Öô“²´KæJó‰*Ûú™?ш’q FJÔut‰.7)“
íÉ˼ÍQ—l§+JUæPe€Ý1IQ=<œà"´¯VÛªU Õtžç¹vè Zªf Ú šM"¿Û!~”°¦ì6\›¶ª© 5$Ö‹‚Ú 1Jñü ä±U ;® O5uÜÛ×µ³üúÖ:/š
U@ çKª@kûÃ%@¶ýO¢ñb :Ö’þ£þÕ®…ê M§x‰¦“iÊñL3Ö2'S5K ê»D„àävÀM¤…6ü@
¤}ÑŠ‰–RN¸¡ÓÊýv¥tõžñz¢ ‚À´„{€¡üÀ#¸—W‹»Ål±¸¼ž¡âç|‚»|ŽþwµEc¨Ëžž…IŒà„«ÛÛ
¦å¿Ã î£÷ƒaMžxþŸÍ*ƒà°ert8_! G˜"DSQqöò¯íÊ"‹dÕimôàxVl6©ÖªÐ!-HXð˜OÇí
¤Úñ….usc–,]¨Ñò èöh”sF £ QòÁ¸¶ìDYÏ
éíCu{³° âQuñLÎŽ †¦ Œ
óÑ4I4‘ÞÔQ5ý5ó6}fæ¢Ìqˆ)]T ÃF£æ@9 :çz"20eL ¶O—äãgXº —¸UæD
”žû}Íc
3Ac¦RwÉÐãüÐÓ>ÀyèÝ=82%_øEáQóbò\ÅWeZð˜_Ò… äqÿ3„ØxŸ¡ºŽöÂP¹ÎYY¥z""üPvàü¾3Â\ó¤IϾ4¤€¤ô–ˆo0²°]z^'Ä Xö}çÏ@2Å~/¥/Ôy˜»Ãz;›¿¹›_Ïg'”~SDJ×™Áº‡i̼tvØ·ÇtlÑ
‚ÎÁº›!Ðå¼£‚bÝ»öNźRzºÙb4Ô—Õ«nÉGc-¤4) ¦‡YÊ< 1kºñ1kb¸{s¹gÞý2ÿé ß*Ð
ÃðËß*Àäá e’0zõÂõ¢atÐknéµB‹=!I%›VºÎ»Ôǹ¢ q÷îº1‹«àPW™)Ë÷í(¥u¾.OŒB®5¸a?ÄXíö5î0¦ºžÉQïF©£á'tzâìôãòò§YŸ½c©CÄɬ?µÅy‘6§Úíþm„â.Y•~(«ƒ‹K/™và|ÅÖ ÞèÞú)ÁÀ›&ê33©è¦3<ˆ˜i«©ôKL +BÏD.ìõ.¶ã¦!ã¨yLœþ ¤M¦rá×Je)Lzòàb‘/Wv$ÔÞ@Ȥ×nûâ°Á:´ð jµ~*ômßïgýýÄÛéö£Bep7„hfšNRñ»ª+=ß_Â1/›V¥G5Š©î¥®ñÇ%úÊ\FS™ [–‹wƹ»|ó¥3½þí êMÊ î‘1u<òûPÇ®{tàíç†þmÕ´|&úžv–Þrà¬X(t=]ª±g eÅb1pùÆ ž 04#ïvËŸª¤æÐð,Íža’S$’nè ãxÔÇ'ÖÏö|p'5*Túq©-IÒ ÙTûbM¨…ú?ŒS±†2ÝP†òUvó='9>–Ÿí ) Ñ ƒèÐß•B;UüÆØ….=ÖXè2Þèù¬WY£á-¹ö”Ö;eÞXh ˆþ /®.gs À‹ÙÏ_ˆÃ¿Ñ1èuì…G£€¾¢©U˜‰3õo¸X¨#¹Üi<~ÑF ¼±mˆ4ý¥‚¼™ÆæÿÿšÝüü ¢Á\Ò¼:âЗѓ¤ä?*O¡
€} ªn,Ôü6=“Aà%æƒ ÔJ¸˜Hy#IW Ÿn?[N~ÆŸÿŠð‘endstream
endobj
25 0 obj
2813
endobj
29 0 obj
<>
stream
xœ•XÛnã8}÷Wðm¥E›-ê®}ófÝ@vÒvÆVÏK²d™Ž5-‹n]œñ`>¡?z«HQ¢ /zØ"YU§N*úq(#þõÿóÃäã*"¯ÍÄ!¯“o&_’þ_~ ÿLaAŒ_¤»‰ÚÃHä’(ñhœô0a,¦!#éÛäÉÊ»º|áYs~yåmQíijå=Û¤,6øÆžºC '²>gU—•äörû?é¿Á(sz«`mê…$Ý‚ÒʳµXÚ¾<ɳÒù?àü¦åUQ½’¨IÃë¯IQm‘µ|KjÛ‹`q[ü[Ç›¶!Eƒ¶áû&±ŸX¼jË3éªâp,ù>ñí³M{Gtô®OÒ‡‰Ccmú÷'kv<–Ežµ…¨òV4{ô¡¤æMwà$«ÈÊš$nd¥ëGpi`-'«D»7sQU<ÇH³] îò¶.¸4>…<$Í'žŸPßCüFYˆ X'NZ;ý qÉ',€N¿½”Kö*"‹Ë E_z?eî §µá 'y)éý üäm>Ž©ç%±>ÛÓÖóÑzHÝÁº5ÄDå1 ’D`6¤1¾²î¾¬ /+;Ô‰\?¾Ü翾¬æw¿]E j—Çl0™Ð8Ð 9LùÔ4$#GQ@kLDFJ¡S’óË ÆFÀ<æÝ Õ§AìÆ×f £ƒhZy¨¤ÎûÓãˆÆ,Ñ€œ8¾ti€ ën Äë_nïL{ìž/íù7²«ÅAfù"‡FÌÕx-øxPD]´S/Ÿ,zo»£^ Y»³W™KÀ\ìé¬u5É£§Š/~D ß3%õ-IW^å¢C s\n–,£~ 骲=Y
ž¯V¶×—ÅruUfÌ©?„Wä,:rÈβÂ0—m-ºMÉ¡^D …´ýUÿýGÑ-jDþÍÁ ñP4‡¬Í÷ds&Gο"ã³vB™œ "D<´²²ãºúp‹&z6E%Ò ¶ÒûÏóµŠ[»nðtE~ɶ„a’\ðÁyÏ…úThªôEíiß„õs׎9t=¨MgÀ R èÏeD˜¦¾¬\yx„@'‘vɬ,f¸T”€øwC±A°%èVSB¦(“°k\yä5(ÌA¯¨4HÉÏ.Ê*ªé_ÓéÂö|Å‹ÙçùÃrùË—Gé3¾ƒçn¹XÌïRûoú xf·¾†çq5OW³ÅúÓ|¯z æ³Nmhc ˜5SBÄ‚ÄJ‡M†eóAC ¢¬³ Ê<ÖÊh-Ó±’ûÚ³fŸ0Q ‡Øß »šÿë~…a(Úx2GS —æÜbf*…3 Àº¬C—Ñ„9®6jèîÂv# × ~AF˘]»2:£*¡1Mj„ •îùƒ†º¾ÖGIÀJKˆ¯†vµYÝB£m‹R~®2XÝR”',Å7I}ô,ÔìË%E §a8— lÕЧißÙ ”4 .±0Šs@¡_©"‡å M ï*pð&JnŽRë&º#û€òOEÞ÷})g{Äà Z>tKܸ”¯=ö›g ”îX‹?Î0U½Ù ¡qà€1ð5~ˆQ"?Æd\lÀâr]ñ!¤Å/aqœdBpÛÏ ²^?hd>îAÙ§½¶Ä±Ö¾6ûì«)’±9{ð·‹n:½—=ŽE»7 'Ö7›9½NšHܳíÈ¢Â'¢ áN?ŸNC‰Çl¦Üüfcµ³ï]ÓÏÇÑë6ξ§qN¼Ÿdßwô¶Îªf‡“rC~ïšVA
*èEùuÜD—mD'éºá6C‘Õ|-*JR5cæe·Å S–ÀP> N<É5©Ô\ë†0ÃúÃ8먩êUàÀ.gév]9ƒ±´9ò¼øž÷e"]Ô›/¦Ø#ÄWä]™ÉúhE.Êg«*)ª^O]ÙÙpž¨ræ0©;hyRñAÊIÖdlN°ÿOï¸IC„áŒÀíé%pk Ëè’
ØküTðàþ¥'M( 'þI.ÔP›3C¡´–Éñm,·£3NλáöÝ8ódm78´XçÒX\›ÕÕêãcÙô@ìaD1feÿ>ñzòGýèo¥3³&4<Wõ ï‹P÷ZÕÊÁõqB[^ô¸xtxö0Ôk ò˜"ß¹‘ ¼Z\‰háö+³#v2P1€“u*D×€4Ékª¦ ¤Ý7ÕÜœ~ 2z©¡0Ñ»þ7Ë[¬r+ ½M*èGXñ5ßµ¾Æ¶ü8‚êð%¬íŽ úöÆ ÿÆB ŒÕËþÄbÔŒáCSý^!xøe¦ ª©Á äÎѧª* A—|G9_‹jÒ‡çO^ RìH%ßU¯Ñç\¨ Z‘ñ Ë,çT!ÿ¿nO¡ôËjA~³N³!(Ä×ùÕ5gLÌh¾’ï{Es6FÁ8‡èL$¾7DÖå9oš]W~ ꎵüƒ »ºÂ—ø\›äop·«Å±Æ E¯kÚ z+ ¥ÚÖXúýIïC6' …Òz>'³‡õr\{ÅËñNÐðV ÛËÛ¨Ž®1õ;d‹m—L£„öâÙÿ–¤º±oã½ÃK,¸—~ââ‚hJœýP÷Ì ™§“_áï¿@ÄÐendstream
endobj
30 0 obj
1973
endobj
4 0 obj
<>
/Contents 5 0 R
>>
endobj
13 0 obj
<>
/Contents 14 0 R
>>
endobj
18 0 obj
<>
/Contents 19 0 R
>>
endobj
23 0 obj
<>
/Contents 24 0 R
>>
endobj
28 0 obj
<>
/Contents 29 0 R
>>
endobj
3 0 obj
<< /Type /Pages /Kids [
4 0 R
13 0 R
18 0 R
23 0 R
28 0 R
] /Count 5
>>
endobj
1 0 obj
<>
endobj
7 0 obj
<>endobj
11 0 obj
<>
endobj
12 0 obj
<>
endobj
16 0 obj
<>
endobj
17 0 obj
<>
endobj
21 0 obj
<>
endobj
22 0 obj
<>
endobj
26 0 obj
<>
endobj
27 0 obj
<>
endobj
31 0 obj
<>
endobj
32 0 obj
<>
endobj
10 0 obj
<>
endobj
9 0 obj
<>
endobj
8 0 obj
<>
endobj
33 0 obj
<>
endobj
34 0 obj
<>stream
2014-01-29T08:09:44+01:00
2014-01-29T08:09:44+01:00
groff version 1.22.2
Untitled
endstream
endobj
2 0 obj
<>endobj
xref
0 35
0000000000 65535 f
0000014082 00000 n
0000016273 00000 n
0000013995 00000 n
0000013187 00000 n
0000000015 00000 n
0000002612 00000 n
0000014147 00000 n
0000014712 00000 n
0000014647 00000 n
0000014579 00000 n
0000014188 00000 n
0000014218 00000 n
0000013347 00000 n
0000002632 00000 n
0000005195 00000 n
0000014268 00000 n
0000014298 00000 n
0000013509 00000 n
0000005216 00000 n
0000008194 00000 n
0000014348 00000 n
0000014378 00000 n
0000013671 00000 n
0000008215 00000 n
0000011100 00000 n
0000014428 00000 n
0000014458 00000 n
0000013833 00000 n
0000011121 00000 n
0000013166 00000 n
0000014499 00000 n
0000014529 00000 n
0000014794 00000 n
0000014850 00000 n
trailer
<< /Size 35 /Root 1 0 R /Info 2 0 R
/ID [<1B61F9555F20156DEBDDD00F825502A3><1B61F9555F20156DEBDDD00F825502A3>]
>>
startxref
16427
%%EOF
curl-7.35.0/docs/libcurl/libcurl-tutorial.html 0000644 0001750 0001750 00000230660 12272124467 016261 0000000 0000000
libcurl-tutorial man page
NAME
libcurl-tutorial - libcurl programming tutorial
Objective
This document attempts to describe the general principles and some basic approaches to consider when programming with libcurl. The text will focus mainly on the C interface but might apply fairly well on other interfaces as well as they usually follow the C one pretty closely.
This document will refer to 'the user' as the person writing the source code that uses libcurl. That would probably be you or someone in your position. What will be generally referred to as 'the program' will be the collected source code that you write that is using libcurl for transfers. The program is outside libcurl and libcurl is outside of the program.
To get more details on all options and functions described herein, please refer to their respective man pages.
Building
There are many different ways to build C programs. This chapter will assume a UNIX-style build process. If you use a different build system, you can still read this to get general information that may apply to your environment as well.
Compiling the Program
Your compiler needs to know where the libcurl headers are located. Therefore you must set your compiler's include path to point to the directory where you installed them. The 'curl-config'[3] tool can be used to get this information:
$ curl-config --cflags
Linking the Program with libcurl
When having compiled the program, you need to link your object files to create a single executable. For that to succeed, you need to link with libcurl and possibly also with other libraries that libcurl itself depends on. Like the OpenSSL libraries, but even some standard OS libraries may be needed on the command line. To figure out which flags to use, once again the 'curl-config' tool comes to the rescue:
$ curl-config --libs
SSL or Not
libcurl can be built and customized in many ways. One of the things that varies from different libraries and builds is the support for SSL-based transfers, like HTTPS and FTPS. If a supported SSL library was detected properly at build-time, libcurl will be built with SSL support. To figure out if an installed libcurl has been built with SSL support enabled, use 'curl-config' like this:
$ curl-config --feature
And if SSL is supported, the keyword 'SSL' will be written to stdout, possibly together with a few other features that could be either on or off on for different libcurls.
See also the "Features libcurl Provides" further down.
autoconf macro
When you write your configure script to detect libcurl and setup variables accordingly, we offer a prewritten macro that probably does everything you need in this area. See docs/libcurl/libcurl.m4 file - it includes docs on how to use it.
Portable Code in a Portable World
The people behind libcurl have put a considerable effort to make libcurl work on a large amount of different operating systems and environments.
You program libcurl the same way on all platforms that libcurl runs on. There are only very few minor considerations that differ. If you just make sure to write your code portable enough, you may very well create yourself a very portable program. libcurl shouldn't stop you from that.
Global Preparation
The program must initialize some of the libcurl functionality globally. That means it should be done exactly once, no matter how many times you intend to use the library. Once for your program's entire life time. This is done using
curl_global_init()
and it takes one parameter which is a bit pattern that tells libcurl what to initialize. Using CURL_GLOBAL_ALL will make it initialize all known internal sub modules, and might be a good default option. The current two bits that are specified are:
CURL_GLOBAL_WIN32
which only does anything on Windows machines. When used on a Windows machine, it'll make libcurl initialize the win32 socket stuff. Without having that initialized properly, your program cannot use sockets properly. You should only do this once for each application, so if your program already does this or of another library in use does it, you should not tell libcurl to do this as well.
CURL_GLOBAL_SSL
which only does anything on libcurls compiled and built SSL-enabled. On these systems, this will make libcurl initialize the SSL library properly for this application. This only needs to be done once for each application so if your program or another library already does this, this bit should not be needed.
libcurl has a default protection mechanism that detects if curl_global_init(3) hasn't been called by the time curl_easy_perform(3) is called and if that is the case, libcurl runs the function itself with a guessed bit pattern. Please note that depending solely on this is not considered nice nor very good.
When the program no longer uses libcurl, it should call curl_global_cleanup(3), which is the opposite of the init call. It will then do the reversed operations to cleanup the resources the curl_global_init(3) call initialized.
Repeated calls to curl_global_init(3) and curl_global_cleanup(3) should be avoided. They should only be called once each.
Features libcurl Provides
It is considered best-practice to determine libcurl features at run-time rather than at build-time (if possible of course). By calling curl_version_info(3) and checking out the details of the returned struct, your program can figure out exactly what the currently running libcurl supports.
Handle the Easy libcurl
libcurl first introduced the so called easy interface. All operations in the easy interface are prefixed with 'curl_easy'.
Recent libcurl versions also offer the multi interface. More about that interface, what it is targeted for and how to use it is detailed in a separate chapter further down. You still need to understand the easy interface first, so please continue reading for better understanding.
To use the easy interface, you must first create yourself an easy handle. You need one handle for each easy session you want to perform. Basically, you should use one handle for every thread you plan to use for transferring. You must never share the same handle in multiple threads.
Get an easy handle with
easyhandle = curl_easy_init();
It returns an easy handle. Using that you proceed to the next step: setting up your preferred actions. A handle is just a logic entity for the upcoming transfer or series of transfers.
You set properties and options for this handle using curl_easy_setopt(3). They control how the subsequent transfer or transfers will be made. Options remain set in the handle until set again to something different. Alas, multiple requests using the same handle will use the same options.
Many of the options you set in libcurl are "strings", pointers to data terminated with a zero byte. When you set strings with curl_easy_setopt(3), libcurl makes its own copy so that they don't need to be kept around in your application after being set[4].
One of the most basic properties to set in the handle is the URL. You set your preferred URL to transfer with CURLOPT_URL in a manner similar to:
curl_easy_setopt(handle, CURLOPT_URL, "http://domain.com/");
Let's assume for a while that you want to receive data as the URL identifies a remote resource you want to get here. Since you write a sort of application that needs this transfer, I assume that you would like to get the data passed to you directly instead of simply getting it passed to stdout. So, you write your own function that matches this prototype:
size_t write_data(void *buffer, size_t size, size_t nmemb, void *userp);
You tell libcurl to pass all data to this function by issuing a function similar to this:
curl_easy_setopt(easyhandle, CURLOPT_WRITEFUNCTION, write_data);
You can control what data your callback function gets in the fourth argument by setting another property:
curl_easy_setopt(easyhandle, CURLOPT_WRITEDATA, &internal_struct);
Using that property, you can easily pass local data between your application and the function that gets invoked by libcurl. libcurl itself won't touch the data you pass with CURLOPT_WRITEDATA.
libcurl offers its own default internal callback that will take care of the data if you don't set the callback with CURLOPT_WRITEFUNCTION. It will then simply output the received data to stdout. You can have the default callback write the data to a different file handle by passing a 'FILE *' to a file opened for writing with the CURLOPT_WRITEDATA option.
Now, we need to take a step back and have a deep breath. Here's one of those rare platform-dependent nitpicks. Did you spot it? On some platforms[2], libcurl won't be able to operate on files opened by the program. Thus, if you use the default callback and pass in an open file with CURLOPT_WRITEDATA, it will crash. You should therefore avoid this to make your program run fine virtually everywhere.
(CURLOPT_WRITEDATA was formerly known as CURLOPT_FILE. Both names still work and do the same thing).
If you're using libcurl as a win32 DLL, you MUST use the CURLOPT_WRITEFUNCTION if you set CURLOPT_WRITEDATA - or you will experience crashes.
There are of course many more options you can set, and we'll get back to a few of them later. Let's instead continue to the actual transfer:
success = curl_easy_perform(easyhandle);
curl_easy_perform(3) will connect to the remote site, do the necessary commands and receive the transfer. Whenever it receives data, it calls the callback function we previously set. The function may get one byte at a time, or it may get many kilobytes at once. libcurl delivers as much as possible as often as possible. Your callback function should return the number of bytes it "took care of". If that is not the exact same amount of bytes that was passed to it, libcurl will abort the operation and return with an error code.
When the transfer is complete, the function returns a return code that informs you if it succeeded in its mission or not. If a return code isn't enough for you, you can use the CURLOPT_ERRORBUFFER to point libcurl to a buffer of yours where it'll store a human readable error message as well.
If you then want to transfer another file, the handle is ready to be used again. Mind you, it is even preferred that you re-use an existing handle if you intend to make another transfer. libcurl will then attempt to re-use the previous connection.
For some protocols, downloading a file can involve a complicated process of logging in, setting the transfer mode, changing the current directory and finally transferring the file data. libcurl takes care of all that complication for you. Given simply the URL to a file, libcurl will take care of all the details needed to get the file moved from one machine to another.
Multi-threading Issues
The first basic rule is that you must never simultaneously share a libcurl handle (be it easy or multi or whatever) between multiple threads. Only use one handle in one thread at any time. You can pass the handles around among threads, but you must never use a single handle from more than one thread at any given time.
libcurl is completely thread safe, except for two issues: signals and SSL/TLS handlers. Signals are used for timing out name resolves (during DNS lookup) - when built without c-ares support and not on Windows.
If you are accessing HTTPS or FTPS URLs in a multi-threaded manner, you are then of course using the underlying SSL library multi-threaded and those libs might have their own requirements on this issue. Basically, you need to provide one or two functions to allow it to function properly. For all details, see this:
OpenSSL
http://www.openssl.org/docs/crypto/threads.html#DESCRIPTION
GnuTLS
http://www.gnu.org/software/gnutls/manual/html_node/Multi_002dthreaded-applications.html
NSS
is claimed to be thread-safe already without anything required.
PolarSSL
Required actions unknown.
yassl
Required actions unknown.
axTLS
Required actions unknown.
Secure Transport
The engine is fully thread-safe, and no additional steps are required.
When using multiple threads you should set the CURLOPT_NOSIGNAL option to 1 for all handles. Everything will or might work fine except that timeouts are not honored during the DNS lookup - which you can work around by building libcurl with c-ares support. c-ares is a library that provides asynchronous name resolves. On some platforms, libcurl simply will not function properly multi-threaded unless this option is set.
Also, note that CURLOPT_DNS_USE_GLOBAL_CACHE is not thread-safe.
When It Doesn't Work
There will always be times when the transfer fails for some reason. You might have set the wrong libcurl option or misunderstood what the libcurl option actually does, or the remote server might return non-standard replies that confuse the library which then confuses your program.
There's one golden rule when these things occur: set the CURLOPT_VERBOSE option to 1. It'll cause the library to spew out the entire protocol details it sends, some internal info and some received protocol data as well (especially when using FTP). If you're using HTTP, adding the headers in the received output to study is also a clever way to get a better understanding why the server behaves the way it does. Include headers in the normal body output with CURLOPT_HEADER set 1.
Of course, there are bugs left. We need to know about them to be able to fix them, so we're quite dependent on your bug reports! When you do report suspected bugs in libcurl, please include as many details as you possibly can: a protocol dump that CURLOPT_VERBOSE produces, library version, as much as possible of your code that uses libcurl, operating system name and version, compiler name and version etc.
If CURLOPT_VERBOSE is not enough, you increase the level of debug data your application receive by using the CURLOPT_DEBUGFUNCTION.
Getting some in-depth knowledge about the protocols involved is never wrong, and if you're trying to do funny things, you might very well understand libcurl and how to use it better if you study the appropriate RFC documents at least briefly.
Upload Data to a Remote Site
libcurl tries to keep a protocol independent approach to most transfers, thus uploading to a remote FTP site is very similar to uploading data to a HTTP server with a PUT request.
Of course, first you either create an easy handle or you re-use one existing one. Then you set the URL to operate on just like before. This is the remote URL, that we now will upload.
Since we write an application, we most likely want libcurl to get the upload data by asking us for it. To make it do that, we set the read callback and the custom pointer libcurl will pass to our read callback. The read callback should have a prototype similar to:
size_t function(char *bufptr, size_t size, size_t nitems, void *userp);
Where bufptr is the pointer to a buffer we fill in with data to upload and size*nitems is the size of the buffer and therefore also the maximum amount of data we can return to libcurl in this call. The 'userp' pointer is the custom pointer we set to point to a struct of ours to pass private data between the application and the callback.
curl_easy_setopt(easyhandle, CURLOPT_READFUNCTION, read_function);
curl_easy_setopt(easyhandle, CURLOPT_READDATA, &filedata);
Tell libcurl that we want to upload:
curl_easy_setopt(easyhandle, CURLOPT_UPLOAD, 1L);
A few protocols won't behave properly when uploads are done without any prior knowledge of the expected file size. So, set the upload file size using the CURLOPT_INFILESIZE_LARGE for all known file sizes like this[1]:
/* in this example, file_size must be an curl_off_t variable */
curl_easy_setopt(easyhandle, CURLOPT_INFILESIZE_LARGE, file_size);
When you call curl_easy_perform(3) this time, it'll perform all the necessary operations and when it has invoked the upload it'll call your supplied callback to get the data to upload. The program should return as much data as possible in every invoke, as that is likely to make the upload perform as fast as possible. The callback should return the number of bytes it wrote in the buffer. Returning 0 will signal the end of the upload.
Passwords
Many protocols use or even require that user name and password are provided to be able to download or upload the data of your choice. libcurl offers several ways to specify them.
Most protocols support that you specify the name and password in the URL itself. libcurl will detect this and use them accordingly. This is written like this:
protocol://user:password@example.com/path/
If you need any odd letters in your user name or password, you should enter them URL encoded, as %XX where XX is a two-digit hexadecimal number.
libcurl also provides options to set various passwords. The user name and password as shown embedded in the URL can instead get set with the CURLOPT_USERPWD option. The argument passed to libcurl should be a char * to a string in the format "user:password". In a manner like this:
curl_easy_setopt(easyhandle, CURLOPT_USERPWD, "myname:thesecret");
Another case where name and password might be needed at times, is for those users who need to authenticate themselves to a proxy they use. libcurl offers another option for this, the CURLOPT_PROXYUSERPWD. It is used quite similar to the CURLOPT_USERPWD option like this:
curl_easy_setopt(easyhandle, CURLOPT_PROXYUSERPWD, "myname:thesecret");
There's a long time UNIX "standard" way of storing ftp user names and passwords, namely in the $HOME/.netrc file. The file should be made private so that only the user may read it (see also the "Security Considerations" chapter), as it might contain the password in plain text. libcurl has the ability to use this file to figure out what set of user name and password to use for a particular host. As an extension to the normal functionality, libcurl also supports this file for non-FTP protocols such as HTTP. To make curl use this file, use the CURLOPT_NETRC option:
curl_easy_setopt(easyhandle, CURLOPT_NETRC, 1L);
And a very basic example of how such a .netrc file may look like:
machine myhost.mydomain.com
login userlogin
password secretword
All these examples have been cases where the password has been optional, or at least you could leave it out and have libcurl attempt to do its job without it. There are times when the password isn't optional, like when you're using an SSL private key for secure transfers.
To pass the known private key password to libcurl:
curl_easy_setopt(easyhandle, CURLOPT_KEYPASSWD, "keypassword");
HTTP Authentication
The previous chapter showed how to set user name and password for getting URLs that require authentication. When using the HTTP protocol, there are many different ways a client can provide those credentials to the server and you can control which way libcurl will (attempt to) use them. The default HTTP authentication method is called 'Basic', which is sending the name and password in clear-text in the HTTP request, base64-encoded. This is insecure.
At the time of this writing, libcurl can be built to use: Basic, Digest, NTLM, Negotiate, GSS-Negotiate and SPNEGO. You can tell libcurl which one to use with CURLOPT_HTTPAUTH as in:
curl_easy_setopt(easyhandle, CURLOPT_HTTPAUTH, CURLAUTH_DIGEST);
And when you send authentication to a proxy, you can also set authentication type the same way but instead with CURLOPT_PROXYAUTH:
curl_easy_setopt(easyhandle, CURLOPT_PROXYAUTH, CURLAUTH_NTLM);
Both these options allow you to set multiple types (by ORing them together), to make libcurl pick the most secure one out of the types the server/proxy claims to support. This method does however add a round-trip since libcurl must first ask the server what it supports:
curl_easy_setopt(easyhandle, CURLOPT_HTTPAUTH, CURLAUTH_DIGEST|CURLAUTH_BASIC);
For convenience, you can use the 'CURLAUTH_ANY' define (instead of a list with specific types) which allows libcurl to use whatever method it wants.
When asking for multiple types, libcurl will pick the available one it considers "best" in its own internal order of preference.
HTTP POSTing
We get many questions regarding how to issue HTTP POSTs with libcurl the proper way. This chapter will thus include examples using both different versions of HTTP POST that libcurl supports.
The first version is the simple POST, the most common version, that most HTML pages using the <form> tag uses. We provide a pointer to the data and tell libcurl to post it all to the remote site:
char *data="name=daniel&project=curl";
curl_easy_setopt(easyhandle, CURLOPT_POSTFIELDS, data);
curl_easy_setopt(easyhandle, CURLOPT_URL, "http://posthere.com/");
curl_easy_perform(easyhandle); /* post away! */
Simple enough, huh? Since you set the POST options with the CURLOPT_POSTFIELDS, this automatically switches the handle to use POST in the upcoming request.
Ok, so what if you want to post binary data that also requires you to set the Content-Type: header of the post? Well, binary posts prevent libcurl from being able to do strlen() on the data to figure out the size, so therefore we must tell libcurl the size of the post data. Setting headers in libcurl requests are done in a generic way, by building a list of our own headers and then passing that list to libcurl.
struct curl_slist *headers=NULL;
headers = curl_slist_append(headers, "Content-Type: text/xml");
/* post binary data */
curl_easy_setopt(easyhandle, CURLOPT_POSTFIELDS, binaryptr);
/* set the size of the postfields data */
curl_easy_setopt(easyhandle, CURLOPT_POSTFIELDSIZE, 23L);
/* pass our list of custom made headers */
curl_easy_setopt(easyhandle, CURLOPT_HTTPHEADER, headers);
curl_easy_perform(easyhandle); /* post away! */
curl_slist_free_all(headers); /* free the header list */
While the simple examples above cover the majority of all cases where HTTP POST operations are required, they don't do multi-part formposts. Multi-part formposts were introduced as a better way to post (possibly large) binary data and were first documented in the RFC 1867 (updated in RFC2388). They're called multi-part because they're built by a chain of parts, each part being a single unit of data. Each part has its own name and contents. You can in fact create and post a multi-part formpost with the regular libcurl POST support described above, but that would require that you build a formpost yourself and provide to libcurl. To make that easier, libcurl provides curl_formadd(3). Using this function, you add parts to the form. When you're done adding parts, you post the whole form.
The following example sets two simple text parts with plain textual contents, and then a file with binary contents and uploads the whole thing.
struct curl_httppost *post=NULL;
struct curl_httppost *last=NULL;
curl_formadd(&post, &last,
CURLFORM_COPYNAME, "name",
CURLFORM_COPYCONTENTS, "daniel", CURLFORM_END);
curl_formadd(&post, &last,
CURLFORM_COPYNAME, "project",
CURLFORM_COPYCONTENTS, "curl", CURLFORM_END);
curl_formadd(&post, &last,
CURLFORM_COPYNAME, "logotype-image",
CURLFORM_FILECONTENT, "curl.png", CURLFORM_END);
/* Set the form info */
curl_easy_setopt(easyhandle, CURLOPT_HTTPPOST, post);
curl_easy_perform(easyhandle); /* post away! */
/* free the post data again */
curl_formfree(post);
Multipart formposts are chains of parts using MIME-style separators and headers. It means that each one of these separate parts get a few headers set that describe the individual content-type, size etc. To enable your application to handicraft this formpost even more, libcurl allows you to supply your own set of custom headers to such an individual form part. You can of course supply headers to as many parts as you like, but this little example will show how you set headers to one specific part when you add that to the post handle:
struct curl_slist *headers=NULL;
headers = curl_slist_append(headers, "Content-Type: text/xml");
curl_formadd(&post, &last,
CURLFORM_COPYNAME, "logotype-image",
CURLFORM_FILECONTENT, "curl.xml",
CURLFORM_CONTENTHEADER, headers,
CURLFORM_END);
curl_easy_perform(easyhandle); /* post away! */
curl_formfree(post); /* free post */
curl_slist_free_all(headers); /* free custom header list */
Since all options on an easyhandle are "sticky", they remain the same until changed even if you do call curl_easy_perform(3), you may need to tell curl to go back to a plain GET request if you intend to do one as your next request. You force an easyhandle to go back to GET by using the CURLOPT_HTTPGET option:
curl_easy_setopt(easyhandle, CURLOPT_HTTPGET, 1L);
Just setting CURLOPT_POSTFIELDS to "" or NULL will *not* stop libcurl from doing a POST. It will just make it POST without any data to send!
Showing Progress
For historical and traditional reasons, libcurl has a built-in progress meter that can be switched on and then makes it present a progress meter in your terminal.
Switch on the progress meter by, oddly enough, setting CURLOPT_NOPROGRESS to zero. This option is set to 1 by default.
For most applications however, the built-in progress meter is useless and what instead is interesting is the ability to specify a progress callback. The function pointer you pass to libcurl will then be called on irregular intervals with information about the current transfer.
Set the progress callback by using CURLOPT_PROGRESSFUNCTION. And pass a pointer to a function that matches this prototype:
int progress_callback(void *clientp,
double dltotal,
double dlnow,
double ultotal,
double ulnow);
If any of the input arguments is unknown, a 0 will be passed. The first argument, the 'clientp' is the pointer you pass to libcurl with CURLOPT_PROGRESSDATA. libcurl won't touch it.
libcurl with C++
There's basically only one thing to keep in mind when using C++ instead of C when interfacing libcurl:
The callbacks CANNOT be non-static class member functions
Example C++ code:
class AClass {
static size_t write_data(void *ptr, size_t size, size_t nmemb,
void *ourpointer)
{
/* do what you want with the data */
}
}
Proxies
What "proxy" means according to Merriam-Webster: "a person authorized to act for another" but also "the agency, function, or office of a deputy who acts as a substitute for another".
Proxies are exceedingly common these days. Companies often only offer Internet access to employees through their proxies. Network clients or user-agents ask the proxy for documents, the proxy does the actual request and then it returns them.
libcurl supports SOCKS and HTTP proxies. When a given URL is wanted, libcurl will ask the proxy for it instead of trying to connect to the actual host identified in the URL.
If you're using a SOCKS proxy, you may find that libcurl doesn't quite support all operations through it.
For HTTP proxies: the fact that the proxy is a HTTP proxy puts certain restrictions on what can actually happen. A requested URL that might not be a HTTP URL will be still be passed to the HTTP proxy to deliver back to libcurl. This happens transparently, and an application may not need to know. I say "may", because at times it is very important to understand that all operations over a HTTP proxy use the HTTP protocol. For example, you can't invoke your own custom FTP commands or even proper FTP directory listings.
Proxy Options
To tell libcurl to use a proxy at a given port number:
curl_easy_setopt(easyhandle, CURLOPT_PROXY, "proxy-host.com:8080");
Some proxies require user authentication before allowing a request, and you pass that information similar to this:
curl_easy_setopt(easyhandle, CURLOPT_PROXYUSERPWD, "user:password");
If you want to, you can specify the host name only in the CURLOPT_PROXY option, and set the port number separately with CURLOPT_PROXYPORT.
Tell libcurl what kind of proxy it is with CURLOPT_PROXYTYPE (if not, it will default to assume a HTTP proxy):
curl_easy_setopt(easyhandle, CURLOPT_PROXYTYPE, CURLPROXY_SOCKS4);
Environment Variables
libcurl automatically checks and uses a set of environment variables to know what proxies to use for certain protocols. The names of the variables are following an ancient de facto standard and are built up as "[protocol]_proxy" (note the lower casing). Which makes the variable 'http_proxy' checked for a name of a proxy to use when the input URL is HTTP. Following the same rule, the variable named 'ftp_proxy' is checked for FTP URLs. Again, the proxies are always HTTP proxies, the different names of the variables simply allows different HTTP proxies to be used.
The proxy environment variable contents should be in the format "[protocol://][user:password@]machine[:port]". Where the protocol:// part is simply ignored if present (so http://proxy and bluerk://proxy will do the same) and the optional port number specifies on which port the proxy operates on the host. If not specified, the internal default port number will be used and that is most likely *not* the one you would like it to be.
There are two special environment variables. 'all_proxy' is what sets proxy for any URL in case the protocol specific variable wasn't set, and 'no_proxy' defines a list of hosts that should not use a proxy even though a variable may say so. If 'no_proxy' is a plain asterisk ("*") it matches all hosts.
To explicitly disable libcurl's checking for and using the proxy environment variables, set the proxy name to "" - an empty string - with CURLOPT_PROXY.
SSL and Proxies
SSL is for secure point-to-point connections. This involves strong encryption and similar things, which effectively makes it impossible for a proxy to operate as a "man in between" which the proxy's task is, as previously discussed. Instead, the only way to have SSL work over a HTTP proxy is to ask the proxy to tunnel trough everything without being able to check or fiddle with the traffic.
Opening an SSL connection over a HTTP proxy is therefor a matter of asking the proxy for a straight connection to the target host on a specified port. This is made with the HTTP request CONNECT. ("please mr proxy, connect me to that remote host").
Because of the nature of this operation, where the proxy has no idea what kind of data that is passed in and out through this tunnel, this breaks some of the very few advantages that come from using a proxy, such as caching. Many organizations prevent this kind of tunneling to other destination port numbers than 443 (which is the default HTTPS port number).
Tunneling Through Proxy
As explained above, tunneling is required for SSL to work and often even restricted to the operation intended for SSL; HTTPS.
This is however not the only time proxy-tunneling might offer benefits to you or your application.
As tunneling opens a direct connection from your application to the remote machine, it suddenly also re-introduces the ability to do non-HTTP operations over a HTTP proxy. You can in fact use things such as FTP upload or FTP custom commands this way.
Again, this is often prevented by the administrators of proxies and is rarely allowed.
Tell libcurl to use proxy tunneling like this:
curl_easy_setopt(easyhandle, CURLOPT_HTTPPROXYTUNNEL, 1L);
In fact, there might even be times when you want to do plain HTTP operations using a tunnel like this, as it then enables you to operate on the remote server instead of asking the proxy to do so. libcurl will not stand in the way for such innovative actions either!
Proxy Auto-Config
Netscape first came up with this. It is basically a web page (usually using a .pac extension) with a Javascript that when executed by the browser with the requested URL as input, returns information to the browser on how to connect to the URL. The returned information might be "DIRECT" (which means no proxy should be used), "PROXY host:port" (to tell the browser where the proxy for this particular URL is) or "SOCKS host:port" (to direct the browser to a SOCKS proxy).
libcurl has no means to interpret or evaluate Javascript and thus it doesn't support this. If you get yourself in a position where you face this nasty invention, the following advice have been mentioned and used in the past:
- Depending on the Javascript complexity, write up a script that translates it to another language and execute that.
- Read the Javascript code and rewrite the same logic in another language.
- Implement a Javascript interpreter; people have successfully used the Mozilla Javascript engine in the past.
- Ask your admins to stop this, for a static proxy setup or similar.
Persistence Is The Way to Happiness
Re-cycling the same easy handle several times when doing multiple requests is the way to go.
After each single curl_easy_perform(3) operation, libcurl will keep the connection alive and open. A subsequent request using the same easy handle to the same host might just be able to use the already open connection! This reduces network impact a lot.
Even if the connection is dropped, all connections involving SSL to the same host again, will benefit from libcurl's session ID cache that drastically reduces re-connection time.
FTP connections that are kept alive save a lot of time, as the command- response round-trips are skipped, and also you don't risk getting blocked without permission to login again like on many FTP servers only allowing N persons to be logged in at the same time.
libcurl caches DNS name resolving results, to make lookups of a previously looked up name a lot faster.
Other interesting details that improve performance for subsequent requests may also be added in the future.
Each easy handle will attempt to keep the last few connections alive for a while in case they are to be used again. You can set the size of this "cache" with the CURLOPT_MAXCONNECTS option. Default is 5. There is very seldom any point in changing this value, and if you think of changing this it is often just a matter of thinking again.
To force your upcoming request to not use an already existing connection (it will even close one first if there happens to be one alive to the same host you're about to operate on), you can do that by setting CURLOPT_FRESH_CONNECT to 1. In a similar spirit, you can also forbid the upcoming request to be "lying" around and possibly get re-used after the request by setting CURLOPT_FORBID_REUSE to 1.
HTTP Headers Used by libcurl
When you use libcurl to do HTTP requests, it'll pass along a series of headers automatically. It might be good for you to know and understand these. You can replace or remove them by using the CURLOPT_HTTPHEADER option.
Host
This header is required by HTTP 1.1 and even many 1.0 servers and should be the name of the server we want to talk to. This includes the port number if anything but default.
Accept
"*/*".
Expect
When doing POST requests, libcurl sets this header to "100-continue" to ask the server for an "OK" message before it proceeds with sending the data part of the post. If the POSTed data amount is deemed "small", libcurl will not use this header.
Customizing Operations
There is an ongoing development today where more and more protocols are built upon HTTP for transport. This has obvious benefits as HTTP is a tested and reliable protocol that is widely deployed and has excellent proxy-support.
When you use one of these protocols, and even when doing other kinds of programming you may need to change the traditional HTTP (or FTP or...) manners. You may need to change words, headers or various data.
libcurl is your friend here too.
CUSTOMREQUEST
If just changing the actual HTTP request keyword is what you want, like when GET, HEAD or POST is not good enough for you, CURLOPT_CUSTOMREQUEST is there for you. It is very simple to use:
curl_easy_setopt(easyhandle, CURLOPT_CUSTOMREQUEST, "MYOWNREQUEST");
When using the custom request, you change the request keyword of the actual request you are performing. Thus, by default you make a GET request but you can also make a POST operation (as described before) and then replace the POST keyword if you want to. You're the boss.
Modify Headers
HTTP-like protocols pass a series of headers to the server when doing the request, and you're free to pass any amount of extra headers that you think fit. Adding headers is this easy:
struct curl_slist *headers=NULL; /* init to NULL is important */
headers = curl_slist_append(headers, "Hey-server-hey: how are you?");
headers = curl_slist_append(headers, "X-silly-content: yes");
/* pass our list of custom made headers */
curl_easy_setopt(easyhandle, CURLOPT_HTTPHEADER, headers);
curl_easy_perform(easyhandle); /* transfer http */
curl_slist_free_all(headers); /* free the header list */
... and if you think some of the internally generated headers, such as Accept: or Host: don't contain the data you want them to contain, you can replace them by simply setting them too:
headers = curl_slist_append(headers, "Accept: Agent-007");
headers = curl_slist_append(headers, "Host: munged.host.line");
Delete Headers
If you replace an existing header with one with no contents, you will prevent the header from being sent. For instance, if you want to completely prevent the "Accept:" header from being sent, you can disable it with code similar to this:
headers = curl_slist_append(headers, "Accept:");
Both replacing and canceling internal headers should be done with careful consideration and you should be aware that you may violate the HTTP protocol when doing so.
Enforcing chunked transfer-encoding
By making sure a request uses the custom header "Transfer-Encoding: chunked" when doing a non-GET HTTP operation, libcurl will switch over to "chunked" upload, even though the size of the data to upload might be known. By default, libcurl usually switches over to chunked upload automatically if the upload data size is unknown.
HTTP Version
All HTTP requests includes the version number to tell the server which version we support. libcurl speaks HTTP 1.1 by default. Some very old servers don't like getting 1.1-requests and when dealing with stubborn old things like that, you can tell libcurl to use 1.0 instead by doing something like this:
curl_easy_setopt(easyhandle, CURLOPT_HTTP_VERSION, CURL_HTTP_VERSION_1_0);
FTP Custom Commands
Not all protocols are HTTP-like, and thus the above may not help you when you want to make, for example, your FTP transfers to behave differently.
Sending custom commands to a FTP server means that you need to send the commands exactly as the FTP server expects them (RFC 959 is a good guide here), and you can only use commands that work on the control-connection alone. All kinds of commands that require data interchange and thus need a data-connection must be left to libcurl's own judgement. Also be aware that libcurl will do its very best to change directory to the target directory before doing any transfer, so if you change directory (with CWD or similar) you might confuse libcurl and then it might not attempt to transfer the file in the correct remote directory.
A little example that deletes a given file before an operation:
headers = curl_slist_append(headers, "DELE file-to-remove");
/* pass the list of custom commands to the handle */
curl_easy_setopt(easyhandle, CURLOPT_QUOTE, headers);
curl_easy_perform(easyhandle); /* transfer ftp data! */
curl_slist_free_all(headers); /* free the header list */
If you would instead want this operation (or chain of operations) to happen _after_ the data transfer took place the option to curl_easy_setopt(3) would instead be called CURLOPT_POSTQUOTE and used the exact same way.
The custom FTP command will be issued to the server in the same order they are added to the list, and if a command gets an error code returned back from the server, no more commands will be issued and libcurl will bail out with an error code (CURLE_QUOTE_ERROR). Note that if you use CURLOPT_QUOTE to send commands before a transfer, no transfer will actually take place when a quote command has failed.
If you set the CURLOPT_HEADER to 1, you will tell libcurl to get information about the target file and output "headers" about it. The headers will be in "HTTP-style", looking like they do in HTTP.
The option to enable headers or to run custom FTP commands may be useful to combine with CURLOPT_NOBODY. If this option is set, no actual file content transfer will be performed.
FTP Custom CUSTOMREQUEST
If you do want to list the contents of a FTP directory using your own defined FTP command, CURLOPT_CUSTOMREQUEST will do just that. "NLST" is the default one for listing directories but you're free to pass in your idea of a good alternative.
Cookies Without Chocolate Chips
In the HTTP sense, a cookie is a name with an associated value. A server sends the name and value to the client, and expects it to get sent back on every subsequent request to the server that matches the particular conditions set. The conditions include that the domain name and path match and that the cookie hasn't become too old.
In real-world cases, servers send new cookies to replace existing ones to update them. Server use cookies to "track" users and to keep "sessions".
Cookies are sent from server to clients with the header Set-Cookie: and they're sent from clients to servers with the Cookie: header.
To just send whatever cookie you want to a server, you can use CURLOPT_COOKIE to set a cookie string like this:
curl_easy_setopt(easyhandle, CURLOPT_COOKIE, "name1=var1; name2=var2;");
In many cases, that is not enough. You might want to dynamically save whatever cookies the remote server passes to you, and make sure those cookies are then used accordingly on later requests.
One way to do this, is to save all headers you receive in a plain file and when you make a request, you tell libcurl to read the previous headers to figure out which cookies to use. Set the header file to read cookies from with CURLOPT_COOKIEFILE.
The CURLOPT_COOKIEFILE option also automatically enables the cookie parser in libcurl. Until the cookie parser is enabled, libcurl will not parse or understand incoming cookies and they will just be ignored. However, when the parser is enabled the cookies will be understood and the cookies will be kept in memory and used properly in subsequent requests when the same handle is used. Many times this is enough, and you may not have to save the cookies to disk at all. Note that the file you specify to CURLOPT_COOKIEFILE doesn't have to exist to enable the parser, so a common way to just enable the parser and not read any cookies is to use the name of a file you know doesn't exist.
If you would rather use existing cookies that you've previously received with your Netscape or Mozilla browsers, you can make libcurl use that cookie file as input. The CURLOPT_COOKIEFILE is used for that too, as libcurl will automatically find out what kind of file it is and act accordingly.
Perhaps the most advanced cookie operation libcurl offers, is saving the entire internal cookie state back into a Netscape/Mozilla formatted cookie file. We call that the cookie-jar. When you set a file name with CURLOPT_COOKIEJAR, that file name will be created and all received cookies will be stored in it when curl_easy_cleanup(3) is called. This enables cookies to get passed on properly between multiple handles without any information getting lost.
FTP Peculiarities We Need
FTP transfers use a second TCP/IP connection for the data transfer. This is usually a fact you can forget and ignore but at times this fact will come back to haunt you. libcurl offers several different ways to customize how the second connection is being made.
libcurl can either connect to the server a second time or tell the server to connect back to it. The first option is the default and it is also what works best for all the people behind firewalls, NATs or IP-masquerading setups. libcurl then tells the server to open up a new port and wait for a second connection. This is by default attempted with EPSV first, and if that doesn't work it tries PASV instead. (EPSV is an extension to the original FTP spec and does not exist nor work on all FTP servers.)
You can prevent libcurl from first trying the EPSV command by setting CURLOPT_FTP_USE_EPSV to zero.
In some cases, you will prefer to have the server connect back to you for the second connection. This might be when the server is perhaps behind a firewall or something and only allows connections on a single port. libcurl then informs the remote server which IP address and port number to connect to. This is made with the CURLOPT_FTPPORT option. If you set it to "-", libcurl will use your system's "default IP address". If you want to use a particular IP, you can set the full IP address, a host name to resolve to an IP address or even a local network interface name that libcurl will get the IP address from.
When doing the "PORT" approach, libcurl will attempt to use the EPRT and the LPRT before trying PORT, as they work with more protocols. You can disable this behavior by setting CURLOPT_FTP_USE_EPRT to zero.
Headers Equal Fun
Some protocols provide "headers", meta-data separated from the normal data. These headers are by default not included in the normal data stream, but you can make them appear in the data stream by setting CURLOPT_HEADER to 1.
What might be even more useful, is libcurl's ability to separate the headers from the data and thus make the callbacks differ. You can for example set a different pointer to pass to the ordinary write callback by setting CURLOPT_WRITEHEADER.
Or, you can set an entirely separate function to receive the headers, by using CURLOPT_HEADERFUNCTION.
The headers are passed to the callback function one by one, and you can depend on that fact. It makes it easier for you to add custom header parsers etc.
"Headers" for FTP transfers equal all the FTP server responses. They aren't actually true headers, but in this case we pretend they are! ;-)
Post Transfer Information
[ curl_easy_getinfo ]
Security Considerations
The libcurl project takes security seriously. The library is written with caution and precautions are taken to mitigate many kinds of risks encountered while operating with potentially malicious servers on the Internet. It is a powerful library, however, which allows application writers to make trade offs between ease of writing and exposure to potential risky operations. If used the right way, you can use libcurl to transfer data pretty safely.
Many applications are used in closed networks where users and servers can be trusted, but many others are used on arbitrary servers and are fed input from potentially untrusted users. Following is a discussion about some risks in the ways in which applications commonly use libcurl and potential mitigations of those risks. It is by no means comprehensive, but shows classes of attacks that robust applications should consider. The Common Weakness Enumeration project at http://cwe.mitre.org/ is a good reference for many of these and similar types of weaknesses of which application writers should be aware.
Command Lines
If you use a command line tool (such as curl) that uses libcurl, and you give options to the tool on the command line those options can very likely get read by other users of your system when they use 'ps' or other tools to list currently running processes.
To avoid this problem, never feed sensitive things to programs using command line options. Write them to a protected file and use the -K option to avoid this.
.netrc
.netrc is a pretty handy file/feature that allows you to login quickly and automatically to frequently visited sites. The file contains passwords in clear text and is a real security risk. In some cases, your .netrc is also stored in a home directory that is NFS mounted or used on another network based file system, so the clear text password will fly through your network every time anyone reads that file!
To avoid this problem, don't use .netrc files and never store passwords in plain text anywhere.
Clear Text Passwords
Many of the protocols libcurl supports send name and password unencrypted as clear text (HTTP Basic authentication, FTP, TELNET etc). It is very easy for anyone on your network or a network nearby yours to just fire up a network analyzer tool and eavesdrop on your passwords. Don't let the fact that HTTP Basic uses base64 encoded passwords fool you. They may not look readable at a first glance, but they very easily "deciphered" by anyone within seconds.
To avoid this problem, use HTTP authentication methods or other protocols that don't let snoopers see your password: HTTP with Digest, NTLM or GSS authentication, HTTPS, FTPS, SCP, SFTP and FTP-Kerberos are a few examples.
Redirects
The CURLOPT_FOLLOWLOCATION option automatically follows HTTP redirects sent by a remote server. These redirects can refer to any kind of URL, not just HTTP. A redirect to a file: URL would cause the libcurl to read (or write) arbitrary files from the local filesystem. If the application returns the data back to the user (as would happen in some kinds of CGI scripts), an attacker could leverage this to read otherwise forbidden data (e.g. file://localhost/etc/passwd).
If authentication credentials are stored in the ~/.netrc file, or Kerberos is in use, any other URL type (not just file:) that requires authentication is also at risk. A redirect such as ftp://some-internal-server/private-file would then return data even when the server is password protected.
In the same way, if an unencrypted SSH private key has been configured for the user running the libcurl application, SCP: or SFTP: URLs could access password or private-key protected resources, e.g. sftp://user@some-internal-server/etc/passwd
The CURLOPT_REDIR_PROTOCOLS and CURLOPT_NETRC options can be used to mitigate against this kind of attack.
A redirect can also specify a location available only on the machine running libcurl, including servers hidden behind a firewall from the attacker. e.g. http://127.0.0.1/ or http://intranet/delete-stuff.cgi?delete=all or tftp://bootp-server/pc-config-data
Apps can mitigate against this by disabling CURLOPT_FOLLOWLOCATION and handling redirects itself, sanitizing URLs as necessary. Alternately, an app could leave CURLOPT_FOLLOWLOCATION enabled but set CURLOPT_REDIR_PROTOCOLS and install a CURLOPT_OPENSOCKETFUNCTION callback function in which addresses are sanitized before use.
Private Resources
A user who can control the DNS server of a domain being passed in within a URL can change the address of the host to a local, private address which a server-side libcurl-using application could then use. e.g. the innocuous URL http://fuzzybunnies.example.com/ could actually resolve to the IP address of a server behind a firewall, such as 127.0.0.1 or 10.1.2.3. Apps can mitigate against this by setting a CURLOPT_OPENSOCKETFUNCTION and checking the address before a connection.
All the malicious scenarios regarding redirected URLs apply just as well to non-redirected URLs, if the user is allowed to specify an arbitrary URL that could point to a private resource. For example, a web app providing a translation service might happily translate file://localhost/etc/passwd and display the result. Apps can mitigate against this with the CURLOPT_PROTOCOLS option as well as by similar mitigation techniques for redirections.
A malicious FTP server could in response to the PASV command return an IP address and port number for a server local to the app running libcurl but behind a firewall. Apps can mitigate against this by using the CURLOPT_FTP_SKIP_PASV_IP option or CURLOPT_FTPPORT.
IPv6 Addresses
libcurl will normally handle IPv6 addresses transparently and just as easily as IPv4 addresses. That means that a sanitizing function that filters out addressses like 127.0.0.1 isn't sufficient--the equivalent IPv6 addresses ::1, ::, 0:00::0:1, ::127.0.0.1 and ::ffff:7f00:1 supplied somehow by an attacker would all bypass a naive filter and could allow access to undesired local resources. IPv6 also has special address blocks like link-local and site-local that generally shouldn't be accessed by a server-side libcurl-using application. A poorly-configured firewall installed in a data center, organization or server may also be configured to limit IPv4 connections but leave IPv6 connections wide open. In some cases, the CURL_IPRESOLVE_V4 option can be used to limit resolved addresses to IPv4 only and bypass these issues.
Uploads
When uploading, a redirect can cause a local (or remote) file to be overwritten. Apps must not allow any unsanitized URL to be passed in for uploads. Also, CURLOPT_FOLLOWLOCATION should not be used on uploads. Instead, the app should handle redirects itself, sanitizing each URL first.
Authentication
Use of CURLOPT_UNRESTRICTED_AUTH could cause authentication information to be sent to an unknown second server. Apps can mitigate against this by disabling CURLOPT_FOLLOWLOCATION and handling redirects itself, sanitizing where necessary.
Use of the CURLAUTH_ANY option to CURLOPT_HTTPAUTH could result in user name and password being sent in clear text to an HTTP server. Instead, use CURLAUTH_ANYSAFE which ensures that the password is encrypted over the network, or else fail the request.
Use of the CURLUSESSL_TRY option to CURLOPT_USE_SSL could result in user name and password being sent in clear text to an FTP server. Instead, use CURLUSESSL_CONTROL to ensure that an encrypted connection is used or else fail the request.
Cookies
If cookies are enabled and cached, then a user could craft a URL which performs some malicious action to a site whose authentication is already stored in a cookie. e.g. http://mail.example.com/delete-stuff.cgi?delete=all Apps can mitigate against this by disabling cookies or clearing them between requests.
Dangerous URLs
SCP URLs can contain raw commands within the scp: URL, which is a side effect of how the SCP protocol is designed. e.g. scp://user:pass@host/a;date >/tmp/test; Apps must not allow unsanitized SCP: URLs to be passed in for downloads.
Denial of Service
A malicious server could cause libcurl to effectively hang by sending a trickle of data through, or even no data at all but just keeping the TCP connection open. This could result in a denial-of-service attack. The CURLOPT_TIMEOUT and/or CURLOPT_LOW_SPEED_LIMIT options can be used to mitigate against this.
A malicious server could cause libcurl to effectively hang by starting to send data, then severing the connection without cleanly closing the TCP connection. The app could install a CURLOPT_SOCKOPTFUNCTION callback function and set the TCP SO_KEEPALIVE option to mitigate against this. Setting one of the timeout options would also work against this attack.
A malicious server could cause libcurl to download an infinite amount of data, potentially causing all of memory or disk to be filled. Setting the CURLOPT_MAXFILESIZE_LARGE option is not sufficient to guard against this. Instead, the app should monitor the amount of data received within the write or progress callback and abort once the limit is reached.
A malicious HTTP server could cause an infinite redirection loop, causing a denial-of-service. This can be mitigated by using the CURLOPT_MAXREDIRS option.
Arbitrary Headers
User-supplied data must be sanitized when used in options like CURLOPT_USERAGENT, CURLOPT_HTTPHEADER, CURLOPT_POSTFIELDS and others that are used to generate structured data. Characters like embedded carriage returns or ampersands could allow the user to create additional headers or fields that could cause malicious transactions.
Server-supplied Names
A server can supply data which the application may, in some cases, use as a file name. The curl command-line tool does this with --remote-header-name, using the Content-disposition: header to generate a file name. An application could also use CURLINFO_EFFECTIVE_URL to generate a file name from a server-supplied redirect URL. Special care must be taken to sanitize such names to avoid the possibility of a malicious server supplying one like "/etc/passwd", "\autoexec.bat", "prn:" or even ".bashrc".
Server Certificates
A secure application should never use the CURLOPT_SSL_VERIFYPEER option to disable certificate validation. There are numerous attacks that are enabled by apps that fail to properly validate server TLS/SSL certificates, thus enabling a malicious server to spoof a legitimate one. HTTPS without validated certificates is potentially as insecure as a plain HTTP connection.
Showing What You Do
On a related issue, be aware that even in situations like when you have problems with libcurl and ask someone for help, everything you reveal in order to get best possible help might also impose certain security related risks. Host names, user names, paths, operating system specifics, etc. (not to mention passwords of course) may in fact be used by intruders to gain additional information of a potential target.
Be sure to limit access to application logs if they could hold private or security-related data. Besides the obvious candidates like user names and passwords, things like URLs, cookies or even file names could also hold sensitive data.
To avoid this problem, you must of course use your common sense. Often, you can just edit out the sensitive data or just search/replace your true information with faked data.
Multiple Transfers Using the multi Interface
The easy interface as described in detail in this document is a synchronous interface that transfers one file at a time and doesn't return until it is done.
The multi interface, on the other hand, allows your program to transfer multiple files in both directions at the same time, without forcing you to use multiple threads. The name might make it seem that the multi interface is for multi-threaded programs, but the truth is almost the reverse. The multi interface can allow a single-threaded application to perform the same kinds of multiple, simultaneous transfers that multi-threaded programs can perform. It allows many of the benefits of multi-threaded transfers without the complexity of managing and synchronizing many threads.
To use this interface, you are better off if you first understand the basics of how to use the easy interface. The multi interface is simply a way to make multiple transfers at the same time by adding up multiple easy handles into a "multi stack".
You create the easy handles you want and you set all the options just like you have been told above, and then you create a multi handle with curl_multi_init(3) and add all those easy handles to that multi handle with curl_multi_add_handle(3).
When you've added the handles you have for the moment (you can still add new ones at any time), you start the transfers by calling curl_multi_perform(3).
curl_multi_perform(3) is asynchronous. It will only execute as little as possible and then return back control to your program. It is designed to never block.
The best usage of this interface is when you do a select() on all possible file descriptors or sockets to know when to call libcurl again. This also makes it easy for you to wait and respond to actions on your own application's sockets/handles. You figure out what to select() for by using curl_multi_fdset(3), that fills in a set of fd_set variables for you with the particular file descriptors libcurl uses for the moment.
When you then call select(), it'll return when one of the file handles signal action and you then call curl_multi_perform(3) to allow libcurl to do what it wants to do. Take note that libcurl does also feature some time-out code so we advise you to never use very long timeouts on select() before you call curl_multi_perform(3), which thus should be called unconditionally every now and then even if none of its file descriptors have signaled ready. Another precaution you should use: always call curl_multi_fdset(3) immediately before the select() call since the current set of file descriptors may change when calling a curl function.
If you want to stop the transfer of one of the easy handles in the stack, you can use curl_multi_remove_handle(3) to remove individual easy handles. Remember that easy handles should be curl_easy_cleanup(3)ed.
When a transfer within the multi stack has finished, the counter of running transfers (as filled in by curl_multi_perform(3)) will decrease. When the number reaches zero, all transfers are done.
curl_multi_info_read(3) can be used to get information about completed transfers. It then returns the CURLcode for each easy transfer, to allow you to figure out success on each individual transfer.
SSL, Certificates and Other Tricks
[ seeding, passwords, keys, certificates, ENGINE, ca certs ]
Sharing Data Between Easy Handles
You can share some data between easy handles when the easy interface is used, and some data is share automatically when you use the multi interface.
When you add easy handles to a multi handle, these easy handles will automatically share a lot of the data that otherwise would be kept on a per-easy handle basis when the easy interface is used.
The DNS cache is shared between handles within a multi handle, making subsequent name resolving faster, and the connection pool that is kept to better allow persistent connections and connection re-use is also shared. If you're using the easy interface, you can still share these between specific easy handles by using the share interface, see libcurl-share(3).
Some things are never shared automatically, not within multi handles, like for example cookies so the only way to share that is with the share interface.
Footnotes
[1]
libcurl 7.10.3 and later have the ability to switch over to chunked Transfer-Encoding in cases where HTTP uploads are done with data of an unknown size.
[2]
This happens on Windows machines when libcurl is built and used as a DLL. However, you can still do this on Windows if you link with a static library.
[3]
The curl-config tool is generated at build-time (on UNIX-like systems) and should be installed with the 'make install' or similar instruction that installs the library, header files, man pages etc.
[4]
This behavior was different in versions before 7.17.0, where strings had to remain valid past the end of the curl_easy_setopt(3) call.
This HTML page was made with roffit.
curl-7.35.0/docs/libcurl/libcurl.m4 0000644 0001750 0001750 00000023671 12213173003 013757 0000000 0000000 # LIBCURL_CHECK_CONFIG ([DEFAULT-ACTION], [MINIMUM-VERSION],
# [ACTION-IF-YES], [ACTION-IF-NO])
# ----------------------------------------------------------
# David Shaw May-09-2006
#
# Checks for libcurl. DEFAULT-ACTION is the string yes or no to
# specify whether to default to --with-libcurl or --without-libcurl.
# If not supplied, DEFAULT-ACTION is yes. MINIMUM-VERSION is the
# minimum version of libcurl to accept. Pass the version as a regular
# version number like 7.10.1. If not supplied, any version is
# accepted. ACTION-IF-YES is a list of shell commands to run if
# libcurl was successfully found and passed the various tests.
# ACTION-IF-NO is a list of shell commands that are run otherwise.
# Note that using --without-libcurl does run ACTION-IF-NO.
#
# This macro #defines HAVE_LIBCURL if a working libcurl setup is
# found, and sets @LIBCURL@ and @LIBCURL_CPPFLAGS@ to the necessary
# values. Other useful defines are LIBCURL_FEATURE_xxx where xxx are
# the various features supported by libcurl, and LIBCURL_PROTOCOL_yyy
# where yyy are the various protocols supported by libcurl. Both xxx
# and yyy are capitalized. See the list of AH_TEMPLATEs at the top of
# the macro for the complete list of possible defines. Shell
# variables $libcurl_feature_xxx and $libcurl_protocol_yyy are also
# defined to 'yes' for those features and protocols that were found.
# Note that xxx and yyy keep the same capitalization as in the
# curl-config list (e.g. it's "HTTP" and not "http").
#
# Users may override the detected values by doing something like:
# LIBCURL="-lcurl" LIBCURL_CPPFLAGS="-I/usr/myinclude" ./configure
#
# For the sake of sanity, this macro assumes that any libcurl that is
# found is after version 7.7.2, the first version that included the
# curl-config script. Note that it is very important for people
# packaging binary versions of libcurl to include this script!
# Without curl-config, we can only guess what protocols are available,
# or use curl_version_info to figure it out at runtime.
AC_DEFUN([LIBCURL_CHECK_CONFIG],
[
AH_TEMPLATE([LIBCURL_FEATURE_SSL],[Defined if libcurl supports SSL])
AH_TEMPLATE([LIBCURL_FEATURE_KRB4],[Defined if libcurl supports KRB4])
AH_TEMPLATE([LIBCURL_FEATURE_IPV6],[Defined if libcurl supports IPv6])
AH_TEMPLATE([LIBCURL_FEATURE_LIBZ],[Defined if libcurl supports libz])
AH_TEMPLATE([LIBCURL_FEATURE_ASYNCHDNS],[Defined if libcurl supports AsynchDNS])
AH_TEMPLATE([LIBCURL_FEATURE_IDN],[Defined if libcurl supports IDN])
AH_TEMPLATE([LIBCURL_FEATURE_SSPI],[Defined if libcurl supports SSPI])
AH_TEMPLATE([LIBCURL_FEATURE_NTLM],[Defined if libcurl supports NTLM])
AH_TEMPLATE([LIBCURL_PROTOCOL_HTTP],[Defined if libcurl supports HTTP])
AH_TEMPLATE([LIBCURL_PROTOCOL_HTTPS],[Defined if libcurl supports HTTPS])
AH_TEMPLATE([LIBCURL_PROTOCOL_FTP],[Defined if libcurl supports FTP])
AH_TEMPLATE([LIBCURL_PROTOCOL_FTPS],[Defined if libcurl supports FTPS])
AH_TEMPLATE([LIBCURL_PROTOCOL_FILE],[Defined if libcurl supports FILE])
AH_TEMPLATE([LIBCURL_PROTOCOL_TELNET],[Defined if libcurl supports TELNET])
AH_TEMPLATE([LIBCURL_PROTOCOL_LDAP],[Defined if libcurl supports LDAP])
AH_TEMPLATE([LIBCURL_PROTOCOL_DICT],[Defined if libcurl supports DICT])
AH_TEMPLATE([LIBCURL_PROTOCOL_TFTP],[Defined if libcurl supports TFTP])
AH_TEMPLATE([LIBCURL_PROTOCOL_RTSP],[Defined if libcurl supports RTSP])
AH_TEMPLATE([LIBCURL_PROTOCOL_POP3],[Defined if libcurl supports POP3])
AH_TEMPLATE([LIBCURL_PROTOCOL_IMAP],[Defined if libcurl supports IMAP])
AH_TEMPLATE([LIBCURL_PROTOCOL_SMTP],[Defined if libcurl supports SMTP])
AC_ARG_WITH(libcurl,
AC_HELP_STRING([--with-libcurl=PREFIX],[look for the curl library in PREFIX/lib and headers in PREFIX/include]),
[_libcurl_with=$withval],[_libcurl_with=ifelse([$1],,[yes],[$1])])
if test "$_libcurl_with" != "no" ; then
AC_PROG_AWK
_libcurl_version_parse="eval $AWK '{split(\$NF,A,\".\"); X=256*256*A[[1]]+256*A[[2]]+A[[3]]; print X;}'"
_libcurl_try_link=yes
if test -d "$_libcurl_with" ; then
LIBCURL_CPPFLAGS="-I$withval/include"
_libcurl_ldflags="-L$withval/lib"
AC_PATH_PROG([_libcurl_config],[curl-config],[],
["$withval/bin"])
else
AC_PATH_PROG([_libcurl_config],[curl-config],[],[$PATH])
fi
if test x$_libcurl_config != "x" ; then
AC_CACHE_CHECK([for the version of libcurl],
[libcurl_cv_lib_curl_version],
[libcurl_cv_lib_curl_version=`$_libcurl_config --version | $AWK '{print $[]2}'`])
_libcurl_version=`echo $libcurl_cv_lib_curl_version | $_libcurl_version_parse`
_libcurl_wanted=`echo ifelse([$2],,[0],[$2]) | $_libcurl_version_parse`
if test $_libcurl_wanted -gt 0 ; then
AC_CACHE_CHECK([for libcurl >= version $2],
[libcurl_cv_lib_version_ok],
[
if test $_libcurl_version -ge $_libcurl_wanted ; then
libcurl_cv_lib_version_ok=yes
else
libcurl_cv_lib_version_ok=no
fi
])
fi
if test $_libcurl_wanted -eq 0 || test x$libcurl_cv_lib_version_ok = xyes ; then
if test x"$LIBCURL_CPPFLAGS" = "x" ; then
LIBCURL_CPPFLAGS=`$_libcurl_config --cflags`
fi
if test x"$LIBCURL" = "x" ; then
LIBCURL=`$_libcurl_config --libs`
# This is so silly, but Apple actually has a bug in their
# curl-config script. Fixed in Tiger, but there are still
# lots of Panther installs around.
case "${host}" in
powerpc-apple-darwin7*)
LIBCURL=`echo $LIBCURL | sed -e 's|-arch i386||g'`
;;
esac
fi
# All curl-config scripts support --feature
_libcurl_features=`$_libcurl_config --feature`
# Is it modern enough to have --protocols? (7.12.4)
if test $_libcurl_version -ge 461828 ; then
_libcurl_protocols=`$_libcurl_config --protocols`
fi
else
_libcurl_try_link=no
fi
unset _libcurl_wanted
fi
if test $_libcurl_try_link = yes ; then
# we didn't find curl-config, so let's see if the user-supplied
# link line (or failing that, "-lcurl") is enough.
LIBCURL=${LIBCURL-"$_libcurl_ldflags -lcurl"}
AC_CACHE_CHECK([whether libcurl is usable],
[libcurl_cv_lib_curl_usable],
[
_libcurl_save_cppflags=$CPPFLAGS
CPPFLAGS="$LIBCURL_CPPFLAGS $CPPFLAGS"
_libcurl_save_libs=$LIBS
LIBS="$LIBCURL $LIBS"
AC_LINK_IFELSE([AC_LANG_PROGRAM([[#include ]],[[
/* Try and use a few common options to force a failure if we are
missing symbols or can't link. */
int x;
curl_easy_setopt(NULL,CURLOPT_URL,NULL);
x=CURL_ERROR_SIZE;
x=CURLOPT_WRITEFUNCTION;
x=CURLOPT_FILE;
x=CURLOPT_ERRORBUFFER;
x=CURLOPT_STDERR;
x=CURLOPT_VERBOSE;
if (x) ;
]])],libcurl_cv_lib_curl_usable=yes,libcurl_cv_lib_curl_usable=no)
CPPFLAGS=$_libcurl_save_cppflags
LIBS=$_libcurl_save_libs
unset _libcurl_save_cppflags
unset _libcurl_save_libs
])
if test $libcurl_cv_lib_curl_usable = yes ; then
# Does curl_free() exist in this version of libcurl?
# If not, fake it with free()
_libcurl_save_cppflags=$CPPFLAGS
CPPFLAGS="$CPPFLAGS $LIBCURL_CPPFLAGS"
_libcurl_save_libs=$LIBS
LIBS="$LIBS $LIBCURL"
AC_CHECK_FUNC(curl_free,,
AC_DEFINE(curl_free,free,
[Define curl_free() as free() if our version of curl lacks curl_free.]))
CPPFLAGS=$_libcurl_save_cppflags
LIBS=$_libcurl_save_libs
unset _libcurl_save_cppflags
unset _libcurl_save_libs
AC_DEFINE(HAVE_LIBCURL,1,
[Define to 1 if you have a functional curl library.])
AC_SUBST(LIBCURL_CPPFLAGS)
AC_SUBST(LIBCURL)
for _libcurl_feature in $_libcurl_features ; do
AC_DEFINE_UNQUOTED(AS_TR_CPP(libcurl_feature_$_libcurl_feature),[1])
eval AS_TR_SH(libcurl_feature_$_libcurl_feature)=yes
done
if test "x$_libcurl_protocols" = "x" ; then
# We don't have --protocols, so just assume that all
# protocols are available
_libcurl_protocols="HTTP FTP FILE TELNET LDAP DICT TFTP"
if test x$libcurl_feature_SSL = xyes ; then
_libcurl_protocols="$_libcurl_protocols HTTPS"
# FTPS wasn't standards-compliant until version
# 7.11.0 (0x070b00 == 461568)
if test $_libcurl_version -ge 461568; then
_libcurl_protocols="$_libcurl_protocols FTPS"
fi
fi
# RTSP, IMAP, POP3 and SMTP were added in
# 7.20.0 (0x071400 == 463872)
if test $_libcurl_version -ge 463872; then
_libcurl_protocols="$_libcurl_protocols RTSP IMAP POP3 SMTP"
fi
fi
for _libcurl_protocol in $_libcurl_protocols ; do
AC_DEFINE_UNQUOTED(AS_TR_CPP(libcurl_protocol_$_libcurl_protocol),[1])
eval AS_TR_SH(libcurl_protocol_$_libcurl_protocol)=yes
done
else
unset LIBCURL
unset LIBCURL_CPPFLAGS
fi
fi
unset _libcurl_try_link
unset _libcurl_version_parse
unset _libcurl_config
unset _libcurl_feature
unset _libcurl_features
unset _libcurl_protocol
unset _libcurl_protocols
unset _libcurl_version
unset _libcurl_ldflags
fi
if test x$_libcurl_with = xno || test x$libcurl_cv_lib_curl_usable != xyes ; then
# This is the IF-NO path
ifelse([$4],,:,[$4])
else
# This is the IF-YES path
ifelse([$3],,:,[$3])
fi
unset _libcurl_with
])dnl
curl-7.35.0/docs/libcurl/curl_share_cleanup.html 0000644 0001750 0001750 00000003670 12272124467 016621 0000000 0000000
curl_share_cleanup man page
NAME
curl_share_cleanup - Clean up a shared object
SYNOPSIS
#include <curl/curl.h>
CURLSHcode curl_share_cleanup(CURLSH * share_handle );
DESCRIPTION
This function deletes a shared object. The share handle cannot be used anymore when this function has been called.
RETURN VALUE
CURLSHE_OK (zero) means that the option was set properly, non-zero means an error occurred as <curl/curl.h> defines. See the libcurl-errors.3 man page for the full list with descriptions. If an error occurs, then the share object will not be deleted.
SEE ALSO
curl_share_init (3) curl_share_setopt (3)
This HTML page was made with roffit.
curl-7.35.0/docs/libcurl/curl_multi_assign.pdf 0000644 0001750 0001750 00000010761 12272124475 016311 0000000 0000000 %PDF-1.4
%Çì¢
5 0 obj
<>
stream
xœ½WÛnÛH}×W4°¡«ÓÍ;1‹4c¡À¹¬dØ‹€&[Ç©á%‚þa~eÿqOu“Å8ÉÛÀ†%³›¬S§NjþÉ—LÐO÷™ìg¯n¶g‚mgΤ^dÝG²g¿±!¤ ëÍÌÜ#Y`³ rx±õ~&eÈ=|;Îî¤ò/û6o²/q]gÛâÁr æ,Ï ie¾°=Á…¬·qÑÆ9{~ûü¿ë7³…à¶ÄS„žG !p|¶¾™Yï–ó@ŒUé!¸Tëtf½½ž¯ÿáµwEÀÒ¦eñ Œì¬V
Kã&fMÉp±L²¸ÉÊ‚ ³fÇâ‚eE£ªˆ±ô4—ÂRFymp éóPc¹ûüîý‡»ÕÝ%"½E£±þ‘IÞ¦Šý“½¢?|÷+m·]JrýòÞzýñöæmRbÓ3TéEöÒ\ÜÅEš«+³O£ŒxzŽ¨_{“^
Ôu°|-)®&4~Ãf–²—tß¡© 濘<ÆéJp Ž2þýúîõíêÃzõþÝ÷’¨$û+éb
а ѾA&l ½3f<ôF[MDa;ˆÈM›9!¼É•+«Ís¢E†îÀG'ZñŒ`'4Ü{– µ²ºx¡
†ëÐPy(£^úÍX¾hÓh`=¯Tœž¨QqöxêýœÊ;îb]•J¡u²ª*èÓó¬Ž)
ŠŽX³g ¹{#m3rW.¤YJ j\Cµ²b›Ÿ;§7ÔÝØó´àW¸ ‹Žû&kÕ;`G>Ôø?㾂ñ7Ù^
2ë\x“áRÇûo¨yÙÇO:vÇ}èÃ"„ æyî-è%ëF¨ž€-¾£©i½Èã#Neä kÜ™¥*f;U‘i.âÆ26Ù‡©|©ÈéúYa¼URߺ?±º‘ÃÁ¥¨.÷
ûà´È%~,Û†©‹. ߊ¼Ÿuå§EcU'ã SŠ(à¾;š2Âuô6c &6¹•É~ùaejR(ˆˆ¬½!Ãêu˜@»hÍŽ
ÛÒ’e
É0Qô%îúa×gü¿ÓÃæñÝYyüéæeùÔ :õdðÌ?89Ü[·×ë·ïا¹t\ ùÒZÞ|¼žã©uÝ ¸JÙùÈ@áÌèÔ7É F º9í«ùOŽ2ðùÃêõò†}¼[Î=@
ìÈú×÷ÑÑ-Ðé¯`¬9 0ÉòñHc§²%Ë.ñ¯¢nª6i¡P¹"Å“ÕzØS†•´À>[¤§"Þg‰9¬Q‚*Nv¦áÀ¼k»<œ‹¦Zô/UKâHg Ä:Ý£¾ôØØø™I£„Õtd@û< ÿ¦y «ùv37ð¸{îüNò÷fø–m5ØPhGd,ú9HRkƒ„úÏn®Œl<eïWôd8€ïrÛéÉ=ž cĎ짅îî“>3•`¬êÏÌpõÈëìå¨ -¥õúÞ®«EÓÕ TtÁñ¶!†£ÝÕq|z°ÁG»Šc:Ò¤^ØÙ a“Qê8<°}ûÛ"ŽßI.Êâ´ãu+å1Ê›ü!®š,ió¸22Å42j£Ât·,ÁŒjW¢Ñ¡áK¼¶„8‡L&Ëd¨ÄÛ9:1t¥ÂŠ+zpZb¼_Θ0}Åš]vÕ¼ás˜? [»¡…Ì ÉZå_ç’`{®ÕÏBr-4}Ó[H—FËÙ†°O,?±å dùžì«·ºYþ¶ºY?OúÈ㎆J/ßAF&€º¤)òÉÎCÇiî
¦ÕìÊv»c7K•Úc[m\þÔŸü~ôVx}Í–7wïÏoS“·Â±‡¨¦<4—‰ çû†±´0¯.Ÿ„@¾>/_:Ò¸"ó|ê˜püdc2‚Ì.3 G„@ £Ó¤n–ûGôæ,#ÉðüÒ3[_ßè„Üuû;$]º^ÏþŸÿƒˆ;endstream
endobj
6 0 obj
1772
endobj
4 0 obj
<>
/Contents 5 0 R
>>
endobj
3 0 obj
<< /Type /Pages /Kids [
4 0 R
] /Count 1
>>
endobj
1 0 obj
<>
endobj
7 0 obj
<>endobj
11 0 obj
<>
endobj
12 0 obj
<>
endobj
10 0 obj
<>
endobj
9 0 obj
<>
endobj
8 0 obj
<>
endobj
13 0 obj
<>
endobj
14 0 obj
<>stream
2014-01-29T08:09:49+01:00
2014-01-29T08:09:49+01:00
groff version 1.22.2