On Fri, Mar 29, 2024 at 4:33 AM Noam Rosenthal
wrote:
>
>
> On Fri, Mar 29, 2024 at 6:33 AM Yoav Weiss (@Shopify) <
> yoavwe...@chromium.org> wrote:
>
>> On top of Domenic's questions, have we tried to estimate the risk here?
>> Even if it's Chromium-only, there could be Enterprise or embedded sc
The automatically generated subject wasn't appropriate for this intent, so
I edited it by hand. I think Jason is aware of it as I was conversing with
him on a GitHub issue about it.
On Wed, Mar 27, 2024 at 8:28 AM Yoav Weiss (@Shopify) <
yoavwe...@chromium.org> wrote:
> As a heads up, this wasn'
On Fri, Mar 29, 2024 at 1:23 PM Mike Taylor wrote:
> On 3/28/24 5:19 PM, Noam Rosenthal wrote:
>
>
> On Thu, Mar 28, 2024 at 9:07 PM Mike Taylor
> wrote:
>
>> On 3/28/24 5:04 PM, Noam Rosenthal wrote:
>>
>> On Thu, Mar 28, 2024 at 9:02 PM Mike Taylor
>> wrote:
>>
>>> Hey Vlad - thanks for the u
Mike, the second version of the Key-Value server API uses encryption on the
inner request payload which means the HTTP cache won't find exact matches
for requests (as encryption results in non-determinism) independent of HTTP
method. I will look at whether PUT or POST makes more sense.
On Wed, Ma
Daniel, I hear your concerns, but I should clarify that this splitting up
of large requests does not do any reassembly or combining of responses, so
sequencing or ordering between responses is not a concern. The Key-Value
servers answering the queries are stateless and should have no ability to
as
On 3/28/24 5:19 PM, Noam Rosenthal wrote:
On Thu, Mar 28, 2024 at 9:07 PM Mike Taylor
wrote:
On 3/28/24 5:04 PM, Noam Rosenthal wrote:
On Thu, Mar 28, 2024 at 9:02 PM Mike Taylor
wrote:
Hey Vlad - thanks for the update.
Do we know if Mozilla is similarly pos
On Fri, Mar 29, 2024 at 6:33 AM Yoav Weiss (@Shopify) <
yoavwe...@chromium.org> wrote:
> On top of Domenic's questions, have we tried to estimate the risk here?
> Even if it's Chromium-only, there could be Enterprise or embedded scenarios
> that somehow rely on it.
>
Yes, and we're willing to keep
