> Increased request latencies, increased heap footprint and increased CPU
> usage. I suspect it will probably be a bigger problem for people who use
> mobile.

> Ideally, converting from http vs https should be transparent. There isn't
> any reason that I can think of to hard code a scheme in the urls on any
> site, except for explicitly switching between http and https for cases such
> as authentication.

> Any other time, you can just use a relative url and the browser will pick
> up and use the preexisting scheme regardless of whether it is http or
> https. A single link which says "encrypt all traffic in https" and then
> redirects to https://mises.org or https://whateverpageiamon should make
> this possible.

> So as long as you don't enforce either in any of your urls, you should be
> fine. Just put an encrypt all traffic button or something similar that
> redirects to the current page using https instead of http. Of course, if
> you have existing urls that specify specifically http, those will have to
> be removed to only specify a host and a document and not a scheme, but they
> shouldn't have been there in the first place. There's no point in writing
> http://mises.org/daily when /daily works better.

>  -------- Original Message --------
> Subject: Re: [Mises.org Dev] Re: HTTPS Everywhere - let's "ban" HTTP
> From: David Veksler <her...@gmail.com>
> Date: Thu, March 22, 2012 1:11 pm
> To: "misesdev@googlegroups.com" <misesdev@googlegroups.com>
> Cc: "misesdev@googlegroups.com" <misesdev@googlegroups.com>

> What are those exactly?

> Sent from my iPad

> On Mar 23, 2012, at 1:09 AM, <jcfol...@pureperfect.com> wrote:

> Are you not concerned with the performance implications of doing this?

>  -------- Original Message --------
> Subject: [Mises.org Dev] Re: HTTPS Everywhere - let's "ban" HTTP
> From: David Veksler <da...@mises.org>
> Date: Thu, March 22, 2012 12:25 am
> To: "Mises.org Development" <misesdev@googlegroups.com>

> As promised:

> http://code.mises.com/svn/comp.php?repname=MisesWeb&compare[]=/@2082&compare[]=/@2083

> Things that don't work with SSL:

>    - Google Books preview
>    - Reddit +1 button

> ---
> Regards,
> David Veksler
> http://about.me/davidveksler

> On Thu, Mar 22, 2012 at 11:55 AM, David Veksler <da...@mises.org> wrote:

>> https://www.eff.org/https-everywhere/

>> This is really cool (and important).  Let's "ban" the http:// scheme
>> from Mises.org.  Instead I will use either Request.Url.Scheme
>> or href="// URLs.

>> Who wants to help?

>> ---
>> Regards,
>> David Veksler
>> http://about.me/davidveksler