Re: [Webpush] Vapid public key

[Costin Manolache <[e-mail]>]

One more small suggestion: one of the pain points ( for me ) is the W3C
subscribe taking the
vapid pubkey as bytes instead of a string, and having to include the key in
.js files as a constant.

Would it be possible to define a .well-known/vapid/... file where the
public key can be saved ?
This may simplify tools, testing ( test env may use test sender keys), etc.
One problem is that
.well-known is at root - so either have
/.well-known/vapid/ENCODED_SW_URL.pub or
have a less standard .well-known/ in the same directory with the SW.

This would be optional - if the key is not included in the register call
explicitly.

GCM has a similar mechanism.

Costin



On Thu, Nov 3, 2016 at 8:09 PM Martin Thomson <[e-mail]>
wrote:

> On 3 November 2016 at 11:56, Martin Thomson <[e-mail]>
> wrote:
> > I could live with either.  The second form is recommended by RFC 7235,
> > so we should probably pick that one.  That said, it makes sniffing
> > marginally harder because the double-quotes are optional and '=' is
> > valid in either form.  You have to look for a comma.
>
> Here's the proposed changes:
>
> https://github.com/webpush-wg/webpush-vapid/pull/29
>