Way too much logging for WebSocket connections? CURLE_AGAIN?

Hello, we establish a WebSocket connection using libcurl (7.61.0) (easy interface). With activated logging, schannel (Windows) is logging many thousand entries like this: 2019-02-07 15:19:18-0107 [5044]:[tWs]: VERB: CURL: schannel: client wants to read 16384 bytes 2019-02-07 15:19:18-0108

Re: CURLOPT_LOGIN_OPTIONS to select multiple ones?

Am 05.07.2018 um 15:39 schrieb Daniel Stenberg: On Thu, 5 Jul 2018, Volker Schmid wrote: Try "AUTH=NTLM;AUTH=CRAM-MD5;AUTH=LOGIN;AUTH=PLAIN" thanks, this is really working and solved my problem! Would be really great if the libcurl documentation would mention that option he

Re: CURLOPT_LOGIN_OPTIONS to select multiple ones?

: On 07/05/2018 11:35 AM, Volker Schmid wrote: > > > Am 03.07.2018 um 17:06 schrieb Volker Schmid: >> >> So, how to simply exclude GSSAPI or make CURLOPT_LOGIN_OPTIONS >> accepting multiple values like "AUTH=NTLM CRAM-MD5 LOGIN PLAIN"? >> Try "AUT

Re: CURLOPT_LOGIN_OPTIONS to select multiple ones?

login? Maybe some compiler switches or curl_easyopt function? Best, Volker Am 03.07.2018 um 17:06 schrieb Volker Schmid: Hello, a mailserver is offering those algorithms after STARTTLS: 250-AUTH GSSAPI NTLM LOGIN Now, libcurl GSSAPI seems broken and it fails due to this. The initial idea

CURLOPT_LOGIN_OPTIONS to select multiple ones?

Hello, a mailserver is offering those algorithms after STARTTLS: 250-AUTH GSSAPI NTLM LOGIN Now, libcurl GSSAPI seems broken and it fails due to this. The initial idea was to stop libcurl from using GSSAPI, but I found no option to exclude such for SMTP. So I tried to force libcurl to use

Unable to login to mailserver / AUTH GSSAPI?

Hello, a customer is trying to connect to a mailserver and fails. But looking to the logfile everything seems fine to me but it still fails. Sadly, I have no clue about why. This is the CURL log. Any ideas what's wrong here? I assume it may be the AUTH GSSAPI method, but I'm not sure. It was

Re: Questions regarding curl_easy with SSL and multi threaded

Hello Daniel, thanks for the detailed reply. > - I wonder about, how to deal with this if libcurl is not using OpenSSL (eg > on Windows using schannel and whatever libcurl is using on Linux or MacOS)? Only a subset of the TLS backends require mutex callbacks set. libcurl built with schannel

Questions regarding curl_easy with SSL and multi threaded

Hello, In my software I create a pool of curl-easy handles and re-use them in several threads. On MacOS I have crashes but on Windows and Linux it works fine. I did some research and found the threaded-ssl.c example at https://curl.haxx.se/libcurl/c/threaded-ssl.html. Now I have several

schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) The revocation function was unable to check revocation because the revocation server was offline.

Hello, We use libCurl version 7.43.0 with schannel support for TLS. Some customers using a proxy are getting the following issue: 2016-03-22 14:20:04-1274 [4736]: VERB: CURL: timeout on name lookup is not supported 2016-03-22 14:20:04-1283 [4736]: VERB: CURL: Trying 10.1.21.217...

Re: CURLOPT_CAPATH returning CURLE_NOT_BUILT_IN on MacOS 10.10

Am 27.08.2015 um 06:37 schrieb Nick Zitzmann: On Aug 26, 2015, at 4:15 AM, Volker Schmid volker.sch...@regify.com wrote: Thanks for the answer. Ok, I understand. But on MacOS I also do not have some cacerts.pem file usable with CURLOPT_CAINFO. So how to make this working? Or do I need

Re: CURLOPT_CAPATH returning CURLE_NOT_BUILT_IN on MacOS 10.10

Am 25.08.2015 um 22:50 schrieb Daniel Stenberg: On Tue, 25 Aug 2015, Volker Schmid wrote: Version:7.43.0 Host: i386-apple-darwin14.0 SSL Version: SecureTransport ZLib version: 1.2.5 Features: CURL_VERSION_SSL + CURL_VERSION_NTLM + CURL_VERSION_IPV6 + CURL_VERSION_LIBZ + CURL_VERSION_ASYNCHDNS

CURLOPT_CAPATH returning CURLE_NOT_BUILT_IN on MacOS 10.10

Hello, a customer of mine is using my software on MacOS 10.10 (he said he updated a few days ago to the most recent). I utilize the libcurl.dylib that the system is giving to me. Interestingly, I get this information after initialization (curl_version_info(CURLVERSION_NOW)): Version:7.43.0

Curl ES 60: Invalid certificate chain on MacOS 10.10.3 (Yosemite)

Hello all, I have a specific problem at a customer. Our software is calling a https:// domain using libcurl. No proxy. The system states curl 7.30.0. We are calling a page that is definitely having a valid certificate including a valid chain. It is not self signed. It is signed by COMODO

Re: Curl ES 60: Invalid certificate chain on MacOS 10.10.3 (Yosemite)

