From owner-freebsd-doc@FreeBSD.ORG  Mon Feb 24 20:02:11 2014
Return-Path: <owner-freebsd-doc@FreeBSD.ORG>
Delivered-To: freebsd-doc@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id BF074C9A;
 Mon, 24 Feb 2014 20:02:11 +0000 (UTC)
Received: from wonkity.com (wonkity.com [67.158.26.137])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 6FBF21164;
 Mon, 24 Feb 2014 20:02:11 +0000 (UTC)
Received: from wonkity.com (localhost [127.0.0.1])
 by wonkity.com (8.14.8/8.14.8) with ESMTP id s1OK25Xk002575
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Mon, 24 Feb 2014 13:02:05 -0700 (MST)
 (envelope-from wblock@wonkity.com)
Received: from localhost (wblock@localhost)
 by wonkity.com (8.14.8/8.14.8/Submit) with ESMTP id s1OK23LH002572;
 Mon, 24 Feb 2014 13:02:03 -0700 (MST)
 (envelope-from wblock@wonkity.com)
Date: Mon, 24 Feb 2014 13:02:03 -0700 (MST)
From: Warren Block <wblock@wonkity.com>
To: Remko Lodder <remko@FreeBSD.org>
Subject: Re: www/175685: HTTPS does not follow visitor among FreeBSD.org
 sub-domains
In-Reply-To: <30FE87E3-162F-415E-9B31-4FC264D9BFEE@FreeBSD.org>
Message-ID: <alpine.BSF.2.00.1402241300460.2118@wonkity.com>
References: <201402241830.s1OIU17s076805@freefall.freebsd.org>
 <30FE87E3-162F-415E-9B31-4FC264D9BFEE@FreeBSD.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3
 (wonkity.com [127.0.0.1]); Mon, 24 Feb 2014 13:02:05 -0700 (MST)
Cc: freebsd-doc@FreeBSD.org, Allan Jude <freebsd@allanjude.com>
X-BeenThere: freebsd-doc@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Documentation project <freebsd-doc.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>,
 <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/>
List-Post: <mailto:freebsd-doc@freebsd.org>
List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>,
 <mailto:freebsd-doc-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Feb 2014 20:02:11 -0000

On Mon, 24 Feb 2014, Remko Lodder wrote:

>
> On 24 Feb 2014, at 19:30, Allan Jude <freebsd@allanjude.com> wrote:
>
>> The following reply was made to PR www/175685; it has been noted by GNATS.
>>
>> From: Allan Jude <freebsd@allanjude.com>
>> To: bug-followup@FreeBSD.org
>> Cc:
>> Subject: Re: www/175685: HTTPS does not follow visitor among FreeBSD.org sub-domains
>> Date: Mon, 24 Feb 2014 13:25:42 -0500
>>
>> Another method that has become common in recent years is
>>
>> <a href="//www.freebsd.org/blah/blah">
>>
>> Which will keep the current protocol, be that HTTP or HTTPS
>>
>> Although I am not sure how some of the more basic browsers like lynx
>> might handle that. Google et all use it for including javascript to
>> avoid 'mixed content?.
>
> Cool. That would solve the problem here as well. To what degree should
> we support the ?lynx?es out there and cli based browsers ?

Is there an example page we can test?  Maybe this is already supported 
by some.