Searched refs:whatever (Results 1 – 19 of 19) sorted by relevance
104 Content-Type: text/whatever116 Content-Type: text/whatever188 Content-Type: text/whatever200 Content-Type: text/whatever
32 …"{\"field1\":\"value1\",\"field2\":\"value2\"}" -F 'b=" \\value1;type=\"whatever\" "; type=text/fo…101 \value1;type="whatever"
36 0, disabled - use whatever the system thinks is fine
28 Pass a *pointer* to whatever you want passed in to your
57 /* allow whatever auth the proxy speaks */
55 NULL, use whatever the TCP stack finds suitable
39 We do not care about what version the library uses. libcurl uses whatever it
54 The *clientp* pointer contains whatever user-defined value set using the
60 The *clientp* pointer contains whatever user-defined value set using the
137 /* allow whatever auth the server speaks */
33 filename is set, content data is processed as a file, whatever is the part's
58 void *whatever; /* message-specific data */
39 read/write whatever there is to read or write right now etc.
71 curl_easy_perform(3) on the handle or whatever you think is
454 specific types) which allows libcurl to use whatever method it wants.1169 To just send whatever cookie you want to a server, you can use1176 In many cases, that is not enough. You might want to dynamically save whatever
105 void *whatever; /* message-specific data */ member
769 If for whatever reason you are not happy with these default choices that curl1141 whatever you want. You do not have to write the received data to a file.
2314 d whatever * overlay(data) void *
4568 dnl now deal with whatever we found
Completed in 85 milliseconds
