From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/27982] debuginfod client maximum-transfer-size and -time parameters
Date: Tue, 15 Jun 2021 14:30:22 +0000 [thread overview]
Message-ID: <bug-27982-10460-ngxmXy5SZt@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27982-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27982
--- Comment #1 from Frank Ch. Eigler <fche at redhat dot com> ---
possible representation in the apis:
-> $DEBUGINFOD_MAXSIZE (in bytes)
-> outgoing request header X-DEBUGINFOD-MAXSIZE: (number)
<- http response code 406 (Not Acceptable) if rejected
<- posix API rc EFBIG (File too large) (don't cache as 000 negative-hit)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-06-15 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 21:16 [Bug debuginfod/27982] New: " fche at redhat dot com
2021-06-15 14:30 ` fche at redhat dot com [this message]
2021-07-19 15:29 ` [Bug debuginfod/27982] " nsanci at redhat dot com
2021-09-15 17:34 ` fche at redhat dot com
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-27982-10460-ngxmXy5SZt@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).