Hello, not sure if this answer is correctly assigned. Sorry. Hi, This snippet from CURLOPT_CAPATH doc might be relevant: If libcurl is built against OpenSSL, the certificate directory must be prepared using the openssl c_rehash utility. HTH, -Vadim I don't think that curl on MacOS

Problem with NTLM proxy auth

Hello all, the following log shows my problem with libcurl 2.27.0.0 (Windows) and NTLM proxy: 2013-08-06 10:09:31 : CURL: About to connect() to proxy 10.50.200.13 port 3128 (#0) 2013-08-06 10:09:31 : CURL: Trying 10.50.200.13... 2013-08-06 10:09:31 : CURL: connected 2013-08-06 10:09:31 :

Re: 15 years

Hello Daniel, At this day, 15 years ago, I uploaded the first release of curl to the world. Thank you for that wonderful library! Would be great if it still exists in another 15 years supporting the WARP protocol, too :-) Best, Volker

Problem with SMTP using libcurl

Hello, we are sending SMTP mails using libcurl. On many systems this works fine but on sone systems it does not. This is the wireshark protocol. It shows that libcurl sends some RSET command after successfully setting some RCPT. Sadly, as soon as we activate logging it seems to behave

Re: Problem with SMTP using libcurl

Hello, Whilst I have thought about extending the supported commands to include RSET, NOOP and VRFY I have not made a business case for it at the moment. As such you have me totally stumped as to what could be sending that RSET :( Maybe a transparent SMTP proxy or virus scanner in the

Curl using STARTTLS even if mailserver does not support it?

Hello, I'm using CURL to send SMTP mails. I initiate it using curl_easy_setopt with CURLOPT_USE_SSL = CURLUSESSL_TRY. I assume that it should use STARTTLS only if the mailserver replies to support it. But this happens at some customer: 2013-02-20 14:36:13 : CURL: About to connect() to

Re: Curl using STARTTLS even if mailserver does not support it?

Hi Steve, Curl currently sends the STARTTLS command regardless of whether the server supports it or not. Ok, that explains one part of the problem. From the log you supplied it looks like the username and password wasn't supplied, so curl treated the connection as anonymous, continued with

SMTP messages are destroyed by Exchange 2003 only

Hello, I might be in the wrong discussion group but I'm using cURL to send SMTP messages. The point is, that the messages seem to work fine in general. But if a Exchange 2003 server is somewhere in the loop, the attached file is destroyed after about 3000 bytes (depends on message size). I

Re: SMTP messages are destroyed by Exchange 2003 only

| L-5244 Sandweiler / Luxembourg phone: +352-268-932-1 | internet: www.regify.com executive board: Kurt Kammerer, Volker Schmid supervisory board chairman: Dr. Hans-Peter Kohlhammer commercial register: Registre de Commerce et des Sociétés B 156705 regify GmbH | Römerstrasse 39 | D-78183

Re: SMTP messages are destroyed by Exchange 2003 only

I got it! My base64 encoded lines had the length of 74 characters per line. I changed this to use 72 characters (I have seen this while examining other Outlook files) and now it works. Unbelievable. I thought that 76 was the maximum: http://en.wikipedia.org/wiki/Base64#MIME So the problem

Find wrong certificate domain

Hello, I'm using libcurl to send SMTP emails. I also set CURLOPT_SSL_VERIFYPEER and CURLOPT_SSL_VERIFYHOST to check the certificate. Some customers are getting an error because the SSL certificate does not match the domain name of the smtp server. I now like to show them the domain name of

Re: Problems with SMTP connection re-using (SSL read: error:00000000:lib(0):func(0):reason(0))

Hello Dan, Any idea why it complains with SSL read: error::lib(0):func(0):reason(0), errno 54? You'd have to look up the OpenSSL documentation to see what errno 54 means, but if the next line can be believed and errno=32 is actually a syscall error, then it's EPIPE - Broken pipe. It

Problems with SMTP connection re-using (SSL read: error:00000000:lib(0):func(0):reason(0))

25 (#0) 2012-12-06 15:40:47 : CURL: MAIL FROM:q...@xxx.com 2012-12-06 15:40:47 : CURL: 250 OK ... Viele Grüße, Volker Schmid CTO regify® your mail matters regify S.A. | 2b, Ennert dem Bierg | L-5244 Sandweiler / Luxembourg phone: +352-268932-1 | internet: www.regify.com executive

SMTP connection re-use possible?

Hello, I'm trying to reuse STARTTLS SMTP connections or simple SMTP connections for sending emails. Sadly, I do not get it to work. Here is how it looks for GMX: CURL: About to connect() to mail.gmx.net port 25 (#0) CURL: Trying 213.165.64.20... CURL: connected CURL: Connected to

Re: SMTP connection re-use possible?

Hello, CURL: Re-using existing connection! (#0) with host mail.gmx.net CURL: Connected to mail.gmx.net (213.165.64.20) port 25 (#0) CURL: MAIL FROM:alice.mas...@.de CURL: 502 5.5.2 Unimplemented {mp028} I find this very strange. Why does it say 502 on this command here? Shouldn't

Re: SMTP connection re-use possible?

Hello, I'm trying to reuse STARTTLS SMTP connections or simple SMTP connections for sending emails. Sadly, I do not get it to work. I never made it ro reuse some SMTP connection. Is this not possible at all? Yes it should be possible... First of all what version of libcurl are you