public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/27277] New: support HEAD query for debuginfod content probe requests
Date: Fri, 29 Jan 2021 16:31:27 +0000	[thread overview]
Message-ID: <bug-27277-10460@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=27277

            Bug ID: 27277
           Summary: support HEAD query for debuginfod content probe
                    requests
           Product: elfutils
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: debuginfod
          Assignee: unassigned at sourceware dot org
          Reporter: fche at redhat dot com
                CC: elfutils-devel at sourceware dot org, woodard at redhat dot com
  Target Milestone: ---

There appear to exist use cases that intend to simply check for the existence
of content in a debuginfod server, without actually downloading it.  In HTTP
land, the HEAD operation is the natural expression of this.  We could support
this in the webapi, and give options to debuginfod-find and the client API to
use it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2021-01-29 16:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-29 16:31 fche at redhat dot com [this message]
2021-02-01  8:47 ` [Bug debuginfod/27277] " mliska at suse dot cz
2021-03-30 20:16 ` fche at redhat dot com
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@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).