From: Ed Tanous <ed@tanous.net>
To: "Mohammed.Habeeb ISV" <mohammed.habeeb@inventec.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: Etag support in openbmc
Date: Sat, 11 Dec 2021 13:28:02 -0800 [thread overview]
Message-ID: <CACWQX828Gxj0tnyppiGfMxNktu7iepYgxT=qs0UQjKFMuy6sbg@mail.gmail.com> (raw)
In-Reply-To: <PS2PR02MB35412394ABF3E0441D72627E90B69@PS2PR02MB3541.apcprd02.prod.outlook.com>
We previously supported etag for static resources, hence the
references to them. They were removed when I moved phosphor-webui to
webpack builds, and it was always on my list to add them back, using
webpacks hashing mechanisms, but I never got a chance.
In practice, they didn't provide that much utility because most browsers:
1. only cache if you have a valid SSL certificate.
2. Have a very limited cache size.
3. Don't support cross site etag caches.
So in practice, the cache didn't provide any benefit in a majority of cases.
In terms of supporting etags on non-static resources, that's quite
complex, given that cache invalidation is difficult, and likely
deserves its own design document.
-Ed
On Mon, Oct 11, 2021 at 8:04 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
prev parent reply other threads:[~2021-12-11 21:28 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
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 [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='CACWQX828Gxj0tnyppiGfMxNktu7iepYgxT=qs0UQjKFMuy6sbg@mail.gmail.com' \
--to=ed@tanous.net \
--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.