From owner-freebsd-questions@FreeBSD.ORG Fri Apr 3 23:41:55 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 688EF282 for ; Fri, 3 Apr 2015 23:41:55 +0000 (UTC) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.229]) by mx1.freebsd.org (Postfix) with ESMTP id 293FD266 for ; Fri, 3 Apr 2015 23:41:54 +0000 (UTC) Received: from [75.187.32.8] ([75.187.32.8:40812] helo=raspberrypi.bildanet.com) by cdptpa-oedge01 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 53/98-31229-FF42F155; Fri, 03 Apr 2015 23:40:47 +0000 Received: from [192.168.1.53] (helo=baho-utot.bildanet.com) by raspberrypi.bildanet.com with esmtp (Exim 4.84) (envelope-from ) id 1YeBCh-0000wc-7e for freebsd-questions@freebsd.org; Fri, 03 Apr 2015 19:40:47 -0400 Message-ID: <551F24FF.9020101@columbus.rr.com> Date: Fri, 03 Apr 2015 19:40:47 -0400 From: scrat User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: Why does FreeBSD insist on https? References: <20150403183957.GA1379@WorkBox.Home> In-Reply-To: <20150403183957.GA1379@WorkBox.Home> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-RR-Connecting-IP: 107.14.168.118:25 X-Cloudmark-Score: 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 23:41:55 -0000 On 04/03/15 14:39, Bigby James wrote: > On 04/03, Dieter BSD wrote: >>> Any browser which does not support HTTPS is either obsolete or simply >>> missing critical functionality. >> Ya, ya, kids today consider anything more than 5ns old obsolete. >> Doesn't make it so. >> >> I have tried a LOT of browsers and they ALL lack important functionality. >> Most were so broken they were completely unusable. I've fixed bug >> in browsers and made enhancements to them. Had to fix well over >> 1000 bugs in one browser before I managed to get it to compile. > I noticed you've (perhaps mistakenly) omitted mention of what browser you happen > to be using and what pages you're trying to access, while simultaneously > pointing the finger at other browsers for lacking "important" functionality. > What "other browsers" lack doesn't really matter, nor does the work you've done on > other browsers in the past, nor for that matter does what you personally > consider "important functionality." What matters is what browser you're using, > and why it (for whatever reason) can't access these FreeBSD-related pages. > > 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). Without stating what browser > you're using, what version it's at, and what pages you're trying to acces one is > left to wonder why the FreeBSD site maintainers should be expected to change > their site structure simply to accomodate what could very well be user error or > oversight, or a single piece of poorly functioning software. Proper resolution > of the issue (whatever it may actually be) counts on cooperation, not > beligerence. > NCSA Mosaic?