unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ronak B <ronakworks@gmail.com>
To: 56512@debbugs.gnu.org
Subject: bug#56512: gnu.org does not redirect http to https
Date: Mon, 11 Jul 2022 19:45:38 -0500	[thread overview]
Message-ID: <CAA9yktOCdfd7mhaj_Twt+A2_b+d0_+9WznKsdUUP6Dk2r7mvaQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]

Hi, I noticed today when I typed "man cat" and clicked on the "http://"
link in the man page that it did not redirect my browser from http to https.

$ curl -I http://www.gnu.org/software/coreutils/
HTTP/1.1 200 OK
Date: Tue, 12 Jul 2022 00:42:26 GMT
Server: Apache/2.4.29
Content-Location: coreutils.html
Vary: negotiate,Accept-Encoding
TCN: choice
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
X-Frame-Options: sameorigin
X-Content-Type-Options: nosniff
Access-Control-Allow-Origin: (null)
Accept-Ranges: bytes
Cache-Control: max-age=0
Expires: Tue, 12 Jul 2022 00:42:26 GMT
Content-Type: text/html
Content-Language: en

I also noticed this previous recent issue where this was resolved using an
nginx redirect from port 80 to 443 for *.guix.info

https://issues.guix.gnu.org/37348

Could we do this for all *.gnu.org too ?

After the domain and all of its subdomains are on HTTPS, then gnu.org can
also be added to the HSTS preload list.

https://hstspreload.org/

Best,
Ronak

[-- Attachment #2: Type: text/html, Size: 1540 bytes --]

             reply	other threads:[~2022-07-12 10:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12  0:45 Ronak B [this message]
2022-07-12 10:19 ` bug#56512: gnu.org does not redirect http to https Julien Lepiller
2022-07-12 11:03   ` Akib Azmain Turja via Bug reports for GNU Guix
2022-07-12 12:13     ` Ronak B
2022-07-12 20:19       ` Csepp
2022-07-14  1:56       ` Maxim Cournoyer

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA9yktOCdfd7mhaj_Twt+A2_b+d0_+9WznKsdUUP6Dk2r7mvaQ@mail.gmail.com \
    --to=ronakworks@gmail.com \
    --cc=56512@debbugs.gnu.org \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).