From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/27277] support HEAD query for debuginfod content probe requests
Date: Tue, 30 Mar 2021 20:16:28 +0000 [thread overview]
Message-ID: <bug-27277-10460-nfbMplkP6b@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27277-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27277
--- Comment #2 from Frank Ch. Eigler <fche at redhat dot com> ---
A related idea:
extend the webapi so that returned content includes response headers that
identify the archive & file name where the content was extracted from.
For server privacy, maybe pass back just the basename. The client API
would need to be extended to store those headers as extra strings a client
could query.
All this can be used by smarter clients to identify in user-friendly ways the
origin of the buildid. For example:
% debuginfod-find describe BUILDID
[runs HEAD query, listens to extra Headers]
length: 2879342938423
server: https://foo/bar
x-archive: foo-bar-2.3.rpm
x-file: bin/sudifusdf
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-30 20:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 16:31 [Bug debuginfod/27277] New: " fche at redhat dot com
2021-02-01 8:47 ` [Bug debuginfod/27277] " mliska at suse dot cz
2021-03-30 20:16 ` fche at redhat dot com [this message]
2021-07-27 13:09 ` nsanci at redhat dot com
2021-07-27 14:41 ` fche at redhat dot com
2021-09-15 17:37 ` [Bug debuginfod/27277] Print http response headers when in verbose mode nsanci at redhat dot com
2021-09-27 18:52 ` nsanci at redhat dot com
2021-11-10 14:12 ` mark at klomp dot org
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-27277-10460-nfbMplkP6b@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).