On Tue, Apr 14, 2015 at 9:51 AM, <lorenzo.kel...@gmail.com> wrote: > 1) Caching proxies: resources obtained over HTTPS cannot be cached by a proxy > that doesn't use MITM certificates. If all users must move to HTTPS there > will be no way to re-use content downloaded for one user to accelerate > another user. This is an important issue for locations with many users and > poor internet connectivity.
Where is the evidence that this is a problem in practice? What do these environments do for YouTube? > 2) Self signed certificates: in many situations it is hard/impossible to get > certificates signed by a CA (e.g. provisioning embedded devices). The current > approach in many of these situations is not to use HTTPS. If the plan goes > into effect what other solution could be used? Either something like https://bugzilla.mozilla.org/show_bug.cgi?id=1012879 as you mentioned or overrides for local devices. This definitely needs more research but shouldn't preclude rolling out HTTPS on public resources. -- https://annevankesteren.nl/ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
