From owner-freebsd-questions@FreeBSD.ORG Thu Apr 2 21:07:00 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 03827375 for ; Thu, 2 Apr 2015 21:07:00 +0000 (UTC) Received: from mail-in6.apple.com (mail-out6.apple.com [17.151.62.28]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CBC69611 for ; Thu, 2 Apr 2015 21:06:59 +0000 (UTC) Received: from relay3.apple.com (relay3.apple.com [17.128.113.83]) by mail-in6.apple.com (Apple Secure Mail Relay) with SMTP id 40.3E.09025.27FAD155; Thu, 2 Apr 2015 14:06:58 -0700 (PDT) X-AuditID: 11973e15-f79fd6d000002341-2a-551daf72a767 Received: from [17.149.224.197] (Unknown_Domain [17.149.224.197]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by relay3.apple.com (Apple SCV relay) with SMTP id FB.09.19589.A7FAD155; Thu, 2 Apr 2015 14:07:06 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Subject: Re: Why does FreeBSD insist on https? From: Charles Swiger In-Reply-To: Date: Thu, 2 Apr 2015 14:06:58 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Dieter BSD X-Mailer: Apple Mail (2.2070.6) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrLLMWRmVeSWpSXmKPExsUi2FAYrFu0XjbUYOstRYv2hbvZLF5+3cTi wOQx49N8Fo+ds+6yBzBFcdmkpOZklqUW6dslcGV8PnuZveAuV8XVc1eYGxiPcHQxcnJICJhI zDnxig3CFpO4cG89kM3FISSwl1Fi5fS/bDBFW969ZoRITGeS2H/9JjtIgllAS+LGv5dMIDav gIHE3FNfwGxhAT2JO2/7gJo5ONgE1CQmTOQBCXMKBEq0/T7KDGKzCKhIbJnQDzVGV6LpxltG CFtbYtnC18wQI60kFqzewwwyRkggQGJRL9gYEaDW7o43YNMlBOQlejalg1wmIfCRVWLSrxfs ExiFZiE5bhaS42Yh2bCAkXkVo1BuYmaObmaemV5iQUFOql5yfu4mRlD4TrcT3cF4ZpXVIUYB DkYlHt6MPTKhQqyJZcWVuYcYpTlYlMR5q+fIhgoJpCeWpGanphakFsUXleakFh9iZOLglGpg VNY8IOl04VP+SgUZt/MaZUoaOb7WfUmZKoX1EWzxqqd+/XTYJPZ3VVGgs6r5DOeHLXwpH9ct cnyxNbI7pL7m7D3Ld5O9ZT5ULzaYXdH1ybpO1NPy0WK5Bz8dV+nl2y15kaNqGXDtaafRli88 TysZPnTbv5147oWR0z+2L3MEvK++/K++bGe5EktxRqKhFnNRcSIAviWTLkACAAA= X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrALMWRmVeSWpSXmKPExsUiOPXBUd2q9bKhBqdWMVm0L9zNZvHy6yYW ByaPGZ/ms3jsnHWXPYApissmJTUnsyy1SN8ugSvj89nL7AV3uSqunrvC3MB4hKOLkZNDQsBE Ysu714wQtpjEhXvr2boYuTiEBKYzSey/fpMdJMEsoCVx499LJhCbV8BAYu6pL2C2sICexJ23 fUANHBxsAmoSEybygIQ5BQIl2n4fZQaxWQRUJLZM6IcaoyvRdOMtI4StLbFs4WtmiJFWEgtW 72EGGSMkECCxqBdsjAhQa3fHG7DpEgLyEj2b0icw8s9Ccs8sJPfMQjJ0ASPzKkaBotScxEpj vcSCgpxUveT83E2MoHBrKAzewfhnmdUhRgEORiUe3ow9MqFCrIllxZW5hxglOJiVRHir5suG CvGmJFZWpRblxxeV5qQWH2KU5mBREudVbgdKCaQnlqRmp6YWpBbBZJk4OKUaGNn0y97OPrPj 5KOAuo6rs16/55FKuDA38f5NZWmdrjk1OlJvv5YUWMqkFH0+VTH396WfirvU4phfblE5bm9a qeN8rZ4nXE/7/v/T3nb8mv+P7j60m8vmxgzuJ0EfuZ685FE73vM3c6Pg5p9d3dsWSuqvDjwp l3LiREnTeaO8vh88RmURu3726CixFGckGmoxFxUnAgBPrjJuMwIAAA== Cc: FreeBSD - 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: Thu, 02 Apr 2015 21:07:00 -0000 On Apr 2, 2015, at 1:26 PM, Dieter BSD wrote: > Why do so many FreeBSD URLs redirect from http to https? > What is this intended to accomplish? Security? Confidentiality? Strong(er) assurance of content integrity? There are an increasing # of transparent proxies which rewrite content, inject ads, even inject malware for HTTP which are foiled by switching to HTTPS + HSTS (HTTP Strict Transport Security). > This is user-hostile. Some browsers cannot do https, and there are > good reasons (unrelated to http vs https) to use these browsers. Any browser which does not support HTTPS is either obsolete or simply missing critical functionality. Your bank, online stores, utilities, almost any site with a login are all going to require HTTPS. However, if you prefer to interact with the web by having a script which performs wget and emails you back the results, go right ahead. :-) > There are also good reasons to prefer http over https even with a = browser > that can do https. Https is useful when needed, but it isn't needed = here. >=20 > Can someone *please* fix this? You should expect that as time passes, more and more sites will either = switch to HTTPS only and/or will switch to HTTP/2 which encourages browsers to = try and connect via HTTPS even for http URLs. Regards, --=20 -Chuck