From owner-freebsd-questions@FreeBSD.ORG Thu Apr 2 20:26:37 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 2A676219 for ; Thu, 2 Apr 2015 20:26:37 +0000 (UTC) Received: from mail-ie0-x22a.google.com (mail-ie0-x22a.google.com [IPv6:2607:f8b0:4001:c03::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E60A8EC4 for ; Thu, 2 Apr 2015 20:26:36 +0000 (UTC) Received: by iedm5 with SMTP id m5so78298150ied.3 for ; Thu, 02 Apr 2015 13:26:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=tpvvyrH+6x4faAUYG5FnDJf9hXdLbUNX7DPpATJiKe0=; b=KyEZVjEDIRBxhNj5RtpcF62Wo1oiUfbPqEIzObQ/kfC3qFxH1AeBMz7FmEIDnPgAXh 3xoE3adGTNpfmspDLPKYPHINZBLtkRg1r02TXIxajeI+NOs/xOjO4ngoBx65U8cm9hgn X0T2VDm6/X/huxkptxr8k9WzfIOx4v+ky1w3eWOz+it1kRg1sIVx+BlDZjVMcREU5GYq 2X2gMVwj2EBVncD6UTtydoi7PSw/kMad/oA5sBHhUP7JyoLEx5U72VpXoNhbGh6JLbNg NdnMJyog3eEbu3jLM4QFZOqG1J07BIejA+xTo43TjmUSMezGiuFSQGTqZ/NrpBFLYOGd Zc9Q== MIME-Version: 1.0 X-Received: by 10.107.165.68 with SMTP id o65mr74581200ioe.56.1428006396439; Thu, 02 Apr 2015 13:26:36 -0700 (PDT) Received: by 10.64.223.170 with HTTP; Thu, 2 Apr 2015 13:26:36 -0700 (PDT) Date: Thu, 2 Apr 2015 12:26:36 -0800 Message-ID: Subject: Why does FreeBSD insist on https? From: Dieter BSD To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 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 20:26:37 -0000 Why do so many FreeBSD URLs redirect from http to https? What is this intended to accomplish? This is user-hostile. Some browsers cannot do https, and there are good reasons (unrelated to http vs https) to use these browsers. 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. Can someone *please* fix this?