From owner-freebsd-questions@FreeBSD.ORG  Sat Apr  4 00:20:09 2015
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
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 B5C40A7F
 for <freebsd-questions@freebsd.org>; Sat,  4 Apr 2015 00:20:09 +0000 (UTC)
Received: from mario.brtsvcs.net (mario.brtsvcs.net [199.48.128.182])
 (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 88E1678F
 for <freebsd-questions@freebsd.org>; Sat,  4 Apr 2015 00:20:09 +0000 (UTC)
Received: from chombo.houseloki.net (unknown
 [IPv6:2601:7:2580:181:21c:c0ff:fe7f:96ee])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mario.brtsvcs.net (Postfix) with ESMTPSA id 4AF262C160E;
 Sat,  4 Apr 2015 00:20:07 +0000 (UTC)
Received: from [IPv6:2601:7:2580:181:baca:3aff:fe83:bd29] (unknown
 [IPv6:2601:7:2580:181:baca:3aff:fe83:bd29])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by chombo.houseloki.net (Postfix) with ESMTPSA id AA3AF5DE;
 Fri,  3 Apr 2015 17:20:05 -0700 (PDT)
Message-ID: <551F2E2D.6090106@bluerosetech.com>
Date: Fri, 03 Apr 2015 17:19:57 -0700
From: Mel Pilgrim <list_freebsd@bluerosetech.com>
Reply-To: freebsd-questions@freebsd.org
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: scrat <baho-utot@columbus.rr.com>, freebsd-questions@freebsd.org
Subject: Re: Why does FreeBSD insist on https?
References: <CAA3ZYrAwXOp_5vfUPsEkF82UPaAqNwnTm7dw1ogf-C-X+j730g@mail.gmail.com>
 <20150403183957.GA1379@WorkBox.Home> <551F24FF.9020101@columbus.rr.com>
In-Reply-To: <551F24FF.9020101@columbus.rr.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Apr 2015 00:20:09 -0000

On 2015-04-03 16:40, scrat wrote:
> On 04/03/15 14:39, Bigby James wrote:
>> On a lark, I went ahead and installed Firefox, Chromium, Dillo, VimB, Luakit,
>> UZBL, surf, SeaMonkey, Conkeror, w3m and lynx. Every one of them is able to
>> access https://www.freebsd.org without any problem, with the exceptions of UZBL
>> and lynx, which each complain about SSL/TLS issues (which can in turn be
>> circumvented in their respective configurations).
>
> NCSA Mosaic?

Considering NCSA Mosaic wouldn't even work on a modern website, I think 
we can safely remove it from the test cases. ;)