From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 988DEC433EF for ; Sat, 11 Dec 2021 21:28:58 +0000 (UTC) Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4JBLVw6CTyz3cP5 for ; Sun, 12 Dec 2021 08:28:56 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=tanous-net.20210112.gappssmtp.com header.i=@tanous-net.20210112.gappssmtp.com header.a=rsa-sha256 header.s=20210112 header.b=Mjj4BSUV; dkim-atps=neutral Authentication-Results: lists.ozlabs.org; spf=none (no SPF record) smtp.mailfrom=tanous.net (client-ip=2a00:1450:4864:20::130; helo=mail-lf1-x130.google.com; envelope-from=ed@tanous.net; receiver=) Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=tanous-net.20210112.gappssmtp.com header.i=@tanous-net.20210112.gappssmtp.com header.a=rsa-sha256 header.s=20210112 header.b=Mjj4BSUV; dkim-atps=neutral Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4JBLVC4kvDz2yxW for ; Sun, 12 Dec 2021 08:28:17 +1100 (AEDT) Received: by mail-lf1-x130.google.com with SMTP id u3so24213757lfl.2 for ; Sat, 11 Dec 2021 13:28:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tanous-net.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=PJFplU6fFc+s7cudNsjrhd+SZK2MYlpQ5bBN8riWD0A=; b=Mjj4BSUVXG8+njTqFPatYDk1N5VYsYaJJ+ack0S0IABNzgp+cneYaiGd/lVF50Q/av UX49+FbbOLP81IRKo4qsV8Ow1pNauMXozXEBVTfkAIxIb0+7WDYGs5M9hZxnI54movBl F0J7CPlycxvJutb/HlJnxjwJWw9UV1uI0dynILgqua2zpnxJl5RjTVcJUWGeDVlOXcf2 wdv2rDqm/V83BNCduMIRCzJNU4+chysdJlGxLqilRN+w4/2HQ0UHKgUxjvfzkoXtyJop o/pY/hyUw2l7eGJSmTBezOlAf5MzVlj6WQQCAfFYpSSWMjP1hpPmrPrQr4QJI2bSyERE 3o3g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=PJFplU6fFc+s7cudNsjrhd+SZK2MYlpQ5bBN8riWD0A=; b=syIcRnI5D1dNdAOaN1/S5pp1GF10ttYl4dwNKnqS9oVGWp/+6+Ye9Q8nNKq6N+Vzp9 GF5Qji9KnXWydDcMYnpbBtz9UyhB/9o6ndlXtW0DFM390WYIH3JrEa6d2S6Ua4VQqbjf DJ8y2D8wViXCbO/kMGfG3dANx5U4DS++Ei5zdoPINkR2WKPgNNvDIPeTq40xGi3Kmqng aQ9gh3hb40FbWRKv7Rpo1yJscXLsBjvTqt0eETsRLc+cLwdFlcEwzhzd8Pz15FZclNZR 3Rlhq+YuaDUpoMKmnm1KSKP699HZEsYUC9LA+aDOvtJ86jR0m4rXKQeP6IHwBChvYkaH Zkkw== X-Gm-Message-State: AOAM532/iuD9ripO3CJPDt24n1gnpVvhfhRgJUXYG08eSgMY42VNjMBY 5TSD7o/m9NeYzC8InTSiTiux8A68cP909TBTwnhFNWQ1xSM= X-Google-Smtp-Source: ABdhPJw88RQnkrF1sql/a62fJqUe044xjVPGtZmQbkmcDxnA+0XfASd9vSCfzg85uVAfomq9QtAMnRmOcHHQV8EYXZ4= X-Received: by 2002:a05:6512:368c:: with SMTP id d12mr19457158lfs.538.1639258093192; Sat, 11 Dec 2021 13:28:13 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Ed Tanous Date: Sat, 11 Dec 2021 13:28:02 -0800 Message-ID: Subject: Re: Etag support in openbmc To: "Mohammed.Habeeb ISV" Content-Type: text/plain; charset="UTF-8" X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: "openbmc@lists.ozlabs.org" Errors-To: openbmc-bounces+openbmc=archiver.kernel.org@lists.ozlabs.org Sender: "openbmc" 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 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