Re: [Push API] How to detect acceptable Content-Encoding for each UA

Hi Martin, Thanks so much for your comment. I understand that there will be no problem when any UA will accept "aesgcm". > Firefox will support aesgcm128 for several releases once "aesgcm" is > done (something I expect to happen in 48). Good. I'm looking forward to seeing it will happen. On

Re: [Push API] How to detect acceptable Content-Encoding for each UA

On 4 March 2016 at 18:07, Tomoyuki SHIMIZU wrote: > On the other hand, it could be renamed according to encryption spec update > (e.g. changing from "aesgcm128" to "aesgcm"[2][3]). It might suggest each UA > might support different types or versions of Content-Encoding in

[Push API] How to detect acceptable Content-Encoding for each UA

Hi, I would like to make a comment on a concern about using Push API with Web Push Encryption. Web Push Encryption spec[1] says an application server must indicate Content-Encoding so that a UA can correctly process received push messages. Currently there are browsers which supports "aesgcm128"