From: "Kevin Carhart" <kevin_carhart@fastmail.fm>
To: edbrowse-dev@edbrowse.org
Subject: CURLINFO_DATA_OUT
Date: Wed, 08 Dec 2021 01:06:10 -0800 [thread overview]
Message-ID: <bf581112-25be-4e0a-ac3b-8f3916619b50@www.fastmail.com> (raw)
This would be an addition to the conditional blocks in ebcurl_debug_handler in http.c
But it could be just as good to plunk it in when the need arises and not bother formalizing it.
if (info_desc == CURLINFO_DATA_OUT) {
// could be so much volume that it needs to sit on its own at db23
char* cp = data;
for ( ; *cp != '\0'; ++cp )
{
printf("%02x", (uchar)*cp);
}
}
reply other threads:[~2021-12-08 9:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bf581112-25be-4e0a-ac3b-8f3916619b50@www.fastmail.com \
--to=kevin_carhart@fastmail.fm \
--cc=edbrowse-dev@edbrowse.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).