All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Broadbent <jebr@google.com>
To: "Mohammed.Habeeb ISV" <mohammed.habeeb@inventec.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: Etag support in openbmc
Date: Mon, 11 Oct 2021 20:46:31 -0700	[thread overview]
Message-ID: <CAPw1Ef8fKL_cE=absnX-QwMBVckKy5vkffC08ox5ogPt46aUSw@mail.gmail.com> (raw)
In-Reply-To: <CAPw1Ef-s-eXPs-8KmHLUyRav0JTWLHRDdLKsGFaKTWmkoeiQzg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 854 bytes --]

ShuoX Zhang from Intel might be working on adding support, but I don't see
anything in gerrit.

https://lists.ozlabs.org/pipermail/openbmc/2021-August/027405.html

On Mon, Oct 11, 2021 at 8:37 PM John Broadbent <jebr@google.com> wrote:

> I don't think bmcweb support etags. I have never seen logic from them and
> Ed made a comment about how bmcweb will have to support them in the future
> here https://github.com/openbmc/webui-vue/issues/43#issue-728321615
>
> But I defer to Ed, and Gunner.
>
> Thank you
> John Broadbent
>
> On Mon, Oct 11, 2021 at 8:03 PM Mohammed.Habeeb ISV <
> mohammed.habeeb@inventec.com> wrote:
>
>> Hi
>>
>> Do we have the Etag support in OpenBMC? I see there is a mention of ETag
>> in
>> bmcweb file redfish-core/src / error_messages.cpp, however not sure if
>> Etag is supported.
>> Please let me know.
>>
>> Regards
>>
>

[-- Attachment #2: Type: text/html, Size: 1693 bytes --]

  reply	other threads:[~2021-10-12  3:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-12  3:02 Etag support in openbmc Mohammed.Habeeb ISV
2021-10-12  3:37 ` John Broadbent
2021-10-12  3:46   ` John Broadbent [this message]
2021-10-12  4:03     ` Zhang, ShuoX
2021-10-12 17:30       ` Gunnar Mills
2021-10-12 19:38         ` Ed Tanous
2021-12-11 21:28 ` Ed Tanous

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='CAPw1Ef8fKL_cE=absnX-QwMBVckKy5vkffC08ox5ogPt46aUSw@mail.gmail.com' \
    --to=jebr@google.com \
    --cc=mohammed.habeeb@inventec.com \
    --cc=openbmc@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.