No HTTPS on nginx.org by default

[B.R.]

HTTPS was supported, but internal links were systematically served over
HTTP.
Without considering any religion, this problem is now fixed.

As per your political decision on serving content (un)encrypted, it is *in
fine* your choice and it has been noted.
Power users already knew about HTTPS anyway.

Thanks Maxim.
---
*B. R.*

On Wed, Aug 24, 2016 at 1:58 PM, Maxim Konovalov <maxim at nginx.com> wrote:

> On 8/22/16 8:30 PM, Maxim Konovalov wrote:
> > On 8/22/16 8:23 PM, Richard Stanway wrote:
> >> See https://nginx.org/en/linux_packages.html#stable
> >>
> >> PGP key links are hard coded to http URLs:
> >>
> >> <p>
> >> For Debian/Ubuntu, in order to authenticate the nginx repository
> >> signature
> >> and to eliminate warnings about missing PGP key during installation
> >> of the
> >> nginx package, it is necessary to add the key used to sign the nginx
> >> packages and repository to the <code>apt</code> program keyring.
> >> Please download <a href="http://nginx.org/keys/nginx_signing.key">this
> >> key</a> from our web site, and add it to the <code>apt</code>
> >> program keyring with the following command:
> >> </p>
> >>
> > Yes, I see.  It should be fixed.  Thanks.
> >
> Fixed now.  Thanks.
>
> --
> Maxim Konovalov
> Join us at nginx.conf, Sept. 7-9, Austin, TX: http://nginx.com/nginxconf
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20160824/82d1cc56/attachment.html>