From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/28284] support description functionality through HEAD
Date: Wed, 07 Sep 2022 23:16:24 +0000 [thread overview]
Message-ID: <bug-28284-10460-3aaymKEA71@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28284-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28284
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Frank Ch. Eigler <fche at redhat dot com> ---
commit 8760e931abf33ed2b215809d5ebf653ced934152
Author: Frank Ch. Eigler <fche@redhat.com>
Date: Fri Sep 2 12:41:38 2022 -0400
PR28284: add tweaks on previous debuginfod x-debuginfod* header forwarding
work
Embrace case-independent headers, more fully document, handle HTTP \r.
In addition to test case, hand-tested against fedora debuginfod
instances, running federated servers under valgrind.
Signed-off-by: Frank Ch. Eigler <fche@redhat.com>
commit bbc2ca6d553f0ce3e670303ac9a3c764cf10d779
Author: Noah Sanci <nsanci@redhat.com>
Date: Wed Jun 15 10:07:29 2022 -0400
PR28284 - Debuginfod header functionality implemented
Debuginfod and debuginfod clients are now equipped to send
and receive http headers prefixed with X-DEBUGINFOD and
print them in verbose mode for more context
Signed-off-by: Noah Sanci <nsanci@redhat.com>
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2022-09-07 23:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 19:02 [Bug debuginfod/28284] New: " nsanci at redhat dot com
2021-08-27 19:02 ` [Bug debuginfod/28284] " nsanci at redhat dot com
2021-08-27 19:05 ` fche at redhat dot com
2021-11-10 14:17 ` mark at klomp dot org
2022-01-20 0:17 ` fche at redhat dot com
2022-05-16 18:55 ` nsanci at redhat dot com
2022-08-11 12:50 ` fche at redhat dot com
2022-08-12 9:05 ` mliska at suse dot cz
2022-09-07 23:16 ` fche at redhat dot com [this message]
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=bug-28284-10460-3aaymKEA71@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.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).