From owner-freebsd-questions@FreeBSD.ORG Fri Apr 3 18:40:02 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 C4EE1269 for ; Fri, 3 Apr 2015 18:40:02 +0000 (UTC) Received: from sender1.zohomail.com (sender1.zohomail.com [74.201.84.162]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AF5F2A0 for ; Fri, 3 Apr 2015 18:40:02 +0000 (UTC) Received: from WorkBox.Home (184-100-67-185.mpls.qwest.net [184.100.67.185]) by mx.zohomail.com with SMTPS id 1428086400004319.0455209380541; Fri, 3 Apr 2015 11:40:00 -0700 (PDT) Date: Fri, 3 Apr 2015 13:39:57 -0500 From: Bigby James To: freebsd-questions@freebsd.org Subject: Re: Why does FreeBSD insist on https? Message-ID: <20150403183957.GA1379@WorkBox.Home> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) 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 18:40:02 -0000 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. -- "A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools." - Douglas Adams