Date: Mon, 24 Feb 2014 13:02:03 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: Remko Lodder <remko@FreeBSD.org> Cc: freebsd-doc@FreeBSD.org, Allan Jude <freebsd@allanjude.com> Subject: Re: www/175685: HTTPS does not follow visitor among FreeBSD.org sub-domains Message-ID: <alpine.BSF.2.00.1402241300460.2118@wonkity.com> In-Reply-To: <30FE87E3-162F-415E-9B31-4FC264D9BFEE@FreeBSD.org> References: <201402241830.s1OIU17s076805@freefall.freebsd.org> <30FE87E3-162F-415E-9B31-4FC264D9BFEE@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1402241300460.2118>