[w3c/ServiceWorker] Inconsistent behaviour when client-side certificates are required (#1022)

I've tested ServiceWorkers on a page where the web server requires client-side certificates for authentication. This is inconsistently implemented, as Chrome seems to re-use the chosen certificate that was used for the initial page load (or even ask the user again when it's unsure, when using Chrome on Android). Firefox on the other hand doesn't send the client-side certificate (even if told not to ask about client-side certificates and just choose the first one that fits) and ends up with a 400 response in the install handler (when trying to fill a cache).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1022