- Nov 06, 2011
-
-
Rene Bernhardt authored
If a proxy offers several Authentication schemes where NTLM and Negotiate are offered by the proxy and you tell libcurl not to use the Negotiate scheme then the request never returns when the proxy answers with its HTTP 407 reply. It is reproducible by the following steps: - Use a proxy that offers NTLM and Negotiate ( CURLOPT_PROXY and CURLOPT_PROXYPORT ) - Tell libcurl NOT to use Negotiate CURL_EASY_SETOPT(CURLOPT_PROXYAUTH, CURLAUTH_BASIC | CURLAUTH_DIGEST | CURLAUTH_NTLM ) - Start the request The call to CURL_EASY_PERFORM never returns. If you switch on debug logging you can see that libcurl issues a new request As soon as it received the 407 reply. Instead it should return and set the response code to 407. Bug: http://curl.haxx.se/mail/lib-2011-10/0323.html
-
- Nov 04, 2011
-
-
Yang Tse authored
Move calling of ERR_remove_state(0) a.k.a ERR_remove_thread_state(NULL) from Curl_ossl_close_all() to Curl_ossl_cleanup(). In this way ERR_remove_state(0) is now only called in libcurl by curl_global_cleanup(). Previously it would get called by functions curl_easy_cleanup(), curl_multi_cleanup and potentially each time a connection was removed from a connection cache leading to premature destruction of OpenSSL's thread local state hash. Multi-threaded apps using OpenSSL enabled libcurl should still call function ERR_remove_state(0) or ERR_remove_thread_state(NULL) at the very end end of threads that do not call curl_global_cleanup().
-
- Nov 03, 2011
-
-
Yang Tse authored
-
Yang Tse authored
-
Yang Tse authored
-
Daniel Stenberg authored
Now called 'use_ssl' instead, which better matches the current CURLOPT name and since the option is used for all pingpong protocols (at least) it makes sense to not use 'ftp' in the name.
-
- Nov 02, 2011
-
-
Daniel Stenberg authored
Use gnutls_priority_set_direct() instead of gnutls_protocol_set_priority(). Remove the gnutls_certificate_type_set_priority() use since x509 is the default certificate type anyway. Reported by: Vincent Torri
-
Yang Tse authored
-
Yang Tse authored
Make NODATACONN425 and NODATACONN421 return a 150 positive preliminary reply before 425 or 421. New NODATACONN150 returns 150 without further positive nor negative reply Now NODATACONN doesn't reply anything at all.
-
- Nov 01, 2011
- Oct 31, 2011
- Oct 30, 2011
-
-
Dave Reisner authored
Try to be a little more descriptive about the effect of this flag, rather than parroting what was said in the paragraph just above.
-
Yang Tse authored
Some torture tests left FTP test server in an unresponsive state, resulting in torture tests that actually completed following unexpected code paths. Changes in this commit solely address this issue and some adjustments for ftpserver.pl logging relative to data channel establishment and tear down. Pending NODATACONN relative adjustments reserved for a further commit.
-
Yang Tse authored
Ensure verification takes place with no server commands file. Ignore verbose setting for running server precheck. Tweak unresponsive server message, to allow detection by haxx.se scripts.
-
- Oct 29, 2011
-
-
Yang Tse authored
-
- Oct 28, 2011
-
-
Yang Tse authored
Fix called sub when checking TFTP server, and adjust message.
-
- Oct 27, 2011
-
-
Yang Tse authored
Extended server checks to others in addition to pingpong when torture testing.
-
Yang Tse authored
-
Yang Tse authored
NODATACONN421: applies only to active FTP mode, instructs server to not establish data connection back to client and reply with FTP 421. NODATACONN425: applies only to active FTP mode, instructs server to not establish data connection back to client and reply with FTP 425. NODATACONN: applies to both active and passive FTP modes, instructs server to not establish nor accept a data channel and fool client into believing that the data channel connection is possible. Some polishing probably required.
-
Yang Tse authored
Fix curl_multi_cleanup() segfault when using weird cleanup sequence.
-
Daniel Stenberg authored
This extends the fix from commit d7934b8b When the multi state is changed within the multi_runsingle from DOING to DO_MORE, we didn't immediately start the FTP state machine again. That then left the FTP state in FTP_STOP. When curl_multi_fdset() was subsequently called, the ftp_domore_getsock() function would return the wrong fd info. Reported by: Gokhan Sengun
-
Daniel Stenberg authored
-
- Oct 26, 2011
-
-
Yang Tse authored
-
Yang Tse authored
-
Patrick Monnerat authored
-
- Oct 25, 2011
-
-
Daniel Stenberg authored
5 more bug fixes, 4 additional contributors
-
Yang Tse authored
When running torture tests, verify before each test case that required pingpong servers which are supposed to be alive are actually responsive. If found not responsive then restart them.
-
- Oct 24, 2011
-
-
Daniel Stenberg authored
I created test 587 in commit 840eff44 but forgot to add the file to the tarball. Added now.
-
Daniel Stenberg authored
This is using the verbatim 525 test code but it disables EPRT in the server and this should work just as well anyway.
-
Daniel Stenberg authored
EPRT is now supported by default by the server. To disable it, use the generic REPLY instruction in the <servercmd> tag. Test 116 now has it disabled. All other existing active FTP port tests strip out the port commands from the logs already so the change of the server isn't that noticable.
-
Yang Tse authored
-
Yang Tse authored
-
Daniel Stenberg authored
As commit 5850cc48 clarifies, libcurl can deliver header lines that are longer than CURL_MAX_WRITE_SIZE, only body data is limited to that size. The curl tool has check (when built debug-enabled) that made the wrong checks and this new test 1205 verifies that larger headers work.
-
Daniel Stenberg authored
Mention this maximum header size for the header callback cases
-
Daniel Stenberg authored
make sure the static build uses the static build option!
-
- Oct 23, 2011
-
-
Daniel Stenberg authored
shoot, Dan Fandrich already had this pointed out...
-
Steve Holme authored
Added pop3 username and password example as well as an explanation of how path part of the URL is used under pop3. Additionally have corrected a couple of typos.
-