On Wed, Apr 11, 2007 at 03:15:54AM +0530, kuriakose wrote:
> New releases should not mask already working functionality in old releases .
> If it does it can cause surprise .

In this case, it looks like a bug that was fixed, not functionality that
was lost.

> > This failed to use ftp-ssl but silently ignored that and proceeded
> > with normal ftp.
> Please say if this is what you meant.
> Since in 1st case it is a lower version of libcurl(7.15.1) it ignored
> ftp-ssl and proceeded with normal ftp . But in 2nd case it is a higher
> version which proceeds only if ftp-ssl otherwise bails out since it couldn't
> use ftp-ssl. Hence you meant this was an intended change in the new version.

Version 7.15.4 included a change that appears to have fixed curl to
actual err out when SSL couldn't be negotiated, instead of the previous
behaviour which you witnessed that allowed the transfer to continue
unencrypted. This fix makes this option work as documented.

>>> Dan

-- 
http://www.MoveAnnouncer.com              The web change of address service
          Let webmasters know that your web site has moved