Hi folks,
I have a proposed change for the web site. This patch (see below) will update
most of the urls to HTTPS. In many cases there was a redirect; for those I
captured the new canonical address.
(Per the https://cygwin.com/contrib.html, this is *not* a change to anything in
the winsup dire
Greetings, Brian Clifton!
> Hi folks,
> I have a proposed change for the web site. This patch (see below) will
> update most of the urls to HTTPS. In many cases there was a redirect; for
> those I captured the new canonical address.
Please no.
--
With best regards,
Andrey Repin
Monday, April
hanks,
Brian
-Original Message-
From: Andrey Repin [mailto:anrdae...@yandex.ru]
Sent: Sunday, April 24, 2016 5:00 PM
To: Brian Clifton ; cygwin@cygwin.com
Subject: Re: Proposed patch for web site: update most links to HTTPS
Greetings, Brian Clifton!
> Hi folks,
> I have a proposed
Greetings, Brian Clifton!
Please don't top-post. thanks.
> -Original Message-
> From: Andrey Repin [mailto:anrdae...@yandex.ru]
> Sent: Sunday, April 24, 2016 5:00 PM
> To: Brian Clifton ; cygwin@cygwin.com
> Subject: Re: Proposed patch for web site: update
On Mon, Apr 25, 2016 at 08:49:18AM +0300, Andrey Repin wrote:
> Greetings, Brian Clifton!
> > -Original Message-
> > From: Andrey Repin
> >> Greetings, Brian Clifton!
> >
> >>> Hi folks,
> >
> >>> I have a proposed change for the web site. This patch (see below) will
> >>> update most of t
Greetings, Adam Dinwoodie!
> Secure connections historically had a high overhead, sure, but that's
> very rarely the case nowadays. Certainly my experince of loading the
> Cygwin web page is that there's no perceptible difference between the
> http and https versions. Adam Langley (a senior engi
-Original Message-
From: Adam Dinwoodie
> ...
> But I agree with Brian: the Cygwin website
> should use https everywhere unless there's some good, specific reason
> why it's a bad idea...
1. Did Brian say that? I couldn't find it in the thread.
2. I would be interested to hear the rationa
> On Apr 25, 2016, at 2:33 PM, Nellis, Kenneth wrote:
>
> -Original Message-
> From: Adam Dinwoodie
>> ...
>> But I agree with Brian: the Cygwin website
>> should use https everywhere unless there's some good, specific reason
>> why it's a bad idea...
>
> 1. Did Brian say that? I couldn
>From: cygwin-ow...@cygwin.com on behalf of Vince
>Rice
>Sent: Monday, April 25, 2016 12:58 PM
>To: cygwin@cygwin.com
>Subject: Re: Proposed patch for web site: update most links to HTTPS
>
>> On Apr 25, 2016, at 2:33 PM, Nellis, Kenneth
>> wrote:
>>
&
On Mon, Apr 25, 2016 at 3:05 PM, Andrey Repin wrote:
> Greetings, Adam Dinwoodie!
>
>> Secure connections historically had a high overhead, sure, but that's
>> very rarely the case nowadays. Certainly my experince of loading the
>> Cygwin web page is that there's no perceptible difference between
Brian Clifton writes:
> In addition to this patch, Apache could be configured better (Cygwin.com
> scores a B):
> https://www.ssllabs.com/ssltest/analyze.html?d=cygwin.com
You'd need to address this to overseers at sourceware.com.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb
Adam Dinwoodie wrote:
Secure connections historically had a high overhead, sure, but that's
very rarely the case nowadays. Certainly my experince of loading the
Cygwin web page is that there's no perceptible difference between the
http and https versions. Adam Langley (a senior engineer at Goog
On Apr 24 17:18, Brian Clifton wrote:
> Hi folks,
>
> I have a proposed change for the web site. This patch (see below) will update
> most of the urls to HTTPS. In many cases there was a redirect; for those I
> captured the new canonical address.
>
> (Per the https://cygwin.com/contrib.html, th
On May 20, 2016, at 10:36 AM, Corinna Vinschen
wrote:
>
> On Apr 24 17:18, Brian Clifton wrote:
>>
>> This patch (see below) will update most of the urls to HTTPS.
>
> Since Cygwin.com redirects http requests to https anyway, all links
> to cygwin.com (or, FWIW, sourceware.org) will end up as
On May 22 00:29, Brian Clifton wrote:
> >On Apr 24 17:18, Brian Clifton wrote:
> >> Hi folks,
> >>
> >> I have a proposed change for the web site. This patch (see below) will
> >> update most of the urls to HTTPS. In many cases there was a redirect; for
> >> those I captured the new canonical ad
On May 23, 2016, at 4:35 AM, Corinna Vinschen wrote:
>
> using relative paths inside the Cygwin docs
> (cygwin-api, cygwin-ug-net, and faq) is not such a bright idea, because
> the docs should ideally work even if not on the cygwin.com website.
Did you mean to say “absolute paths”? If not, then
On May 24 06:38, Warren Young wrote:
> On May 23, 2016, at 4:35 AM, Corinna Vinschen wrote:
> >
> > using relative paths inside the Cygwin docs
> > (cygwin-api, cygwin-ug-net, and faq) is not such a bright idea, because
> > the docs should ideally work even if not on the cygwin.com website.
>
> D
On May 24, 2016, at 8:33 AM, Corinna Vinschen wrote:
>
> On May 24 06:38, Warren Young wrote:
>> On May 23, 2016, at 4:35 AM, Corinna Vinschen wrote:
>>>
>>> using relative paths inside the Cygwin docs
>>
>> Did you mean to say “absolute paths”?
>
> I was talking about links to the non-ducumen
>From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On Behalf Of
>Corinna Vinschen
>Sent: Monday, May 23, 2016 3:35 AM
>To: cygwin@cygwin.com
>Subject: Re: Proposed patch for web site: update most links to HTTPS
>
>On May 22 00:29, Brian Clifton wrote:
>&
On Jun 12 07:52, Brian Clifton wrote:
> >From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On Behalf Of
> >Corinna Vinschen
> >Can you please split up the patch in two chunks?
> >
> >The generic website patches should be based on the Website git repo at
> >
> > git://sourceware.org/g
20 matches
Mail list logo
