From: "Frank Ch. Eigler" <fche@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: elfutils-devel@sourceware.org
Subject: Re: [patch git] PR28284 - debuginfod x-debuginfod* header processing
Date: Tue, 6 Sep 2022 12:05:47 -0400 [thread overview]
Message-ID: <20220906160547.GE13250@redhat.com> (raw)
In-Reply-To: <dfddb2d9d56de2e6abd1cd4f125f1b08b578c32d.camel@klomp.org>
Hi -
Thanks for giving it a look.
> > I had a bit of time to tweak Noah Sanci's PR28284 work, and I believe
> > it addresses Mark's last set of comments (from a while ago). This
> > follow-up patch corrects things like case sensitivity, spacing, \r\n
> > processing, and tweaks documentation.
>
> I hadn't thought about the \r\n at the end of the HTTP headers. Thanks.
> I assume \r\n at the end of HTTP headers required, since you are
> expecting in the code now, or could it also be \n on its own?
At the wire protocol level, yes, required. But this code strips them
from the normal C/userspace processing (and libcurl adds them back as
needed).
> > The gist of it is to add a new client api function
> > debuginfod_get_headers(), documented to return x-debuginfod* headers
> > from current or previous fetch requests.
>
> This looks good, but I think c->winning_headers needs to be
> freed/cleared at the start of debuginfod_query_server. Otherwise if you
> reuse the debuginfod_client and you hit the cache, the user gets the
> headers from the last use of debuginfod_client that did fetch something
> from a server. Which imho is confusing (the headers won't match the
> cached result returned).
Good point, we don't want an aborted new transfer to retain records from
a previous run, will fix that.
> > debuginfod-find prints those
> > in -v verbose mode, and debuginfod relays them in federation.
>
> This is the only thing I am not 100% happy about. It means you can only
> see the headers using debuginfod-find but no longer with any other
> client when DEBUGINFOD_VERBOSE is set. Is this really what we want?
Well, dunno, can't speak for we all. :-) For debugging purposes (which
is what DEBUGINFOD_VERBOSE is), we could print all headers that come
in, from any server we're connecting to. For API / human-friendly
use, limiting to x-debuginfod* ones from the winning server seems more
useful. (I hope we don't have to rethink again once the signature
contents start coming down that pipe too - hope they're not too long.)
Will add a commit to that effect shortly and run it through the
trybots.
- FChE
next prev parent reply other threads:[~2022-09-06 16:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-03 0:13 Frank Ch. Eigler
2022-09-06 15:49 ` Mark Wielaard
2022-09-06 16:05 ` Frank Ch. Eigler [this message]
2022-09-06 16:42 ` Ryan Goldberg
2022-09-08 11:42 ` Mark Wielaard
2022-09-08 13:45 ` Frank Ch. Eigler
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=20220906160547.GE13250@redhat.com \
--to=fche@redhat.com \
--cc=elfutils-devel@sourceware.org \
--cc=mark@klomp.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 read-only IMAP folder(s) and NNTP newsgroup(s).