Download
Browse source Changelog
Documentation
Project   Help us   Known bugs   TODO Protocols   CA bundle   HTTP Cookies   HTTP/2   SSL Certs Releases   Security   Version numbers   Vulnerabilities curl tool   man page   Tutorial   HTTP scripting Who and Why
libcurl
ABI API Competitors Examples Features Mailing list Related libs Using libcurl Tutorial Testimonials
Get Help
curl-library curl-users curl-announce curl-commits Book: Everything curl Report a bug Mail Etiquette
Development
Autobuilds Code Style Contribute Deprecate Internals Release Notes Release Procedure Roadmap Run Tests Security Process Specifications Test curl
News
Changelog Release table
curl / Mailing Lists / curl-library / Single Mail

curl-library

Way too much logging for WebSocket connections? CURLE_AGAIN?

From: Volker Schmid via curl-library <curl-library_at_cool.haxx.se>
Date: Thu, 7 Feb 2019 17:59:41 +0100

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 [5044]:[tWs]: VERB: CURL: schannel: encrypted data buffer: offset 0 length 17408
2019-02-07 15:19:18-0108 [5044]:[tWs]: VERB: CURL: schannel: Curl_read_plain returned CURLE_AGAIN
2019-02-07 15:19:18-0108 [5044]:[tWs]: VERB: CURL: schannel: encrypted data buffer: offset 0 length 17408
2019-02-07 15:19:18-0108 [5044]:[tWs]: VERB: CURL: schannel: encrypted data buffer: offset 0 length 17408
2019-02-07 15:19:18-0108 [5044]:[tWs]: VERB: CURL: schannel: decrypted data buffer: offset 0 length 16384
2019-02-07 15:19:18-0109 [5044]:[tWs]: VERB: CURL: schannel: schannel_recv cleanup
2019-02-07 15:19:18-0120 [5044]:[tWs]: VERB: CURL: schannel: client wants to read 16384 bytes
2019-02-07 15:19:18-0120 [5044]:[tWs]: VERB: CURL: schannel: encrypted data buffer: offset 0 length 17408
2019-02-07 15:19:18-0120 [5044]:[tWs]: VERB: CURL: schannel: Curl_read_plain returned CURLE_AGAIN
2019-02-07 15:19:18-0120 [5044]:[tWs]: VERB: CURL: schannel: encrypted data buffer: offset 0 length 17408
2019-02-07 15:19:18-0121 [5044]:[tWs]: VERB: CURL: schannel: encrypted data buffer: offset 0 length 17408
2019-02-07 15:19:18-0121 [5044]:[tWs]: VERB: CURL: schannel: decrypted data buffer: offset 0 length 16384
2019-02-07 15:19:18-0121 [5044]:[tWs]: VERB: CURL: schannel: schannel_recv cleanup
2019-02-07 15:19:18-0132 [5044]:[tWs]: VERB: CURL: schannel: client wants to read 16384 bytes
2019-02-07 15:19:18-0133 [5044]:[tWs]: VERB: CURL: schannel: encrypted data buffer: offset 0 length 17408
2019-02-07 15:19:18-0133 [5044]:[tWs]: VERB: CURL: schannel: Curl_read_plain returned CURLE_AGAIN
2019-02-07 15:19:18-0133 [5044]:[tWs]: VERB: CURL: schannel: encrypted data buffer: offset 0 length 17408
2019-02-07 15:19:18-0133 [5044]:[tWs]: VERB: CURL: schannel: encrypted data buffer: offset 0 length 17408
2019-02-07 15:19:18-0133 [5044]:[tWs]: VERB: CURL: schannel: decrypted data buffer: offset 0 length 16384
2019-02-07 15:19:18-0133 [5044]:[tWs]: VERB: CURL: schannel: schannel_recv cleanup
... hundreds of thousands will follow ...

Does that simply mean it waits for data on this channel/connection or does it mean there is some activity? Is it normal to have that on WebSocket connections? Or are we doing it wrong somewhere?

On Linux, there are no such messages in the logfiles for WebSocket connections. With the same code basis for our product but, of course, not schannel.

Thanks,

Volker
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2019-02-07