From: Andrey Repin <anrdaemon@yandex.ru>
To: Brian Clifton <brian@clifton.me>, cygwin@cygwin.com
Subject: Re: Proposed patch for web site: update most links to HTTPS
Date: Mon, 25 Apr 2016 06:10:00 -0000 [thread overview]
Message-ID: <48360918.20160425084918@yandex.ru> (raw)
In-Reply-To: <BL2PR03MB22817533DCF96CD385BD883DF620@BL2PR03MB228.namprd03.prod.outlook.com>
Greetings, Brian Clifton!
Please don't top-post. thanks.
> -----Original Message-----
> From: Andrey Repin [mailto:anrdaemon@yandex.ru]
> Sent: Sunday, April 24, 2016 5:00 PM
> To: Brian Clifton <brian@clifton.me>; cygwin@cygwin.com
> Subject: Re: Proposed patch for web site: update most links to HTTPS
>> 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.
> Can you please elaborate on why? I'm confused on why you prefer that Cygwin
> links users to non-secure versions of pages? (which in many cases will be
> redirected anyways).
I prefer it not forcing either, and only force secure connection, when absolutely
necessary. I.e. when downloading the setup binary.
> Links which ONLY work on http *have not* been changed and there are no other
> changes in this patch.
Secure connections been painfully slow and just annoying, when all you need is
a quick glance at the documentation.
All internal links must be relative to the domain and not force either
protocol or the domain name.
--
With best regards,
Andrey Repin
Monday, April 25, 2016 08:45:10
Sorry for my terrible english...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-04-25 5:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 0:05 Brian Clifton
2016-04-25 0:29 ` Andrey Repin
2016-04-25 5:50 ` Brian Clifton
2016-04-25 6:10 ` Andrey Repin [this message]
2016-04-25 13:20 ` Adam Dinwoodie
2016-04-25 17:41 ` Andrey Repin
2016-04-26 10:17 ` Csaba Raduly
2016-04-25 19:59 ` Nellis, Kenneth
2016-04-25 20:46 ` Vince Rice
2016-04-25 23:18 ` Brian Clifton
2016-04-26 19:19 ` Achim Gratz
2016-04-27 10:18 ` Linda Walsh
2016-05-20 16:36 ` Corinna Vinschen
2016-05-20 20:47 ` Warren Young
2016-05-22 0:30 ` Brian Clifton
2016-05-23 10:35 ` Corinna Vinschen
2016-05-24 12:42 ` Warren Young
2016-05-24 16:59 ` Corinna Vinschen
2016-05-24 18:55 ` Warren Young
2016-06-12 10:13 ` Brian Clifton
2016-06-14 19:20 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48360918.20160425084918@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=brian@clifton.me \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).