| Age | Commit message (Collapse) | Author | 
|---|
|  | Fix qssl.c wrong error message
Upgrade OS400 wrappers and makefiles to 7.18.1 | 
|  | Define HAVE_GSSMIT if <gssapi/{gssapi.h,gssapi_generic.h,gssapi_krb5.h}> are
  available, otherwise define HAVE_GSSHEIMDAL if <gssapi.h> is available.
  Only define GSS_C_NT_HOSTBASED_SERVICE to gss_nt_service_name if
  GSS_C_NT_HOSTBASED_SERVICE isn't declared by the gssapi headers. This should
  avoid breakage in case we wrongly recognize Heimdal as MIT again. | 
|  |  | 
|  | assumes proxies to use | 
|  | message when libcurl doesn't get a 220 back immediately on connect, I now
  changed it to be more specific on what the problem is. Also worth noticing:
  while the bug report contains an example where the response is:
    421 There are too many connected users, please try again later
  we cannot assume that the error message will always be this readable nor
  that it fits within a particular boundary etc. | 
|  | GET simply because previously when you set CURLOPT_NOBODY to TRUE first and
  then FALSE you'd end up in a broken state where a HTTP request would do a
  HEAD by still act a lot like for a GET and hang waiting for the content etc. | 
|  |  | 
|  |  | 
|  | $capath is known to configure, so it can be defined in config.h instead. | 
|  |  | 
|  | application to provide data for a multipart with the read callback. Note
  that the size needs to be provided with CURLFORM_CONTENTSLENGTH when the
  stream option is used. This feature is verified by the new test case
  554. This feature was sponsored by Xponaut. | 
|  | the progress callback for the first (potentially huge) piece of body data
  sent together with the POST request headers in the initial send(). | 
|  | libcurl wasn't built to use OpenSSL as that is a prerequisite for this
  option to function! | 
|  | case 617 (which was added by Daniel Fandrich 5 Mar 2008). | 
|  | default instead of a ca bundle. The configure script will also look for a
  ca path if no ca bundle is found and no option given.
- Fixed detection of previously installed curl-ca-bundle.crt | 
|  |  | 
|  | - Added macros for curl_share_setopt and curl_multi_setopt to check at least
  the correct number of arguments. | 
|  | CURLOPT_FTP_CREATE_MISSING_DIRS to create a directory, and then re-used the
  handle and uploaded another file to another directory that needed to be
  created, the second upload would fail. Another case of a state variable that
  wasn't properly reset between requests. | 
|  | a single state variable to make the code easier to follow and understand. | 
|  | (http://curl.haxx.se/bug/view.cgi?id=1911069) that identified a race
  condition in the name resolver code when the DNS cache is shared between
  multiple easy handles, each running in simultaneous threads that could cause
  crashes. | 
|  | works in C mode atm (http://curl.haxx.se/mail/lib-2008-02/0267.html ,
  http://curl.haxx.se/mail/lib-2008-02/0292.html ) | 
|  | easy handle if curl_easy_reset() was used between them. I fixed it and Brian
  verified that it cured his problem.
- Brian Ulm reported that if you first tried to download a non-existing SFTP
  file and then fetched an existing one and re-used the handle, libcurl would
  still report the second one as non-existing as well! I fixed it abd Brian
  verified that it cured his problem. | 
|  | _USE_32BIT_TIME_T has been defined to get a 32-bit time_t | 
|  | select/poll calls will only be retried upon EINTR failures as
it previously was in lib/select.c revision 1.29
In this way Curl_socket_ready() and Curl_poll() will again fail
on any select/poll errors different than EINTR. | 
|  |  | 
|  | a re-used connection where both requests used Negotiate. | 
|  |  | 
|  |  | 
|  |  | 
|  | in the project. | 
|  | Patch submitted by Kaspar Brand. | 
|  | forces it to prefer SSLv3. | 
|  | http://curl.haxx.se/bug/feature.cgi?id=1900014 that makes libcurl (built to
  use OpenSSL) support a full chain of certificates in a given PKCS12
  certificate. | 
|  | happened if you set the connection cache size to 1 and for example failed to
  login to an FTP site. Bug report #1896698
  (http://curl.haxx.se/bug/view.cgi?id=1896698) | 
|  |  | 
|  |  | 
|  | better control at the exact state of the connection's SSL status so that we
  know exactly when it has completed the SSL negotiation or not so that there
  won't be accidental re-uses of connections that are wrongly believed to be
  in SSL-completed-negotiate state. | 
|  | such as the CURLOPT_SSL_CTX_FUNCTION one treat that as if it was a Location:
  following. The patch that introduced this feature was done for 7.11.0, but
  this code and functionality has been broken since about 7.15.4 (March 2006)
  with the introduction of non-blocking OpenSSL "connects".
  It was a hack to begin with and since it doesn't work and hasn't worked
  correctly for a long time and nobody has even noticed, I consider it a very
  suitable subject for plain removal. And so it was done. | 
|  | http://sourceforge.net/tracker/index.php?func=detail&aid=1767276&group_id=976&atid=350976
Submitted by Kaspar Brand. | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  | 'enumerated type mixed with another type'
and
  'variable was set but never used' | 
|  | get a fresh one downloaded and created with 'make ca-bundle' or you can get
  one from here => http://curl.haxx.se/docs/caextract.html if you want a fresh
  new one extracted from Mozilla's recent list of ca certs.
  The configure option --with-ca-bundle now lets you specify what file to use
  as default ca bundle for your build. If not specified, the configure script
  will check a few known standard places for a global ca cert to use. | 
|  |  | 
|  | DONE before the entire request operation is complete and thus we can't know in
what state it is for re-using, so we're forced to close it. In a perfect world
we can add code that keep track of if we really must close it here or not, but
currently we have no such detail knowledge.
Jerome Muffat-Meridol helped us work this out. | 
|  | premature set TRUE, which means it was done before the request comleted. It
could then very well not have received any data. | 
|  |  | 
|  |  |