From owner-freebsd-questions@FreeBSD.ORG Fri Apr 3 03:13:11 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0A73B307 for ; Fri, 3 Apr 2015 03:13:11 +0000 (UTC) Received: from mail.parts-unknown.org (mail.parts-unknown.org [IPv6:2001:470:67:119::4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E117B6E5 for ; Fri, 3 Apr 2015 03:13:10 +0000 (UTC) Received: by mail.parts-unknown.org (Postfix, from userid 80) id 2774F5B3BD22; Thu, 2 Apr 2015 20:13:04 -0700 (PDT) Received: from mail.parts-unknown.org (mail.parts-unknown.org [2001:470:67:119::4]) by mail.parts-unknown.org (Horde Framework) with HTTP; Thu, 02 Apr 2015 20:13:04 -0700 Date: Thu, 02 Apr 2015 20:13:04 -0700 Message-ID: <20150402201304.Horde.ps5NBpg-dY-dU9z9iH1yLQ2@mail.parts-unknown.org> From: David Benfell To: freebsd-questions@freebsd.org Subject: Re: Why does FreeBSD insist on https? References: In-Reply-To: User-Agent: Horde Application Framework 5 Content-Type: multipart/signed; boundary="=_dx4Fr28Bmzui1n8RLL4HuQ1"; protocol="application/pgp-signature"; micalg=pgp-sha1 MIME-Version: 1.0 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Apr 2015 03:13:11 -0000 This message is in MIME format and has been PGP signed. --=_dx4Fr28Bmzui1n8RLL4HuQ1 Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoting Charles Swiger : > > You should expect that as time passes, more and more sites will either sw= itch > to HTTPS only and/or will switch to HTTP/2 which encourages browsers=20= =20 >=20to try and > connect via HTTPS even for http URLs. I haven't looked at the announcement personally, so I might be=20=20 mistaken,=20but my understanding is that Google is tweaking search=20=20 rankings=20in part based on https behavior: Not only do you need to be=20= =20 doing=20it, but you need to be doing it right. And I agree that if the browser won't do https, then it's the browser=20=20 that's=20at fault, certainly not FreeBSD. --=20 David Benfell --=_dx4Fr28Bmzui1n8RLL4HuQ1 Content-Type: application/pgp-signature Content-Description: PGP Digital Signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJVHgU/AAoJEBV64x4SNmArfPwP/jmduuaKbhvZQEaM7GOja4+5 DhPkf8GbO14ijJmX+ovhjWDOaZsObuZJooNUkAFRZBVW6UeDWt6rTE1SGoENIXYc bFHt6ri3KCjG6t9yIEUKlIZm9adgsyaQqybvmoZcERod8LrrpbSehKIhnXDr4GUU p2llDvhLCVCY2HmqYsdmjqGYSzPQyrJV+JPYH2UTOLNIrHgOGpBvrZb/ZVQxJrPL 58nANxBrfjFlkoRdlT7tnK4mmRUqNHNlkFO7x8GypMfHHGt6YgHgypIsXUSoKRu+ qAuEiB6Nttlkqy748Or6UnCwXt2uXfadB847PJopy61wb1LkUW3yQhVH30Y+hNcb hNMrlLDSXpNoDfX01KJgC4+n7RS3qgUPQ1HyhTRnq1ul4cIpUxRMtZ+ryzloX+Wx cfbgEk9vr6iV8VhU1HBln2DOLuNPNyRC9X4hwlVSwHQbTsl5AsdT0sc8EXE4yigB SoHggPTY0D/VuKAXefCGgrFM5Ij0m6DmV2ubm3pJbo+ZGX8Bfp8qXsFpZJyRezro ZqS75MBIQRNasRPanEezBiyzBDtd6V/JdlV1vyiti8o5AZMgu+goby1b/t9Y4ic2 z3RN08RYXRs7w6vZdF1J3Ucjin1QI5vC5ah9oET5LGhFQVT54EWkJVvbRHMf4vD+ MVz9xEpuIeu741Q6Ya0W =FCrO -----END PGP SIGNATURE----- --=_dx4Fr28Bmzui1n8RLL4HuQ1--