Subject: Re: [Webpush] Versioning aes128gcm-encoded messages

From: Kit Cambridge <[email-masked]>
Date: Mon, 17 Apr 2017 09:28:24 -0700

On Sun, Mar 19, 2017 at 8:52 PM, Martin Thomson
<[email-masked]> wrote:
> The problem with versioning inline is that it is invisible to HTTP
> content negotiation.  Granted, that doesn't really make any difference
> to the push usage, but a label is visible.  If you accept the need to
> have more labels, then the inline check is redundant.

This sounds good to me. No need to add a version to the payload if we
can use the header.