W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2019

Re: Making sure the RFC is good for Qwilt [WAS Re: Call for Adoption: Cache HTTP Response Header]

From: Shmulik Bibi Biran <shmulikb@qwilt.com>
Date: Tue, 12 Feb 2019 10:33:39 +0000
Cc: ietf-http-wg@w3.org, httpbis-chairs@ietf.org
Message-Id: <CAOwYN6wwp7MbfbqYVfiFZ5LYb64FazzX0CAvQnZtRG9die88jQ@mail.gmail.com>
To: tpauly@apple.com, hidinginthebbc@gmail.com
Hi,
Apologies for the last response.
I think this document does a good job covering the interesting information a cache can add, and is very clear and well defined.
My only suggestion is to add another optional parameter for debug capabilities:
I was thinking of a parameter named "id" of type string, that will hold an internal transaction id that can be used by the cache admin to debug problematic transactions.
Though perhaps "id" is too specific and can be replaced with a more generalized version like "dbg". Each implementation can decide what information will be helpful to put there.

The use case I have in mind, is to have some reference to internal logs that hold more information about the HTTP transaction / content, and will help in debug sessions when this token is provided by the end user (or any other entity along the transaction flow).

Thanks,
Shmulik

 

---------- Forwarded message ---------
From: Thomas Peterson <hidinginthebbc@gmail.com <mailto:hidinginthebbc@gmail.com>>
Date: Mon, Jan 14, 2019 at 11:51 AM
Subject: Re: Call for Adoption: Cache HTTP Response Header
To: Tommy Pauly <tpauly@apple.com <mailto:tpauly@apple.com>>, HTTP Working Group <ietf-http-wg@w3.org <mailto:ietf-http-wg@w3.org>>
Cc: <httpbis-chairs@ietf.org <mailto:httpbis-chairs@ietf.org>>


I too am also in favour of adopting, and despite my initial concerns not being completely addressed with any update to the document (see https://lists.w3.org/Archives/Public/ietf-http-wg/2018JulSep/0314.html <https://lists.w3.org/Archives/Public/ietf-http-wg/2018JulSep/0314.html>), I don't believe these should block it moving forward.



Regards


On 13/01/2019 20:19, Tommy Pauly wrote:
> Hello HTTPBis,
> 
> In Bangkok, we had a presentation from Mark on a draft to define a standard Cache HTTP Response Header, that can be used to replace non-standard uses of the "X-Cache" header. The document can be found here: https://tools.ietf.org/html/draft-nottingham-cache-header-00 <https://tools.ietf.org/html/draft-nottingham-cache-header-00>.
> 
> The response in the room was favorable to having the group work on this header, but we didn't have time (and hadn't had sufficient discussion) to do a formal call for adoption.
> 
> This email starts a request for feedback, and a call for adoption. Please reply to this email with your thoughts, and state whether or not you believe the group should adopt this document. Feedback is requested by Friday, January 25th.
> 
> Best,
> Tommy


-- 
Shmulik Bibi Biran
Qwilt | Work: +972-72-2221704 <>| Mobile: +972-58-5439876 <> | shmulikb@qwilt.com <mailto:shmulikb@qwilt.com>
Received on Monday, 25 February 2019 06:19:26 UTC

This archive was generated by hypermail 2.3.1 : Monday, 25 February 2019 06:19:28 UTC