Re: Intent to deprecate: Insecure HTTP

2015-04-17 Thread Henri Sivonen
On Wed, Apr 15, 2015 at 3:33 AM, Karl Dubost kdub...@mozilla.com wrote: Le 14 avr. 2015 à 19:29, Henri Sivonen hsivo...@hsivonen.fi a écrit : Currently, the UI designation for http is neutral while the UI designation for mixed content is undesirable. I think we should make the UI designation

Re: Intent to deprecate: Insecure HTTP

2015-04-17 Thread Bob Clary
On 04/17/2015 09:46 AM, Mike Hoye wrote: On 2015-04-17 12:20 PM, Anne van Kesteren wrote: On Fri, Apr 17, 2015 at 6:13 PM, andrewneme...@gmail.com wrote: As a non-tech person, the only thing I know is https means my browser runs even slower on DSL. This has already been addressed earlier in

Re: Intent to deprecate: Insecure HTTP

2015-04-17 Thread Anne van Kesteren
On Fri, Apr 17, 2015 at 6:46 PM, Mike Hoye mh...@mozilla.com wrote: I don't see where that document speaks to the impact of TLS on caching proxies, which I'm guessing is the source of the performance hit Andrew mentions. It's been a while since I've looked, but in Canada (and probably other

Re: Intent to deprecate: Insecure HTTP

2015-04-17 Thread andrewnemethy
As a non-tech person, the only thing I know is https means my browser runs even slower on DSL, which is all that is available in many rural areas. Would this not mean that I'd be back to dial-up times to load a story or post, all of which are larded up with ads and videos these days? At 7 mbps

Re: Intent to deprecate: Insecure HTTP

2015-04-17 Thread Mike Hoye
On 2015-04-17 12:20 PM, Anne van Kesteren wrote: On Fri, Apr 17, 2015 at 6:13 PM, andrewneme...@gmail.com wrote: As a non-tech person, the only thing I know is https means my browser runs even slower on DSL. This has already been addressed earlier in the thread. HTTPS has negligible

Re: Intent to deprecate: Insecure HTTP

2015-04-17 Thread Martin Thomson
On Fri, Apr 17, 2015 at 11:22 AM, Anne van Kesteren ann...@annevk.nl wrote: As I said early on in this thread, this claim often comes up, but is never backed up. Where is the research that shows we need public caching proxies? This is early days, but I'm working with a partner on two things:

How does stl_wrappers works in mozilla building system?

2015-04-17 Thread Yonggang Luo
I can not found the cause that how mozilla building with stl_wrappers. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

How does stl_wrappers works in mozilla building system?

2015-04-17 Thread Yonggang Luo
I can not found the cause that how mozilla building with stl_wrappers. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

Re: Intent to deprecate: Insecure HTTP

2015-04-17 Thread Robert Kaiser
Karl Dubost schrieb: Henri, great points, about… Le 14 avr. 2015 à 19:29, Henri Sivonen hsivo...@hsivonen.fi a écrit : Currently, the UI designation for http is neutral while the UI designation for mixed content is undesirable. I think we should make the UI designation of plain http

Re: Intent to deprecate: Insecure HTTP

2015-04-17 Thread Anne van Kesteren
On Fri, Apr 17, 2015 at 6:13 PM, andrewneme...@gmail.com wrote: As a non-tech person, the only thing I know is https means my browser runs even slower on DSL. This has already been addressed earlier in the thread. HTTPS has negligible performance impact. See e.g.: https://istlsfastyet.com/

Re: How does stl_wrappers works in mozilla building system?

2015-04-17 Thread Nicholas Alexander
On Fri, Apr 17, 2015 at 2:58 PM, Yonggang Luo luoyongg...@gmail.com wrote: I can not found the cause that how mozilla building with stl_wrappers. What do you want to know? https://dxr.mozilla.org/mozilla-central/search?tree=mozilla-centralq=stl_wrapperredirect=true clearly shows a Python