There are two kinds of state will cause the SSL certification:
CURLM_STATE_WAITPROXYCONNECT and CURLM_STATE_WAITCONNECT. I think you mean
CURLM_STATE_WAITPROXYCONNECT using non blocking, and CURLM_STATE_WAITCONNECT
using blocking mode, processing the remaining work.
However, if through the HTTPS proxy to access the FTPS server, if the
CURLM_STATE_WAITPROXYCONNECT state SSL authentication is successful, the FTPS
server will give the client returns "220 FTP server ready" message, and under
the condition of CURLM_STATE_WAITCONNECT, there will be re second SSL
certification, and the "220 FTP server ready" message will use second
authentication failure.
I think CURLM_STATE_WAITPROXYCONNECT and CURLM_STATE_WAITCONNECT two kinds of
state SSL certification should be related to. If the
CURLM_STATE_WAITPROXYCONNECT state, SSL authentication is successful, you do
not need to CURLM_STATE_WAITCONNECT, again SSL certification. If the
CURLM_STATE_WAITPROXYCONNECT state, the SSL certification is not completed,
then the CURLM_STATE_WAITCONNECT state to the SSL certification.
------------------ 原始邮件 ------------------
发件人: "Daniel Stenberg";<[email protected]>;
发送时间: 2015年1月22日(星期四) 凌晨5:59
收件人: "libcurl development"<[email protected]>;
主题: Re: 回复： FTPS:Failed to access FTPS through a HTTP proxyserver(v7.40.0)
On Mon, 19 Jan 2015, 无有先生 wrote:
> Annex I amendments, please check.
Thanks!
Your patch suggests we add a special exception for FTPS when connecting over
HTTP. But this doesn't look like it is FTPS specific! It looks like it
probably should be done like this for every TLS based protocol that isn't
HTTP. Do you agree?
--
/ daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
